On Fri, Feb 06, 2004 at 02:31:56PM +0100, Michel D�nzer wrote: > On Fri, 2004-02-06 at 14:39, Sven Luther wrote: > > On Fri, Feb 06, 2004 at 12:24:25AM +0100, Michel D�nzer wrote: > > > On Thu, 2004-02-05 at 17:19, Sven Luther wrote: > > > > On Thu, Feb 05, 2004 at 04:14:03PM +0100, Michel D�nzer wrote: > > > > > On Thu, 2004-02-05 at 17:03, Sven Luther wrote: > > > > > > > > > > > > BTW, is the fbdev driver supposed to be working with the dri-trunk > > > > > > server ? > > > > > > > > > > What for? It obviously doesn't support the DRI, so > > > > > xserver-xfree86-dri-trunk doesn't ship it. > > > > > > > > Yeah, that is what i thought also, but it is usefull for debuging > > > > purpose and such. Especially if for whatever reason the normal driver is > > > > messed up, to have at least a working setup. > > > > > > You can always use (parts of) xserver-xfree86 in that case? *shrug* > > > > Yeah, but the dri alternative magic makes this not possible. > > How so? (There's no 'alternative magic', do you mean the diversion?) You > can > > * use XFree86.nodri-trunk > * ln -s /usr/X11R6/lib/modules/drivers/fbdev_drv.o > /usr/X11R6/lib/modules-dri-trunk/drivers/ > * ...
You mean, there should be no problem in running the 4.3.0 fbdev driver in the dri-trunk one ? If so, should you not be creating symlinks for all the missing modules or something ? Anyway, as said, it was just a curiosity, not a real problem. Friendly, Sven Luther
