9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "chötrin." <chotrin@posteo.net>
To: 9front@9front.org
Subject: Re: [9front] Getting Started with Kernel Development?
Date: Sun, 25 Apr 2021 22:37:53 +0000	[thread overview]
Message-ID: <09DE236CE114658955B1874482660617@posteo.net> (raw)
In-Reply-To: <0C73F8031AC040C9C98E26332A9A4D2B@felloff.net>

Quoth cinap_lenrek@felloff.net:
> As far as i know, the stock raspberry pi is not using I2S.

I've run Raspbian on another RPi and used the onboard sound with it,
but not sure about how it's handled under the hood.  I *suspect* it's
using I2S.  At least, that's what it looks like from this ALSA driver
source:

https://github.com/raspberrypi/linux/blob/rpi-5.10.y/sound/soc/bcm/bcm2835-i2s.c

There's some discussion on the RPi forums that hints at how the
onboard sound works:

https://www.raspberrypi.org/forums/viewtopic.php?t=59823

And the BCM spec I mentioned is here (warning: huge PDF):

https://cs140e.sergio.bz/docs/BCM2837-ARM-Peripherals.pdf

The relevant parts start on page 119.  Apparently the register base
address moved between BCM2835 and BCM2837.

Anyway, this may be a fool's errand to get working-- you could very
well be correct that they're doing some really janky stuff between the
Broadcom chip and the audio out pins.  I haven't dug deep enough to
stare at any schematics or anything like that yet.

Still, I'd like to give it a go.  I'd like to dig into the guts of
Plan 9 and I'd like to get audio working without tacking on an
external DAC (although, that'd probably sound WAY better).

I'm *thinking* that I'll use some external thumbdrive or be dropping
stuff into the RPi's FAT partition depending on how accessible the
bitbanging is from userspace.  I'm new to Plan 9, so I'm probably
pretty far off the mark.

Quoth cinap_lenrek@felloff.net:
> The GPU has firmware code to drive that GPIO pin and also send
> audio over HDMI, but todo that you have to talk to the videocore
> firmware thru a complicated software media streaming interface.

Oh yeah, I saw that, also.  I think I'll pass on trying to do that for
the time being.  :^)

chötrin.


  parent reply	other threads:[~2021-04-25 22:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 14:15 chötrin.
2021-04-25 16:07 ` cinap_lenrek
2021-04-25 17:20   ` hiro
2021-04-25 17:21     ` hiro
2021-04-25 23:36     ` Steve Simon
2021-04-26  9:33       ` hiro
2021-04-26 13:01         ` Steve Simon
2021-04-25 22:37   ` chötrin. [this message]
2021-04-26 17:08 ` Daniel Morandini
2021-04-26 17:17   ` hiro
2021-04-27  9:39     ` Daniel Morandini
2021-04-27 11:07       ` cinap_lenrek
2021-04-28  8:34         ` Daniel Morandini
2021-04-29  5:10         ` kjn
2021-04-29 11:07           ` Eli Cohen
2021-04-30  1:12             ` chötrin.
2021-04-30  1:24               ` Eli Cohen
2021-04-30  7:36                 ` hiro
2021-04-26 23:40   ` chötrin.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09DE236CE114658955B1874482660617@posteo.net \
    --to=chotrin@posteo.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).