Date: Thu, 21 Dec 1995 23:12:27 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: gatliff@cel.cummins.com (William A. Gatliff) Cc: hackers@freebsd.org Subject: Re: FreeBSD interrupt management Message-ID: <199512212212.XAA16320@uriah.heep.sax.de> In-Reply-To: <9512211636.AA03690@gatekeeper.cummins.com> from "William A. Gatliff" at Dec 21, 95 11:07:39 am
next in thread | previous in thread | raw e-mail | index | archive | help
As William A. Gatliff wrote: > > I've waded around in some 2.0.5 driver code (the 8250, I think), and I'm > stumped. I can't make the connection between when the uart generates the > interrupt and the calling sequence to invoke the driver. I checked the Well, i think this is one of the most trickiest portions, since all the interrupt handler stubs are being auto-generated by the config program. I order to understand all of this, you don't only need the kernel sources, but you also need to configure a kernel compile directory. Well, why don't you grab an old i386/sx16, wipe the dust off it, and install a tiny FreeBSD on it? > handbook, and couldn't find any clues on how device drivers interact with the > kernel, and apparently the 8250 driver isn't basic enough for a lower life > form such as myself. :^) Can someone point me in a different direction? Hmm, well, once you figured it out and happen to know about the details, please write us a section for the handbook. :-) > I've FTP'd 2.1, but I can't get the files back into human-readable form... for the `foo' dist: cat foo.?? | gzip -dc | (cd /where/you/want; tar -xvf -) They are gzipped tar files. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512212212.XAA16320>