From: Andreas Kemnade <andreas@kemnade.info>
To: Andreas Kemnade <andreas@kemnade.info>,
linux-media@vger.kernel.org, mchehab@kernel.org
Subject: Re: [PATCH RFC] dvb: af9035.c: Logilink vg0022a to device id table
Date: Tue, 14 Mar 2017 07:26:21 +0100 [thread overview]
Message-ID: <20170314072621.2b81c73f@aktux> (raw)
In-Reply-To: <1489078274-24227-1-git-send-email-andreas@kemnade.info>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
On Thu, 9 Mar 2017 17:51:14 +0100
Andreas Kemnade <andreas@kemnade.info> wrote:
> Ths adds the logilink VG00022a dvb-t dongle to the device table.
> The dongle contains (checked by removing the case)
> IT9303
> SI2168
> 214730
>
> The result is in cold state:
>
> usb 1-6: new high-speed USB device number 15 using xhci_hcd
> usb 1-6: New USB device found, idVendor=1d19, idProduct=0100
> usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-6: Product: TS Aggregator
> usb 1-6: Manufacturer: ITE Tech., Inc.
> usb 1-6: SerialNumber: XXXXXXXXXXXX
> dvb_usb_af9035 1-6:1.0: prechip_version=83 chip_version=01 chip_type=9306
> dvb_usb_af9035 1-6:1.0: ts mode=5 not supported, defaulting to single tuner mode!
> usb 1-6: dvb_usb_v2: found a 'Logilink VG0022A' in cold state
> usb 1-6: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9303-01.fw'
> dvb_usb_af9035 1-6:1.0: firmware version=1.4.0.0
> usb 1-6: dvb_usb_v2: found a 'Logilink VG0022A' in warm state
> usb 1-6: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
> dvbdev: DVB: registering new adapter (Logilink VG0022A)
> si2168: probe of 6-0067 failed with error -5
>
> when warmed up by connecing it via a powered usb hub to win7 and
> then attaching the same usb hub to a linux machine:
>
with some fixes in af9035.c I already get the same state as with warm
up by win7. I just need to find out which changes are really necessary
and convert it into a clean patch.
> so firmware uploading to the si2168 somehow messes things up
>
I experimented a lot here and I found this:
If 0101 is not sent to the si2168 you can get answers from the
Si2147-A30.
After the 0101 is sent to the si2147-A30 it will still execute
commands but you will not get the answer back through the si2168.
You just get ff.
After moving the chip id readout from si2157_init to si2157_probe,
scanning for stations works. So the si2147-A30 seems to react on
commands.
Regards,
Andreas Kemnade
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-03-14 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 16:51 [PATCH RFC] dvb: af9035.c: Logilink vg0022a to device id table Andreas Kemnade
2017-03-14 6:26 ` Andreas Kemnade [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=20170314072621.2b81c73f@aktux \
--to=andreas@kemnade.info \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).