> I had a good fix for this in one of my patches. Only BSD needs the names > but both need the IDs and linux even had a hotplug struct. This was geard > and enginered with both OSes being treated as eaquils and other OSes made > easy to acommidate. What I did was had some macroes that took paramiters > and filled ought the struct depending on what OS the macro came from. I > put this all in <radeon>.h inside a ifdeine PCIID_STRUCT that only got > deffined in the <radeon>.c right b4 the include. Thought this info dose > not have to live in the headers I thouht it just looked nicer that way. >
what I'd like is a way to just put the strings into the BSD driver, but also so that the strings wouldn't have to be merged up to the kernel at all, maybe a patch with the strings in it might be accepted if they aren't built into the binary but I'd rather they never went near the kernel, I'm trying to think of someway to do it with macros... I don't really want to have to add the pci ids to two places, perhaps we could use an external script to take a list of pci ids from a file and create a suitable .h for Linux and BSD in the build system, then we can merge the Linux ones up to the kernel.... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- 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