From: nizar <nizar.saied@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: [linux-dvb] technisat skystar usb 2.0
Date: Tue, 21 Apr 2009 12:32:56 +0200 [thread overview]
Message-ID: <gskaq4$s1$1@ger.gmane.org> (raw)
In-Reply-To: <200904151251.09812.railis@juvepoland.com>
Dominik Sito wrote:
> Monday 13 April 2009 17:31:29 nizar napisał(a):
>> Please help needed.
>> I have skystar usb 2.0 (13d0:2282) i have also the log of usbsnoop
> (300
>> Mo) .
>> What are steps to :
>>
>> 1- know if a firmware is needed.
>> 2- if yes how to extract it.
>>
>>
>> thank you
>> Nizar
>>
>>
>> _______________________________________________
>> linux-dvb users mailing list
>> For V4L/DVB development, please use instead linux-
> media@vger.kernel.org
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
> Just give `lspci -vvv` and `lsusb -vvv` result.
> Regards.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hi Dominik
I have send the lspci and lsusb.
I think that b2c2-flexcop-usb.c dont handle usb2.0
So if I suppose that the frontend is the same as those of skystar 2 pci
the main tasks are :
-1- Find the firmware of the pci-to-usb controller (Net ship 2282)
-2- Change the b2c2-flexcop-usb.c to work with usb2.0 (bulk urb).
result :
-1- ====> Try to extract the firmware from the usbsnoop.log
-2- ====> Not too hard.I trying to write b2c2-flexcop-usb2.c
Thank you.
Nizar Saied
prev parent reply other threads:[~2009-04-21 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 15:31 [linux-dvb] technisat skystar usb 2.0 nizar
2009-04-15 10:51 ` Dominik Sito
2009-04-15 11:27 ` nizar
2009-04-21 10:32 ` nizar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gskaq4$s1$1@ger.gmane.org' \
--to=nizar.saied@gmail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox