Thanks for the reply Sven,

I guess the main problem right now, is that a pwc-modules package and a 
linux-2.6 package will both ship a pwc.ko, but in different locations.

Is there a automatic way, using inst or rm scripts in the packaging, to 
dpkg-divert the kernel pwc.ko with the pwc-modules one? Basically is there a 
variable that, at build time, will be automatically replaced with the kernel 
version ( output same as 'uname -r' i guess??)?

Thanks
Lawrence

On Tuesday 10 January 2006 03:35, Sven Luther wrote:
> On Tue, Jan 10, 2006 at 01:31:50AM -0330, Lawrence Williams wrote:
> > Package: linux-2.6
> > Severity: important
> >
> > Hi,
> >
> > I am asking for the in-kernel pwc module (Philips USB webcam) to be
> > disabled by default, as it doesn't work with the majority of their webcam
> > chipsets
>
> Nope wrong, they just don't uncompress the data flow, which should be
> uncompressed in userland. The problem is that none of the userland tools do
> this yet.
>
> > commonly in use. More importantly, it also conflicts with the resulting
> > package built from the source contained in the pwc-source package (two
> > different pwc.ko files placed in 2 different modules dir for the same
> > kernel version... during modprobe, kernel picks their version always ).
>
> The third-party pwc module is supposed to provide pre-built modules for
> official kernels, which do the right with regard to packaging and diverts
> the kernel pwc module so everything works fine. If this is not the case,
> then it is a pwc bug, but i believe this not to be the case.
>
> > It would save pwc users alot of time, as no kernel rebuild would be
> > needed, and a pwc-modules package could work from a fresh install :)
>
> Just install the right package should do the trick. Having a userland
> library for uncompressing the data from the kernel pwc module and passing
> it transparently to the other userland apps would be the better solution
> though, not sure how this works though.
>
> Friendly,
>
> Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to