From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] AC'97
Date: Mon, 16 Apr 2007 20:42:10 -0400 [thread overview]
Message-ID: <9ab217670704161742y3a933a40iaef369758989a2ae@mail.gmail.com> (raw)
In-Reply-To: <43c21e2f96a00f29cac27671bbc12f58@coraid.com>
2007/4/16, erik quanstrom <quanstro@coraid.com>:
> let's just suppose there is already an ac97 driver that does everything
> available. the excercize of writing another driver is still useful. there's
> a lot to be learned through the process. i saw a lot of good information
> on the web page describing the process that wasn't present in the link
> to source on 9grid. i may need to write an ac97 driver for a non-plan9
> kernel. i think i could use some of the tips presented there.
Similar to what I've said before in this thread. In fact, that link
did indeed provide a good bit of useful information. If only all
drivers were written with this model in mind! Porting would be a lot
easier. My original question was certainly not intended to downplay
the efforts of either party.
> so, uriel, could you explain why these folk's education needs to benefit you
> or to fit into some grand development model?
Wait, this is exactly what I wanted to avoid. Let's kill the flames,
please. Or avoid them before they start.
> - erik
>
>
next prev parent reply other threads:[~2007-04-17 0:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 20:25 Devon H. O'Dell
2007-04-16 20:26 ` [9fans] AC'97 Devon H. O'Dell
2007-04-16 21:03 ` Bankim Bhavsar
2007-04-16 22:20 ` Steve Simon
2007-04-16 22:22 ` erik quanstrom
2007-04-16 22:27 ` Devon H. O'Dell
2007-04-17 0:02 ` [9fans] AC'97 Uriel
2007-04-17 0:12 ` Skip Tavakkolian
2007-04-17 0:26 ` erik quanstrom
2007-04-17 0:42 ` Devon H. O'Dell [this message]
2007-04-17 1:16 ` Dave Eckhardt
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=9ab217670704161742y3a933a40iaef369758989a2ae@mail.gmail.com \
--to=devon.odell@gmail.com \
--cc=9fans@cse.psu.edu \
/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).