> > > > > > > The whole dependancy seems like nonsense to me. > > I think > > > > depends on PCI > > > > is a lot more sensible. > > I think the original reasoning was something like this: > > If DRM is built-in, then AGP _must_ be built-in or not included at all, > modular > won't work. If DRM is modular or not built, then AGP may be built-in, > modular, > or not built at all. > > The "depends on AGP || AGP=n" means that if DRM=y, then AGP=y or AGP=n, and if > DRM=m or DRM=n, then AGP=y or AGP=m or AGP=n. > > Yes it's unclear and yes it should probably be documented in a comment > somewhere.
What Kyle said is the correct answer... we either keep this lovely construct (I'll add a comment for 2.6.13) or we go back to the old intermodule or module_get stuff... DRM built-in with modular AGP is always wrong... or at least I'll get a hundred e-mails less every month if I say it is .. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
