On Freitag, 14. Oktober 2005 14:55, Nicolas Huillard wrote: > Denis Oliver Kropp a écrit : > > Quoting Mark Adams: > > > >>>IIRC it still needs a cleanup. > >> > >>It does -- we were going to try to move to the VIA version of viafb > >>and then add a new all-encompasing vsync ioctl. Where did that get > >>to? > > > > I got a bit demotivated by the mpeg hack and distracted by other work, > > Well, I quite understood your situation. > > > but let's begin with that. What about adding the latest viafb to the > > DirectFB CVS and hacking on it together? Anybody willing to help can > > get cvs access. > > The fast and easy way is to update DirectFB's CVS with patcher2k/Rolf's > code, and update that, since a lot of work has been done on it, and > everyone there uses this one, and VIA's code has a lot *still* to be done. > > 0) decide how viafb should be added to CVS : I personally like the patch > way adopted by André Krein on patcher2k. Any other way allowing to > easily develop, commit and package the driver will suit me. > 1) take Rolf's patch and add it to CVS
My wish in that case is: provide this driver in a way that it could be build outside the kernel tree (like dvb drivers) so there would be no need to patch and revert patch, .. . > 2) provide a CVS nightly snapshot like other projects > 3) provide CVS access to developers (I have a VT1622 tuning to add, and > maybe code for hardware cursor handling, if not already there) > 4) release this driver like DirectFB is released (maybe in synch with > DirectFB) > 5) when all this is in place, there is a chance the driver will finally > reach the official kernel tree > -- Stefan Lucke _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
