It seams that pci_find_device, that DRI uses, has been replaced. This really doesn't
affect DRI
but it's new and the Linux driver would more closely resemble the BSD one once were
doing things
the new way. Also this will pave the road for my next big idea, changing the card%d
device names
to something more use full. I think it would be best If we used busid_string, this
way the
Xserver can just open the busid that's in the Device section and away it goes, no more
unique
kludge. Then why not have the kernel tell the xserver what to do, making the device
section
optional(A bit of sarcasm hear). There are a lot of things that could be done, but I
think in the
end slow and steady will win the race.
The only problem might be that the structures that BSD and Linux use are slightly
different. It
seams thought that the BSD one is defined as belonging to dri, in that we can change
it. I'm
going to sync drm_bsd with linux, and hope BSD will live.
Linux(from the core kernel include/linux/pci.h)
struct pci_device_id {
unsigned int vendor, device; /* Vendor and device ID or PCI_ANY_ID */
unsigned int subvendor, subdevice; /* Subsystem ID's or PCI_ANY_ID */
unsigned int class, class_mask; /* (class,subclass,prog-if) triplet */
unsigned long driver_data; /* Data private to the driver */
};
BSD(from drm_os_{free,net}bsd.h)
struct drm_chipinfo
{
int vendor;
int device;
int supported;
char *name;
};
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
