On Tue, 2002-07-09 at 18:29, Mike Mestnik wrote: > I'v looked into this, it seams that the tdfx driver dose something simular to >FreeBSD. The code > in drm_drv.h could be adapted to create the device nodes, via devfs. The current >linux setup just > allocates 1 minor number, more is supported by drm_drv.h but only the tdfx makes use >of this. I > can easily add the call to devfs, but I wonder if I shouldn't fix it up right. I'm >planing on > making the linux&bsd structures the same, this adds bloat to linux but it's not too >bad. Then I > could place all the PCI ids in the shared dir, where should thay go (*_drv.h)? I'm >planing on > having DRISUP_BOTH, DRISUP_BSD, DRISUP_LINUX, DRISUP_NONE defined for the 3rd >element. Later > something like DRISUPPORTED(bsd,linux,ect...) can be implemented for more OSes. Is >there any > thing special I should do, if I put data/code in a .h file? Is there any thing else >I should be > aware of?
*_drv.h would be the place to put the stuff. You could probably skip the DRISUP_<OS> -- if the driver's supported it'll be hooked into the build system for the OS (NetBSD and FreeBSD will have the DRM in the kernel, or driver-specific makefiles). However, having a way of turning the support for a pci id off depending on the os's support or compile options would be good (depending on __REALLY_HAVE_SG, __REALLY_HAVE_AGP etc). -- Eric Anholt <[EMAIL PROTECTED]> http://people.freebsd.org/~anholt/dri/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
