From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Getting Started with Kernel Development?
Date: Fri, 30 Apr 2021 09:36:24 +0200 [thread overview]
Message-ID: <CAFSF3XN9H+xm-rjHuy2kg68zcQJ4DOfD+k3mBc6VaPo1a6PtZA@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9bzyKw8DkcOqZAsBTdZ=srR5aE62OVosNebSweRsZq3rRQ@mail.gmail.com>
if they are scratchy perhaps you want a kratzbaum like
https://shop-cdn-m.mediazs.com/bilder/natural/paradise/kratzbaum/deckenspanner/xxl/9/400/59368_59369_np_kb_ds_xxl_1000x1000_logo_la_dsc8713_9.jpg
On 4/30/21, Eli Cohen <echoline@gmail.com> wrote:
> I'm very glad you appreciate it! it still needs a few things done if
> used over a different driver, it needs GPIO pin selection for
> different boards, better buffering (right now each write just gets
> alloced and sent whole to the speakers), and it just plain sounds
> scratchy...
>
> - Eli
>
> On Thu, Apr 29, 2021 at 6:17 PM chötrin. <chotrin@posteo.net> wrote:
>>
>> Quoth Eli Cohen <echoline@gmail.com>:
>> > I started on an audio driver a while back, there seems to be another
>> > one in extra that might be better
>> >
>> > https://raw.githubusercontent.com/echoline/9emmc/master/bcm/audiobcm2835.c
>>
>> This is great! Thank you for sharing this. :D
>>
>> chötrin.
>>
>
next prev parent reply other threads:[~2021-04-30 8:06 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
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 [this message]
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=CAFSF3XN9H+xm-rjHuy2kg68zcQJ4DOfD+k3mBc6VaPo1a6PtZA@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).