From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <cfaee64eda7f61730e82e56c22b30b1c@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 16 Apr 2006 19:31:12 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Writing device drivers
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 37ab620e-ead1-11e9-9d60-3106f5b1d025

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?

- erik

On Sun Apr 16 19:24:05 CDT 2006, rsc@swtch.com wrote:
> > why can't the firmware be compiled on linux or
> > windows or something and treated as binary goo?
>
> depends on how much it interacts with the driver.
> the wireless ones come with a giant mess of goop
> that you're not allowed to touch or even know what
> it means.  but then the ncr scsi drivers have a nice
> simple microcode that is tightly integrated with the
> actual driver.  see the plan 9 and linux drivers, for example.
> nigel wrote an assembler for it and it's *far* better
> than the hand-assembly that the linux driver writers
> resorted to.
>
> russ
>