From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Writing device drivers
Date: Mon, 17 Apr 2006 01:00:14 +0200 [thread overview]
Message-ID: <9f3897940604161600u2b0dbd3bv17d8018aa0b22c3f@mail.gmail.com> (raw)
In-Reply-To: <509071940604150716p4df88e40yf304d9d7b82a6fb0@mail.gmail.com>
On 4/15/06, Anthony Sorace <anothy@gmail.com> wrote:
> personally, i'd love firewire/ieee1394 support, although that's mostly
> because i've got a small stack of such disks available to me, mostly
> sitting idle. i believe someone (peter bosch?) was working on this a
> few years ago.
I agree - firewire bus/device class drivers + at least ohci1394 would
be a great thing...
> for getting familiar with the plan 9 interfaces and such, you can get
> started by just writing a driver that does something simple,
> software-only. i found that quite educational getting started. go
> write /dev/rot13 or something. for something trivial with real
> hardware... has anyone ever bothered to write a driver for the PC
> speaker? that should be fairly easy (but then, it is a PC, so i
> wouldn't be shocked if not).
>
For a little project - why not create kernel mode port of linux coffee
machine driver? (somewhere in the HOWTOs :D)
Not so long ago I tried to plunge through SCSI code to make Plan9 work
on my machine without Xen&co, but I decided to withdraw when I found
I'd have to write a compiler for firmware (and possibly rewrite
BSD/Linux firmware) in addition to driver itself... (Adaptec AIC-7892
- UltraWide2...)
--
Paul Lasek
next prev parent reply other threads:[~2006-04-16 23:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a5bd8ccbc2e53557663e2a9020fb26c@coraid.com>
[not found] ` <820bc1260604140834v2a773ev90ff46b4e6b2427f@mail.gmail.com>
2006-04-14 15:36 ` Eric Smith
2006-04-14 19:33 ` David Leimbach
2006-04-15 4:58 ` jmk
2006-04-15 13:24 ` Eric Smith
2006-04-15 14:16 ` Anthony Sorace
2006-04-16 23:00 ` Paweł Lasek [this message]
2006-04-19 3:10 erik quanstrom
2006-04-19 4:02 ` jmk
2006-04-19 4:57 ` lucio
2006-04-19 6:59 ` Nigel Roles
2006-04-19 21:12 ` quanstro
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 0:31 erik quanstrom
2006-04-17 1:44 ` Russ Cox
2006-04-17 10:01 ` Nigel Roles
2006-04-18 1:34 ` erik quanstrom
2006-04-18 14:49 ` Nigel Roles
2006-04-18 15:42 ` jmk
2006-04-18 15:59 ` Moritz Kiese
2006-04-18 16:03 ` Nigel Roles
2006-04-18 19:15 ` Paweł Lasek
2006-04-17 0:11 erik quanstrom
2006-04-17 1:24 ` Russ Cox
2006-04-16 1:02 erik quanstrom
2006-04-16 2:36 ` Anthony Sorace
2006-04-16 8:06 ` Bruce Ellis
2006-04-15 23:34 erik quanstrom
2006-04-15 23:55 ` Skip Tavakkolian
2006-04-15 15:26 erik quanstrom
2006-04-15 23:04 ` Federico Benavento
2006-04-15 23:18 ` Skip Tavakkolian
2006-04-16 0:43 ` Federico G. Benavento
2006-04-16 18:03 ` Charles Forsyth
2006-04-16 18:14 ` Bruce Ellis
2006-04-16 21:31 ` Charles Forsyth
2006-04-14 3:20 Eric Smith
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=9f3897940604161600u2b0dbd3bv17d8018aa0b22c3f@mail.gmail.com \
--to=pawel.lasek@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).