Subject: Re: [9front] pi4 wifi and audio
Date: Sat, 12 Feb 2022 14:45:13 -0800 [thread overview]
Message-ID: <6403CC303B834A70F53A520558BED0EB@gmail.com> (raw)
Quoth Thaddeus Woskowiak <firstname.lastname@example.org>:
> I don't think Miller's wifi does WPA or any auth. Though I've not ran
> Miller's pi image in a long time. Miller's wifi driver is also different
> from 9 front's WiFi driver so it's not a simple port.
> For good pi audio I use a Dayton USB DAC which outputs pretty clean audio.
> Unfortunately the pi uses a really crummy SoC as it started life as an
> EoL'd chip for set-top boxes. That's why it does weird crap like boot from
> the GPU and lacked proper Ethernet for ages. Even Pi founder Ebbon Upton
> was unable to grasp why people wanted proper Ethernet as the pi was only
> ever meant for teaching. It's an educational toy built from a chip
> scrounged from the cut out bin but everyone seems to want to ignore that
> part. You get what you pay for.
> I tend to prefer cheap embedded PC's off eBay or itx Celeron SoC boards if
> I need a small low power system.
> On Sat, Feb 12, 2022, 1:11 PM <email@example.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.
Interesting. Seems like a lot of wasted effort. Unless as you say using pi as a teaching
experiement. So what about hackboard2. Kind of the same specs but Intel. I'm wondering if
it will just boot 9front and work without too much fuss.
next prev parent reply other threads:[~2022-02-13 0:11 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
2022-02-12 18:46 ` Steve Simon
2022-02-12 20:56 ` Thaddeus Woskowiak
2022-02-12 22:45 ` thinktankworkspaces [this message]
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
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 \
* 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).