On Fri, 6 Aug 2004, Jon Smirl wrote:
This patch provides a new kernel API for access ROMs from device
drivers. If you're working on a driver that uses the ROM (most video
drivers) please give this patch a try and send some feedback/bugs.
pci_map_rom() - map the rom and provide virtual
Maximum size of a standard PCI ROM is 128KB. On non-x86 platforms the
code will pick the length up from the size of the PCI window. That
window has no limit.
On the other hand, map_rom_copy is only called by the device driver for
a board that has minimal PCI decoding. The PCI spec allows the
Il Sat, Aug 07, 2004 at 07:59:29AM -0700, Jon Smirl ha scritto:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Maximum size of a standard PCI ROM is 128KB.
This is the maximun that kmalloc can allocate.
On non-x86 platforms the code will pick the length up from
All of the video ROMs I have are 48KB - 64KB in size. But, the copy
code is only triggered by the driver for older PCI cards with minimal
decoding. I am unaware of any video cards with this problem so they
won't make the copy. The only cards I seem to recall having this
problem are some older
On Sad, 2004-08-07 at 17:37, Kronos wrote:
You can check and see if the ROM is really big and use vmalloc, if not
then you use kmalloc (if I remember correctly my radeon has a 4KB ROM -
vmalloc would be overkill).
You can also read it out to userspace in a loop in chunks thus needing
only a
--- Alan Cox [EMAIL PROTECTED] wrote:
On Sad, 2004-08-07 at 17:37, Kronos wrote:
You can check and see if the ROM is really big and use vmalloc, if
not
then you use kmalloc (if I remember correctly my radeon has a 4KB
ROM -
vmalloc would be overkill).
You can also read it out to
On Sad, 2004-08-07 at 18:40, Jon Smirl wrote:
We have to copy the whole thing when the driver tells us to. After we
copy the ROM the hardware is going to use the address decoder for
something else. There is no safe way to get back to the ROM again other
than to unload the device driver.
Good
