On Tue, Jul 22, 2008 at 2:54 PM, Jelle de Jong <[EMAIL PROTECTED]> wrote: > Markus Rechberger wrote: >> >> On Tue, Jul 22, 2008 at 2:37 PM, Jelle de Jong >> <[EMAIL PROTECTED]> wrote: >>> >>> Markus Rechberger wrote: >>>> >>>> Hi Jelle, >>>> >>>> On Tue, Jul 22, 2008 at 9:26 AM, Jelle de Jong >>>> <[EMAIL PROTECTED]> wrote: >>>> Hi Markus, >>>> >>>> I am happy to see process is continuously made with the em28xx drivers. >>>> So thumbs up for the work. I am only a bid worried about the chosen >>>> development forking strategy. I know there has been previous attempts to >>>> merge with the upstream v4l project but so far its still a fork. >>>> >>>> This makes me wonder what the plans and status is with merging back >>>> upstream and what the community can do to help you with this? >>>> >>>>> Nima Paknejad is preparing a patch for the git repository, although I >>>>> will keep the development as it is. It's much more comfotable to have >>>>> it split out for the ongoing development. >>>>> As seen with the latest B2C0/drx3975d device also in future it needs >>>>> some careful testing. There are still a few things todo in order to >>>>> get the critical setup of all devices right. >>>>> Markus >>> >>> It would be great for lowering the entry level for developers, users and >>> maintainers when v4l and em28xx are using the same code repository, >>> naturally a personal branch of this shared repository for testing and >>> develop is feasible, and this makes it possible to merge some stable >>> files >>> back to the main trunk so it will be included with the upstream Linux >>> kernel >>> (v4l) and all distributions shipping v4l. >> >> this is what Nima is on. >> >>> If the above is not possible, then its maybe an idea to change the >>> v4l-devel >>> package so that the build process of the em28xx-new drivers will not >>> depend >>> on the kernel-source, but only development header files? >>> >> the kernel headers are usually part of the linux kernel source, it's >> up to the distributor to not include everything. >> >> Markus > > A nice, thats good news, thumps up for the merging work. Can we assume > the mering will be intergrated in the current em28xx development process? >
the upstream pushes very likely, as for development the repository will be kept extra, especially since for the target applications not everything is required usually. Markus > Lets hope users can use there em28xx devices out of the box soon after a > new kernel updated with the merged code. > > Keep up the great development > > Kind regards, > > Jelle > > > _______________________________________________ > Em28xx mailing list > [email protected] > http://mcentral.de/mailman/listinfo/em28xx > _______________________________________________ Em28xx mailing list [email protected] http://mcentral.de/mailman/listinfo/em28xx
