On Mon, Dec 24, 2007 at 10:29:09AM -0500, Jeffrey J. Kosowsky wrote: > Axel, > I know that you currently have a gspcav1-kmdl to support certain v4l > drivers and have others in the video4linux-kmdl. > > Any possibility of including other non-included v4l modules such as > uvc either as a standalone rpm or as part of one of the existing v4l > kmdls?
Sure. > I could imagine eventually moving to perhaps two kmdls. > - video4linux-kmdl which would include updated versions of the > standard kernel kmdls > > - video4linux-other-kmdl which would include modules for other > non-kernel included v4l drivers, including gspcav1 (which would be > folded in), uvc, and any other ones that meet your user needs. "video4linux" is kind of a trademark in this case, e.g. it is the set of drivers shipped by the merged v4l/dvb project, no more no less. Everything else is shipped with the upstream project name, e.g. gspca contains all drivers shipped by gspca (mostly webcam drivers) and the like. If there is a standalone project, then the kmdl would be named like the project is named or like the tarball is named. E.g. ATrpms does not name a collection of some drivers "v4l-extra" or something else to avoid confusion with users. For uvc I would just name it "uvc". Also note that all these projects *may* have different versioning and release cycles so merging them on a donwstream level is a bit difficult (v4l hasn't had a release in years though, e.g. ever since Gerd left maintenance of the v4l subsystem). In short: Go ahead and package uvc! I'll gladly help to iron out anything that isn't clear. I'd start with gspcav1 as a template as v4l kmdls have a long history and carry a lot of legacy constructs. -- Axel.Thimm at ATrpms.net
pgpy1hrSGZIwM.pgp
Description: PGP signature
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
