From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d190612120151s53a2a530h93db8bb2afdb0408@mail.gmail.com>
Date: Tue, 12 Dec 2006 20:51:43 +1100
From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Again: (self)hosted Plan9? Was: [9fans] extending xen to allow
In-Reply-To: <82c890d00612120141v1bfc526dra2f296afdee13fca@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ee9e417a0612111829n33dbb109t7d76959bfe0c0549@mail.gmail.com>
	<818c01eca2880742b4a56e87bc863a99@terzarima.net>
	<82c890d00612120141v1bfc526dra2f296afdee13fca@mail.gmail.com>
Topicbox-Message-UUID: f114229e-ead1-11e9-9d60-3106f5b1d025

well while i'm commenting randomly ...

none.

there is essentially no documention on many, many boards
and chips "just in case we want to rip off their IP'.

correct me if i'm wrong - i have stood corrected.

brucee

On 12/12/06, Gabriel Diaz <gabidiaz@gmail.com> wrote:
> Hello
>
> what books you guys recommend to start with hardware programming?
> (nemo's kernel book of course)
>
> I mean, having no experience with hardware programming, a desire i
> have is to read something to learn from other's experience on writing
> software for manage hardware. (something like the practice of
> programming but focused on hardware issues).
>
> of course i can always re-read my school notes, and start to fight
> with the real life. . . but this looks discouraging, (and becomes much
> more discouraging taking in account the comments of more talented
> programmers on the iwp9 :)
>
> thanks
>
> gabi
>
>
> On 12/12/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> > >> - writing drivers sucks.
> >
> > it's not a big problem in itself.  i quite enjoy it for
> > the reasonably well-documented chipsets one finds in (say)
> > embedded ARM and PowerPC platforms.  for those, i hardly ever
> > bother to look at another driver.  it's just so straightforward.
> > i look at the book and do what it says.  it doesn't work, so i
> > find there's an errrata or fuss about discovering that a bit
> > has the opposite sense from what's documented.  no matter.
> >
> > on the PC, it's rather more troublesome: when i could get
> > reasonable documentation it was much the same as anything else.
> > without it, it's tedious, and perhaps too time-consuming
> > if i'm doing it in my spare time.  theo de raadt's slides
> > were quite a good summary.
> >
> > still, there's not much choice, really.
> >
>