From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] bcm-audio
Date: Thu, 2 Dec 2021 21:09:43 -0800 [thread overview]
Message-ID: <CAHwi9by22QOF7ou18uWfsOsKtZB0CBz3dgJ5GeOudhejFnAnfQ@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9by1Rxi-gk-aCua7kTg-Z_Cyfyzv3Kb6wqYmr4BnkfY0Fw@mail.gmail.com>
dammit. now everyone is going to think I'm creepy as fuck. well... at
least I stopped using plan 9 right??? fantastic software, by the way
:)
I rescind any orders to go play with barbie dolls.
On Thu, Dec 2, 2021 at 9:04 PM Eli Cohen <echoline@gmail.com> wrote:
>
> ATTN: DO NOT DELETE
>
> NOTICE: POSSIBLE SECURITY RISK
>
> I'm not sure I agree, hiro. hardware can have many flaws but drivers
> can have flaws too. I am pretty sure my (comparable, simpler) audio
> driver did have at least one flaw, I did not check buffer size of
> write messages or use a ringbuffer or anything, I sent them all off
> with DMA. I'm worried 8192 KB might be a problem by that point. the
> way I was able to tell was by looking at the username of the kproc, it
> was all shitty, also that machine has been all fucked up for months in
> all kinds of other ways. it worked fine for listening to online radio
> streams of news radio, then it crapped out really badly for some
> reason. I have been unable to repair the machine. I've been feeling
> really bad about this because it was a bunch of rpi CMs like a tiny
> cray (not joking hiro. you are an asshole too!!! see what happens?? my
> computer science barbie doll is not impressed. to say the least)
>
> please consider at least that my ENTIRELY DIFFERENT audio driver
> FLAGGED FOR SUSPICION OF BAD CODE and deleted
>
> I tried reading through the bcm-audio code but it was more
> complicated. I'm pretty sure mine sucks though. I deleted it but hey
> this is plan 9. mine is on github
>
> I sat here pissed for months, then unplugged it, threw that shit in a
> box for now. the barbie doll and I have felt better for a while over
> here. we have tiny cups for tea parties but we ain't trustin' no
> actual fuckin' tea no more with world leaders and shit.
>
> don't even think about touching my fuckin' doll collection now. plan 9
> is cool. rest of y'all are fuckin' burnt
next prev parent reply other threads:[~2021-12-03 5:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 20:18 adr
2021-12-02 23:02 ` hiro
2021-12-03 0:30 ` Steve Simon
2021-12-03 1:43 ` Thaddeus Woskowiak
2021-12-03 2:13 ` adr
2021-12-03 1:35 ` adr
2021-12-03 2:55 ` Thaddeus Woskowiak
2021-12-03 5:04 ` Eli Cohen
2021-12-03 5:09 ` Eli Cohen [this message]
2021-12-03 5:15 ` Kurt H Maier
2021-12-03 5:28 ` Eli Cohen
2021-12-03 5:32 ` Eli Cohen
2021-12-03 7:45 ` the lemons
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=CAHwi9by22QOF7ou18uWfsOsKtZB0CBz3dgJ5GeOudhejFnAnfQ@mail.gmail.com \
--to=echoline@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).