--- Alexander Stohr <[EMAIL PROTECTED]> wrote: > > I'm planing on > > having DRISUP_BOTH, DRISUP_BSD, DRISUP_LINUX, DRISUP_NONE > > defined for the 3rd element. > > I dont like the "both" thing. The design looks for me rather > like a bitfild than an enum... so this would be the solution: > > (DRISUP_BSD | DRISUP_LINUX) > > a DRISUP_ALL would make more sense, but the cases where it > will apply will not be large, if ever existing. > > > Later something like DRISUPPORTED(bsd,linux,ect...) can be > > implemented for more OSes. > > i am in favour of the basic idea to design a standard way > for determining what specific chips a driver is capable of. > two platforms means portability is mostly solved and its > adoption will rise soon. > > Regards, Alex. > Eric also mentioned that __REALLY_HAVE_SG, __REALLY_HAVE_AGP also can play a role, I'm just going to leave these set to an inline '1', and let the course of time having ppl do things like (!DRISUP_LINUX) if it's ever needed.
__________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com ------------------------------------------------------- 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
