Jeff Garzik writes:
> > For example, S3 cards typically use:
> >
> > 0x0102, 0x42e8, 0x46e8, 0x4ae8, 0x8180 - 0x8200, 0x82e8, 0x86e8,
> > 0x8ae8, 0x8ee8, 0x92e8, 0x96e8, 0x9ae8, 0x9ee8, 0xa2e8, 0xa6e8,
> > 0xaae8, 0xaee8, 0xb2e8, 0xb6e8, 0xbae8, 0xbee8, 0xe2e8,
> > 0xff00 - 0xff44
^^^^ PCI IO addresses
> I tried to push this through when I was hacking heavily on fbdev
> drivers, especially S3, and it didn't fly. On x86's, those addresses
> are already reserved:
No they're not.
> [jgarzik@rum linux_2_4]$ cat /proc/iomem
> 00000000-0009efff : System RAM
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000f0000-000fffff : System ROM
> [...]
^^^^^^^^^^^^^ PCI memory addresses.
> Another alternative I thought of is freeing the resource if it is
> allocated by the system, and having the driver allocate its own
> resource. When the driver unloads, it frees its resources and allocates
> the whole region back to the system. I look at this as the fbdev
> driver's "clarifying the picture" of the hardware resource usage.
If the driver isn't loaded, the port is still used by the hardware. Therefore,
it should be reserved independent of whether we have the driver loaded/in kernel
or not.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Nov 23 2000 - 21:00:13 EST