tm6000/tm6010 progress?
Hello,
I am willing to help the devel opment of tm6000/tm6010 drivers as I am a "happy" owner of Freecom Hybrid USB stick (14aa:0620 AVerMedia (again) or C&E). Last entry in tm6010mercurial is 5 month ago and I cannot compile the tm6010 tree.
I am computer science student so I might be able to help with driver development although I have close to no experience in this area. I will sure be able to help testing drivers on my hardware.
The question is, what is the progress and status of tm6010 development? I am particulary interested in analog an remote control status.
regards,
Erik Boritsch
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 6 lines · On Fri, 24 Oct 2008 14:41:40 +0200 Erik Boritsch <[email protected]> wrote:
Hello,
I am willing to help the devel opment of tm6000/tm6010 drivers as I am a "happy" owner of Freecom Hybrid USB stick (14aa:0620 AVerMedia (again) or C&E). Last entry in tm6010mercurial is 5 month ago and I cannot compile the tm6010 tree.
I passed to a period of time were I couldn't dedicate to it. Let's see if I would have more time those days.
Quoted 3 lines
I am computer science student so I might be able to help with driver development although I have close to no experience in this area. I will sure be able to help testing drivers on my hardware.
Any help is welcome.
Quoted 3 lines
The question is, what is the progress and status of tm6010 development? I am particulary interested in analog an remote control status.
Analog:
There's a serious bug at URB decoding routines, causing kernel Panic, caused by one of my trials to avoid loosing parts of the URB's. I didn't have time yet to track where the problem is.
IR: There's no IR code yet. This chip doesn't support the standard way to probe devices at I2C bus. The better would be to convert it to the new i2c way, where the driver knows what devices are at what addresses. With this change, it shouldn't be hard to implement IR support.
Cheers,
Mauro
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 1225191933.8398.40.camel@uvdr
Hi Eddi,
Quoted 13 lines · On Tue, 28 Oct 2008 12:05:33 +0100 Eddi De Pieri <[email protected]> wrote:
I report you some problem:
With DVB support active build fail on tm6000-dvb.o
CC [M] /data/devel/tm6010/v4l/tm6000-dvb.o
/data/devel/tm6010/v4l/tm6000-dvb.c: In function 'tm6000_dvb_register':
/data/devel/tm6010/v4l/tm6000-dvb.c:240: error: unknown field 'video_dev' specified in initializer /data/devel/tm6010/v4l/tm6000-dvb.c:240: warning: initialization makes integer from pointer without a castI've tried changing the line..
(quoted diff) +1
-1- .video_dev = dev, + .i2c_addr = 0x61,
Quoted 1 line
Now it build but the decoder is not detected.
Hmm.. Ok, I'll check this.
The DVB part deserves some work. I'm currently trying to fix the streaming routine to use the same model for DVB as we did on em28xx-dvb.
Quoted 7 lines
insmod tm6000-alsa.ko
insmod: error inserting 'tm6000-alsa.ko': -1 Unknown symbol in module# dmesg [ 1785.667726] tm6000_alsa: Unknown symbol tm6000_get_reg [ 1785.667930] tm6000_alsa: Unknown symbol tm6000_set_reg
tm6000-alsa is just a cleaned copy of the dummy alsa prototype. It never worked. I need first to have the streaming routines working fine for making the binding between stream reception and audio.
Quoted 2 lines
Without dvb it build but mplayer show green screen and no image.
One of the hardest part of tm6000 is the streaming decoding. If you take a look at the history, most of the latest patches were meant to fix streaming reception.
On analog mode, tm6000 produces frames with 180 bytes wide. The 3rd byte is the header identifier (why they didn't use the first byte?). since the frames are broken into several URB's, and even can be broken into different URB sets, a complex logic is required to avoid double-buffering and to recover the original image. That part of the code is currently broken. It used to work in the past, but, on some cases, I was losing some URB's, causing very bad effects at the image. We need this fixed in order to have the driver properly working.
Cheers,
Mauro
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb