linux-mips
[Top] [All Lists]

Re: Legacy PCI IO for PCI graphics on SGI O2...Anybody?

To: sknauert@wesleyan.edu
Subject: Re: Legacy PCI IO for PCI graphics on SGI O2...Anybody?
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Fri, 22 Jun 2007 15:06:24 +0100 (BST)
Cc: linux-mips@linux-mips.org
In-reply-to: <53391.129.133.92.31.1182519298.squirrel@webmail.wesleyan.edu>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <54672.129.133.92.31.1182184357.squirrel@webmail.wesleyan.edu> <20070619.121030.130240189.nemoto@toshiba-tops.co.jp> <Pine.LNX.4.64N.0706191246060.15474@blysk.ds.pg.gda.pl> <20070620.012206.30438292.anemo@mba.ocn.ne.jp> <53391.129.133.92.31.1182519298.squirrel@webmail.wesleyan.edu>
Sender: linux-mips-bounce@linux-mips.org
On Fri, 22 Jun 2007, sknauert@wesleyan.edu wrote:

> > Oh I thought ioperm() or iopl() on archs other then x86 are all dummy
> > routines, but apparently that was wrong.  Now I have looked some
> > ioperm.c in glibc and am very suprised by so many hard-coded
> > boardname/addresses ;)
> >
> 
> This seems like a mistake, shouldn't the hardware specific chunks be in
> the kernel?

 No particular need for this -- libc is a part of the operating system 
API.  Anything below this API is up to the system implementation and the 
more bits moved to the userland the better.

  Maciej

<Prev in Thread] Current Thread [Next in Thread>