Date: Sat, 13 Dec 1997 23:33:49 -0500 (EST) From: gjp@erols.net (Gary Palmer) To: itojun@itojun.org Cc: hackers@FreeBSD.ORG Subject: Re: Beginning SPARC port Message-ID: <199712140433.XAA17136@mutara.noc.erols.net> References: <Pine.LNX.3.95.971205141315.20201G-100000@paladio> <27620.881807554@coconut.itojun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <27620.881807554@coconut.itojun.org>, itojun@itojun.org (Jun-ichiro itojun Itoh) writes: > By performing simple grep for `outb', the following files seem to > include i386-specific function calls. > pccard/pcic.c > pci/aic7870.c > pci/if_de.c > pci/ncr.c > pci/tek390.c > pci/wd82371.c What makes you think outb is i386 specific? Surely since it is defined in a machine header to some asm fn, what it really means is that it is GNU C specific? If you think about it, if a platform needed a bit of complexity to do inb/outb, you #define them to funciton calls. Yes, there is `cruft' in the main (non /sys/i386) tree which needs to be dealt with, and there is even more in the main userland tree I bet, but one of the reasons we on the core team have long wanted a port to another platform is to clean up the source tree. Its generally felt that another port will highlight shortcomings and bugs in our i386 port faster than bashing on it with ddb will... Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712140433.XAA17136>