9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] pi4 wifi and audio
Date: Sat, 12 Feb 2022 19:07:31 +0100	[thread overview]
Message-ID: <CAFSF3XMZWNeriJ7XG8n3nzR1wdw1RSNHQgKW4fNLBw-ErN7ZdQ@mail.gmail.com> (raw)
In-Reply-To: <0783F40825A7C63C5EB299280A1F6A9D@gmail.com>

yes, miller's version has wifi. i don't remember if anybody did the
work to bring it to 9front, but in any case they didn't finish it ( ==
mainline it).

audio, some people wasted their time with the incomplete audio
solution in the rpi, it but then gave up IIRC.
some people like to add a DAC to the I2C bus, but i consider that also
a waste of time, esp. as long as you can get 1$ USB->audio converters
including shipping from china, the quality is 100% matching the rpi
hardware, and a lot better than most DIY rpi audio add-ons.

as much as i hate USB, for soundcards that's good enough and we
already support it.

On 2/12/22, thinktankworkspaces@gmail.com <thinktankworkspaces@gmail.com> wrote:
> So 9front on pi4 seems pretty stable. But has anyone got audio and wifi
> working. I recall
> reading some place that pi hardware developers kind of deviated from
> convention so its a bit
> tricky to get some of that stuff working. Perhaps I might also be asking for
> some sort of
> guide to read on how to build or deal with making drivers in 9front and some
> troubleshooting
> steps to follow. Ponies and Unicorns I want those also, so yea.

  reply	other threads:[~2022-02-12 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 17:43 thinktankworkspaces
2022-02-12 18:07 ` hiro [this message]
2022-02-12 18:46   ` Steve Simon
2022-02-12 20:56 ` Thaddeus Woskowiak
2022-02-12 22:45   ` thinktankworkspaces
2022-02-13  0:40     ` hiro
2022-02-13  2:55       ` thinktankworkspaces
2022-02-13  3:25     ` Thaddeus Woskowiak
2022-02-13  7:37       ` Steve Simon

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:

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

  git send-email \
    --in-reply-to=CAFSF3XMZWNeriJ7XG8n3nzR1wdw1RSNHQgKW4fNLBw-ErN7ZdQ@mail.gmail.com \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \


* 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).