[lkml]   [2001]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Going beyond 256 PCI buses

Benjamin Herrenschmidt writes:
> Well... that would work for VGA itself (note that this semaphore
> you are talking about should be shared some way with the /proc
> interface so XFree can be properly sync'ed as well).

Once XFree takes ownership of the VC it has control of all the
graphics cards in the system. It does this before it does any poking

> But I still think it may be useful to generalize the idea to
> all kind of legacy IO & PIOs. I definitely agree that VGA is a kind
> of special case, mostly because of the necessary exclusion on
> the VGA IO response.

I don't think this is the way to go.

First, what would you use it for? Let's check some examples:

1) "legacy serial on Super I/O"

This is best handled by a asm/serial.h mechanism, something akin
to how asm/floppy.h works. Let the platform say how to get at
the ports.

Wait, there already is a asm/serial.h that does just this :-)

2) "floppy"

See asm/floppy.h :-)

3) "PS/2 keyboard and mouse"

I believe there is an asm/keyboard.h for the keyboard side of this.
Yes, and it has macros for the register accesses.

4) "legacy keyboard beeper"

Make an asm/kbdbeep.h or something.

Add whatever else you might be interested that things tend to

And if your concern is having multiple of these in your system, the
only ones that make sense are floppy and serial and those are handled
just fine by the asm/serial.h mechanism.

This way of doing this allows 16550's, floppies, etc. to be handled on
any bus whatsoever.

I mean, besides this and VGA what is left and even matters?

David S. Miller

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:55    [W:0.101 / U:2.636 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site