From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Nigel Roles <nigel@9fs.org>
Subject: RE: [9fans] Writing device drivers
Date: Mon, 17 Apr 2006 20:34:10 -0500 [thread overview]
Message-ID: <20060418013410.E7A9998D64@dexter-peak.quanstro.net> (raw)
In-Reply-To: <HOEHIDJJJINMLFPOLFJCIEKIDGAA.nigel@9fs.org>
thanks for the excellent information. i have the fortune of having a
dac960 controller and an adaptec 7898n in the same machine. lucky me.
a quick look at the dac960 driver for linux doesn't immediately reveal
any firmware. do you think that would be an easier driver to build than
the adaptec?
i don't know a think about scsi bus protocol and i don't have a bus analyzer.
is such a beast affordable? (i am running old va linux boxen after all.)
- erik
"Nigel Roles" <nigel@9fs.org> writes
|
| 9fans-bounces+ngr=9fs.org@cse.psu.edu wrote:
| >> it looks like all the code for aic-7xxx is in the linux kernel tree,
| >> including an assembler.
| >>
| >> does anybody know what processor it uses?
| >
| > it probably doesn't matter. it's unlikely that the
| > microcode is written in a real processor's assembly
| > language. usually it is a virtual processor defined
| > by the card.
|
| Originally Adaptec has an on-board 8035 which presented a mailbox (aka scb
| (aka Scsi Command Block)) interface to the host. You load up the command
| block, enable it, and wait for an interrupt. The firmware was fixed in an
| EPROM next door. This conforms to Russ'es idea that it is a virtual
| processor.
[etc]
next prev parent reply other threads:[~2006-04-18 1:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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
[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
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=20060418013410.E7A9998D64@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=nigel@9fs.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).