[linux-dvb] LifeView TV Walker - Model LR506

Aapo Tahkola aet at rasterburn.org
Wed Jun 27 19:41:03 CEST 2007


On Wed, 20 Jun 2007 14:14:14 +0200
"Daniel Weigl" <danielweigl at gmx.at> wrote:

> Hello Nick,
> 
> Thx for your replies!
> 

Take a look at
http://www.rasterburn.org/~aet/m920x/m920x-twalker-rl506.patch
This driver should not belong to m920x.c since it's not based on m920x
(noticed that afterwards).

Couple notes:
- m920x_identify_state will most likely not work for your device
- m920x_firmware_download routine should not be used for this
device(assuming you have to dl firmware)
- you need to make sure adapter field of tvwalker_lr506_properties is
properly filled

You can examine other drivers that use CY7C68013A(FX2) to figure out
what still needs to be done.

Couple pointers:
19:30 < mkrufky> most likely, the dvb-usb-firmware's default
CYPRESS_FX2 handling should do the job

19:31 < mkrufky> you may want to
look at the FIRST entry in cxusb, for the medion 95700, for an example
of what a typical dvb_usb_device_properties struct looks like for an
FX2 device

19:31 < mkrufky> (dont look at the bluebird ones -- we had
to override the firmware download routing with a USB PID firmware patch)

> > Are you able to open it up and find out
> > what chips are inside?
> Okay... I already posted some bits about it in my first post - but
> this may be a bit messy... english is not my native language. So here
> are the ICs I have found inside:
> 
> On the Top (or I just call it top)
> 	Phillips 8275AC1
> 	CY7C68013A (Cypress?)
> And on the bottom:
> 	TDA1004GHT SA1371.1
> Additionally ther is also a small 8pin SMD chip, where I cant read
> the number/id, because ther is a blue color-spot on it. Maybe it is a
> i2c (or 1-wire or similiar) flash, which stores the firmware? So that
> ther is no download needed at all... But Iam just guessing right into
> the blue.
> 
> I have made some pictures of the device (and its inside), you can
> find it under:
>    http://danyserv.selfip.org/pic/thumbnails.php?album=27
> 
> > You should try to extract your device's firmware from that dvbsnoop
> > output so you won't be dependent on Windows when you get the device
> > working.
> Oh... did i write _dvb_snoop... of course i meant _usb_snoop... sorry
> for that, but i guess you thought the same thing, i was meaning.
> 
> Okay, I will try, but I have no (deeper) experiences with USB nor  
> DVB(-drivers), so Iam not sure, if ill get anything :)
> 
> >>   The logfile: http://nopaste.info/eead046817.html
> > I couldn't download this; it is wrapped in HTML.
> Okay, here i have it as plaintext again:
> I started the usbsnoop
> ( http://benoit.papillault.free.fr/usbsnoop/ ) befor i connected the
> stick and stoped it some seconds after i had plugged it in.
> 
> The log file can be found under:
> 	http://danyserv.selfip.org/dir/LifeView/usbsnoop.log  (~600kb)
> 
> I made a second log, which includes the plugin and the start of the  
> DVB-App and some seconds of the TV-stream:
> 	http://danyserv.selfip.org/dir/LifeView/usbsnoop_tv.log.bz2
> (~200kb) (I truncated the log after some big packets, bec. the whole
> log had ~200MiB)
> 
> So, thats all for now, i thank you for any help you (or anybody else)
> can provide.
> 
> Daniel Weigl
> 
> 


-- 
Aapo Tahkola



More information about the linux-dvb mailing list