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 address, transparently
> return shadow/copy if needed. Normal drivers call this
>
> pci_map_rom_copy() - same as pci_map_rom except the ROM will copied,
> future reads of ROM will use copy. Hardware with minimal decoding calls
> use this
>
> pci_unmap_rom() - release the ioremap if there is one
>
> The ROMs also appear in sysfs and you can use hexdump to see them.
>
> If the Radeon ROM is all FFFF. Load a radeon device driver and it will
> appear. Radeon cards have a bug that loading the driver will fix.
> +unsigned char *
> +pci_map_rom_copy(struct pci_dev *dev, size_t *size) {
> + struct resource *res = &dev->resource[PCI_ROM_RESOURCE];
> + unsigned char *rom;
> +
> + rom = pci_map_rom(dev, size);
> + if (!rom)
> + return NULL;
> +
> + if (res->flags & (PCI_ROM_COPY | PCI_ROM_SHADOW))
> + return rom;
> +
> + res->start = (unsigned long)kmalloc(*size, GFP_KERNEL);
What's the maximum size of a PCI ROM? Larger than kmalloc() can handle?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
