--- Ian Romanick <[EMAIL PROTECTED]> wrote:
> Can you elaborate? I'm not super familiar with this part of the DRM, so
> I just need a clarification. We're just talking about device
> initialization (i.e., PCI mapping) that the X-server currently does, right?
I'm not proprosing bringing any family specific code into the drivers yet. But
for example there are some radeon bug patches that only need to be applied to
R300 chips.
> I guess I don't understand this. What is the extra data you're
> proposing to encode in the string? Is that analogous to the
> device_private field in my old user-space patch? By that I mean does it
> serve the same purpose?
The last field is the device private field. We can put whatever we want there.
Right now there it is pointing to the device name string. Instead we could make
a pointer to a structure and include the family ID.
If we don't put the family ID into the structure you have to write a great big
case statement with all of the PCI IDs to compute it. It's less memory to put it
in the structure.
>From linux kernel....
struct pci_device_id {
__u32 vendor, device; /* Vendor and device ID or PCI_ANY_ID*/
__u32 subvendor, subdevice; /* Subsystem ID's or PCI_ANY_ID */
__u32 class, class_mask; /* (class,subclass,prog-if) triplet */
kernel_ulong_t driver_data; /* Data private to the driver */
};
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
