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: Tue, 18 Apr 2006 21:15:50 +0200 [thread overview]
Message-ID: <9f3897940604181215p3aa0e5f2kf26677a438b61377@mail.gmail.com> (raw)
In-Reply-To: <20060418013410.E7A9998D64@dexter-peak.quanstro.net>
On 4/18/06, erik quanstrom <quanstro@quanstro.net> wrote:
> 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?
IIRC dac960 has completely OS-independent firmware and communicates
using some kind of protocol? with host os - it is only a storage
controller with SCSI pass-thru for SCSI Tape. It's not what you'd call
a SCSI HBA :)
I wouldn't be surprised if dac960 isn't somehow similar to DPT EATA
standard, where you didn't give a damn about integrated firmware (DPT
Smart* IV controllers used m68k cpu's connected with specialised SCSI
co-processor and PCI bus adapter - It's firmware was completely
independent (most powerful models had complete 68060 :D)
> 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.)
I don't think it's necessary to have a bus analyzer.... just read SCSI
documentation and available source code from *BSD and Linux...
> - erik
--
Paul Lasek
next prev parent reply other threads:[~2006-04-18 19:15 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
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 [this message]
-- 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=9f3897940604181215p3aa0e5f2kf26677a438b61377@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).