David Dawes writes:
On Fri, Nov 07, 2003 at 02:39:49PM -0800, Jon Smirl wrote:
I should be more specific, it's mapping the ROM into PCI space that the kernel
doesn't know about. Of course the kernel knows about the mapping from PCI space
to user space. During a hotplug event the kernel
I should be more specific, it's mapping the ROM into PCI space that the kernel
doesn't know about. Of course the kernel knows about the mapping from PCI space
to user space. During a hotplug event the kernel could map the new device on top
of the ROM in PCI space.
--- Jon Smirl [EMAIL PROTECTED]
On Fri, 7 Nov 2003, Jon Smirl wrote:
I should be more specific, it's mapping the ROM into PCI space that the kernel
doesn't know about. Of course the kernel knows about the mapping from PCI space
to user space. During a hotplug event the kernel could map the new device on top
of the ROM in
On Fri, Nov 07, 2003 at 02:39:49PM -0800, Jon Smirl wrote:
I should be more specific, it's mapping the ROM into PCI space that the kernel
doesn't know about. Of course the kernel knows about the mapping from PCI space
to user space. During a hotplug event the kernel could map the new device on top
I'm working on a function like the one below for copying out the VBIOS ROM. This
would make a good candidate for a device indepenent DRM IOCTL (with a callout
for the bug fix). This is something that really should be fixed in X. Mapping
the ROM in from user space without the kernel's knowledge is
