9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "chötrin." <chotrin@posteo.net>
To: 9front@9front.org
Subject: [9front] Getting Started with Kernel Development?
Date: Sun, 25 Apr 2021 14:15:37 +0000	[thread overview]
Message-ID: <C5525CBB0882CCD7A2D41C696976D1F5@posteo.net> (raw)

Hi y'all!

I'm running 9front on a RPi 3B+, and it looks like there's no audio
device support here.  I think I'd like to try my hand at implementing
that, but hacking at the Plan 9 kernel is new to me.

uramekus pointed me to nemo's "Notes on the Plan 9 3rd edition Kernel
Source," which I'm currently perusing to try to grok what's going on.
It's been really helpful so far.

I've also got the "BCM2835 ARM Peripherals" spec, which specifies how
to interact with the chip's I2S audio interface.

I *think*, at least upon cursory inspection, I'm going to be
implementing the bcm64 end of /sys/src/9/port/audioif.h to speak with
/sys/src/9/port/devaudio.c.  I can use the /sys/src/9/pc tree as an
example to follow, assuming I can figure out how the boot code is
calling, say, audiosb16link().  I have plenty of homework ahead of me,
to say the least.

My question to you is this: where do I get started actually making
changes to the 9front kernel and testing them out?  What does, or
should, the development flow look like for me?  Ideally, I'd be able
to go back and forth between a known good kernel and whatever I'm
hacking at.  I don't want to be backing up my SD card and restoring it
over and over again, if at all possible.

If there's some handy writeups, documentation, or tips y'all have for
getting started with this, I'd be much obliged!

Thanks for reading, and be well. :)

chötrin.


             reply	other threads:[~2021-04-26  9:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 14:15 chötrin. [this message]
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
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=C5525CBB0882CCD7A2D41C696976D1F5@posteo.net \
    --to=chotrin@posteo.net \
    --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).