From owner-freebsd-arch Sun Jan 13 10:49: 8 2002 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1C64F37B419 for ; Sun, 13 Jan 2002 10:49:02 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0DIn0l04533; Sun, 13 Jan 2002 11:49:01 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0DIn0x68134; Sun, 13 Jan 2002 11:49:00 -0700 (MST) (envelope-from imp@village.org) Date: Sun, 13 Jan 2002 11:48:28 -0700 (MST) Message-Id: <20020113.114828.53910112.imp@village.org> To: tmoestl@gmx.net Cc: gibbs@scsiguy.com, freebsd-arch@FreeBSD.ORG Subject: Re: adding more endian conversion and bus space functions From: "M. Warner Losh" In-Reply-To: <20020113181157.GA451@crow.dom2ip.de> References: <20020111005207.GA7246@crow.dom2ip.de> <200201131656.g0DGuJg21488@aslan.scsiguy.com> <20020113181157.GA451@crow.dom2ip.de> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <20020113181157.GA451@crow.dom2ip.de> Thomas Moestl writes: : Are there many drivers around that already do their own conversions? : To me, it seems that most that are prepared to be used on big-endian : systems already rely on the bus space functions to do the appropriate : conversions (since on NetBSD, they do so), but I may be wrong. The extent to which these things are supported on FreeBSD (that is running Xendian host with Yendian bus) is in the bus layer. Nothing does the conversion now. I disagree with Justin because of one thing he said: "PCI is LE". None of the drivers in the tree right now assure that they data they write to the bus is LE. They just call bus_space_write (or in extremely lame cases like the cardbus bridge code, write directly to the memory mapped area with *(foo->offset) = 0x12345678;). NetBSD does this fairly well right now, so I don't think that the confusion that Justin is worried about exists there. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message