From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <82c890d00612120141v1bfc526dra2f296afdee13fca@mail.gmail.com> Date: Tue, 12 Dec 2006 10:41:58 +0100 From: "Gabriel Diaz" 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: <818c01eca2880742b4a56e87bc863a99@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <818c01eca2880742b4a56e87bc863a99@terzarima.net> Topicbox-Message-UUID: f129fc68-ead1-11e9-9d60-3106f5b1d025 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 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. >