Date: Wed, 26 Jan 2011 17:32:24 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: Andrew Gallatin <gallatin@gmail.com> Cc: freebsd-multimedia@freebsd.org Subject: Re: webcamd: PCTV 801eSE Message-ID: <201101261732.24928.hselasky@c2i.net> In-Reply-To: <AANLkTi=776r2hRb_dw2vVPz1roV5bgikSqp=XYQy6Gfk@mail.gmail.com> References: <AANLkTinh7mA5jrr1240LnOSGL37yzb2uW_yWZfBD5cpa@mail.gmail.com> <201101260901.19745.hselasky@c2i.net> <AANLkTi=776r2hRb_dw2vVPz1roV5bgikSqp=XYQy6Gfk@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 26 January 2011 17:14:21 Andrew Gallatin wrote: > On Wed, Jan 26, 2011 at 3:01 AM, Hans Petter Selasky <hselasky@c2i.net> wrote: > > Try to check the USB buffer size: > > Hi, > > #define DIB0700_DEFAULT_STREAMING_CONFIG(ep) \ > > That seems to have been it! I used the attached patch, and now the > picture is clear from stations 100km away, where it was unusable on > stations 25km away before. > > Is there some difference between the Linux & FreeBSD USB systems that > Linux is able to handle non-512 byte multiples? I think linux maybe handles this case differently. The issue is that USB is packet based, and there is no FIFO to fixup partly received packets. Linux should have this patch aswell! But probably better, one layer up, in the DVB layer which parses this structure. In r1711 I've updated "patches/do_patch.sh" to include your patch! > > I still have the occasional error messages: > > > xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)... > Loading firmware at '/boot/modules/dvb-fe-xc5000-1.6.114.fw', f=7 > xc5000: firmware read Zu bytes. > xc5000: firmware uploading... > xc5000: firmware upload complete... > dib0700: i2c write error (status = -32) > > s5h1411_readreg: readreg error (ret == 0) > dib0700: i2c write error (status = -32) > > s5h1411_readreg: readreg error (ret == 0) > xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)... > Loading firmware at '/boot/modules/dvb-fe-xc5000-1.6.114.fw', f=7 > xc5000: firmware read Zu bytes. > xc5000: firmware uploading... > xc5000: firmware upload complete... > dib0700: i2c write error (status = -32) > > s5h1411_readreg: readreg error (ret == 0) > dib0700: i2c write error (status = -32) > > s5h1411_readreg: readreg error (ret == 0) > <...> > > Should I be concerned? If the functionality is OK, I would not worry. I think -32 means EPIPE which means STALL. That means that the driver most likely is writing a non-supported register. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101261732.24928.hselasky>