From owner-freebsd-hackers Sat Dec 13 21:18:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA10283 for hackers-outgoing; Sat, 13 Dec 1997 21:18:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from coconut.itojun.org (root@coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA10276 for ; Sat, 13 Dec 1997 21:18:44 -0800 (PST) (envelope-from itojun@itojun.org) Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.5/3.6Wbeta6) with ESMTP id OAA16612; Sun, 14 Dec 1997 14:18:39 +0900 (JST) To: gjp@erols.net (Gary Palmer) cc: hackers@FreeBSD.ORG In-reply-to: gjp's message of Sun, 14 Dec 1997 00:06:53 EST. <199712140506.AAA17194@mutara.noc.erols.net> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Beginning SPARC port From: Jun-ichiro itojun Itoh Date: Sun, 14 Dec 1997 14:18:39 +0900 Message-ID: <16608.882076719@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> hardware I/O model is CPU specific. There are architectures >> that do not have inb/outb instruction, and maps I/O device control >> registers onto memory. I dunno how Sparc-with-PCI motherboard >> access pci registers, but I'm sure there has to be bunch of changes. >Right, but in that case you #define the inb/outb macros to be the >appropriate load/store instructions for the processor. >What I am trying to say is that while it may not be the Politically >Correct(TM) solution, it is not totally i386 bound either. Being >#defines, its a bit more flexible than you were making out. Yes, I agree with your idea, as the first step. In the future we should introduce some function like, pci_reg_write_byte(), for more platform-independency. Not all the implementers know about i386:-) itojun