Date: Fri, 14 Jan 2011 13:12:41 -0800 From: Kevin Baxter <voidchicken@gmail.com> To: Andrew Gallatin <gallatin@gmail.com> Cc: freebsd-multimedia@freebsd.org, Luigi Rizzo <rizzo@iet.unipi.it> Subject: Re: Webcamd and the au0828 Message-ID: <AANLkTik_eRjDJQtzSFDMYi__VF62ExhTfGanTaf8M4oH@mail.gmail.com> In-Reply-To: <AANLkTimuwZ8389=FUCiFKLxf6AnbiCN=fRvhJrnGUKZB@mail.gmail.com> References: <AANLkTin7M7H2X0zj3p6Rp2PMEZ2GsUrbohqwm1CKvwmd@mail.gmail.com> <20110113234339.GA52146@onelab2.iet.unipi.it> <AANLkTimuwZ8389=FUCiFKLxf6AnbiCN=fRvhJrnGUKZB@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 13, 2011 at 6:49 PM, Andrew Gallatin <gallatin@gmail.com> wrote: > On Thu, Jan 13, 2011 at 6:43 PM, Luigi Rizzo <rizzo@iet.unipi.it> wrote: > > > you prompted me to try the same for em28xx, so i followed a similar > route: > > Try using webcamd from the Hans' SVN, not from ports. Hans & I got > em28xx working earlier this week. I tripped over a SEGV like the OP > describes, and Hans fixed it. For at least my em28xx stick, it is > working well. > > Drew > Like I accidentally replied to only Andrew, yes the svn fixed the dev->driver issue already. An upstream driver change broke the dw2102.c compilation, so I commented it out. Now it detects the stick and populates /dev, so far so good. But it still doesn't want to work. pwcview gives me: Webcam set to: 320x240 (sif) at 5 fps libv4l2: error queuing buf 0: Invalid argument libv4l2: error queuing buf 1: Invalid argument libv4l2: error queuing buf 2: Invalid argument libv4l2: error queuing buf 3: Invalid argument libv4l2: error reading: Device busy Error reading from webcam: Device busy and xawtv can't use directvideo. It probably doesn't like my radeon. Leaving only the behemoth that is MythTV to diagnose. It sees the input source, but a channel scan fails to find anything. The webcamd debug log: Linux video capture interface: v2.00 -snip a whole lot of registrations- Attached ugen5.2[0] to cuse unit 0 au0828: i2c bus registered tveeprom 129-0050: Hauppauge model 72001, rev B3F0, serial# 7982575 tveeprom 129-0050: MAC address is 0x7fffffffe855M tveeprom 129-0050: tuner model is Xceive XC5000 (idx 150, type 76) tveeprom 129-0050: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88) tveeprom 129-0050: audio processor is AU8522 (idx 44) tveeprom 129-0050: decoder processor is AU8522 (idx 42) tveeprom 129-0050: has no radio, has IR receiver, has no IR transmitter hauppauge_eeprom: hauppauge eeprom: model=72001 analog subdev registration failed tuner subdev registration fail au8522 129-0047: creating new instance xc5000 129-0061: creating new instance xc5000: Successfully identified at address 0x61 xc5000: Firmware has not been loaded previously DVB: registering new adapter (au0828) DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... Registered device AU0828 [Hauppauge HVR950Q] Creating /dev/video0 Creating /dev/video1 Creating /dev/dvb/adapter0/demux0 Creating /dev/dvb/adapter0/dvr0 Creating /dev/dvb/adapter0/frontend0 and upon channel scanning: 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... I'm not sure what's with the Zu bytes thing. That translates into 0x5a75=21357, or 0x755a=30042 (for endianness), but the actual size of the firmware file is 12401 bytes. Compression? More importantly, there are references to the au8522, which according to the v4l wiki, is the 950Q's A/V decoder. It looks like au8522_decoder.c is needed after all. And the linker wants an implementation of i2c_register_driver and i2c_del_driver. Kevin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik_eRjDJQtzSFDMYi__VF62ExhTfGanTaf8M4oH>