9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Getting Started with Kernel Development?
Date: Sun, 25 Apr 2021 19:20:01 +0200	[thread overview]
Message-ID: <CAFSF3XNKTR+hybdf19nAUGqV9Ka7X=FSCBM=qMDwjLbE4A2POw@mail.gmail.com> (raw)
In-Reply-To: <0C73F8031AC040C9C98E26332A9A4D2B@felloff.net>

here's a fitting solution

https://de.aliexpress.com/item/1005002220730177.html

i picked this one because it doesn't have a case,  just like the rpi.
of course the ones with case are a little cheaper, but this way you
can say you built it yourself

On 4/25/21, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
>> I've also got the "BCM2835 ARM Peripherals" spec, which specifies how
>> to interact with the chip's I2S audio interface.
>
> As far as i know, the stock raspberry pi is not using I2S.
>
> There are some people that have build their own soundcards
> for the pi with a I2S DAC but it is not standard.
>
> Instead, they hacked together some filter circuit and connected
> it to a GPIO pin.
>
> (This pattern is a logical continuation on raspberry pi hardware
> design philosphy, where using the existing dedicated peripherals
> for their intended purpose must be rejected and standards must be
> ignored: cpu -> GPU, ethernet -> USB, audio -> GPIO, wifi -> SDCARD,
> usb -> ?????WHATISTHIS????, usbc -> ?????, PXE -> ???????).
>
> 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.
>
> Afik, it is possible to drive the gpio pin from the cpu somehow
> but quality will be garbage and waste alot of power.
>
> --
> cinap
>

  reply	other threads:[~2021-04-25 17:57 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 [this message]
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.
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='CAFSF3XNKTR+hybdf19nAUGqV9Ka7X=FSCBM=qMDwjLbE4A2POw@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --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).