From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: [9front] uh. duh. so
Date: Tue, 28 Sep 2021 18:27:24 -0700 [thread overview]
Message-ID: <CAHwi9bzcAx22CMHS-LSRCtRDsUn6H3T0DEoy6ft5fvk11LvVQQ@mail.gmail.com> (raw)
well. I sent that email about my thoughts on listen1...
a while back I wrote an audio driver for RPi crapola... DO NOT USE MINE!!!
I have deleted it from the repo... it has a buffer overflow bug at
least... I was able to get the radio coming out of the speakers and
quit working on it and left it. derp :/
next reply other threads:[~2021-09-29 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 1:27 Eli Cohen [this message]
2021-09-29 1:31 ` [9front] " Eli Cohen
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=CAHwi9bzcAx22CMHS-LSRCtRDsUn6H3T0DEoy6ft5fvk11LvVQQ@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).