AverTV_A918R (af9035-af9033-tda18218) / patch proposal

AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

Hi all,

After struggling some days trying to wake up a AVerTV_HD_Express_A918R  
DVB-T card, I am stuck with a DMX_SET_PES_FILTER error reported by  
dvbsnoop, I cannot solve (beyond my skills).
This card is based on Afatech AF9035 +  AF9033 + NXP TDA18218HN, and then  
very similar to AVerTV_Volar_HD_PRO_A835 (in term of components used).

You will find all details and current state at:
http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_HD_Express_A918R

In the meantime, I propose following patches to get dvb_usb_af9035  
compatible with A918R.
--------------------------------------------------------------------------------------
--- /drivers/media/dvb-core/dvb-usb-ids.h
+++ /drivers/media/dvb-core/dvb-usb-ids.h
   @@ -233,6 +233,7 @@
   #define USB_PID_AVERMEDIA_A835                         0xa835
   #define USB_PID_AVERMEDIA_B835                         0xb835
  +#define USB_PID_AVERMEDIA_A918R                      0x0918
   #define USB_PID_AVERMEDIA_1867                         0x1867
   #define USB_PID_AVERMEDIA_A867                         0xa867
--------------------------------------------------------------------------------------
  --- /drivers/media/usb/dvb-usb-v2/af9035.c
  +++ /drivers/media/usb/dvb-usb-v2/af9035.c
  @@ -1125,6 +1125,8 @@
          { DVB_USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_B835,
                &af9035_props, "AVerMedia AVerTV Volar HD/PRO (A835)",  
NULL) },
  +       { DVB_USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_A918R,
  +             &af9035_props, "AVerMedia AverTV (A918R)", NULL) },
          { DVB_USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_1867,
                &af9035_props, "AVerMedia HD Volar (A867)", NULL) },
--------------------------------------------------------------------------------------
If someone has some ideas to solve/understand the DMX_SET_PES_FILTER  
issue, please feel free to advise what should be tested or modified.
Thanks, and ... Happy New Year !
Diorser.

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Antti Palosaari]

On 01/01/2013 11:40 PM, Diorser wrote:
> Hi all,
>
> After struggling some days trying to wake up a AVerTV_HD_Express_A918R
> DVB-T card, I am stuck with a DMX_SET_PES_FILTER error reported by
> dvbsnoop, I cannot solve (beyond my skills).
> This card is based on Afatech AF9035 +  AF9033 + NXP TDA18218HN, and
> then very similar to AVerTV_Volar_HD_PRO_A835 (in term of components used).
>
> You will find all details and current state at:
> http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_HD_Express_A918R
>
> In the meantime, I propose following patches to get dvb_usb_af9035
> compatible with A918R.
> --------------------------------------------------------------------------------------
>
> --- /drivers/media/dvb-core/dvb-usb-ids.h
> +++ /drivers/media/dvb-core/dvb-usb-ids.h
>    @@ -233,6 +233,7 @@
>    #define USB_PID_AVERMEDIA_A835                         0xa835
>    #define USB_PID_AVERMEDIA_B835                         0xb835
>   +#define USB_PID_AVERMEDIA_A918R                      0x0918
>    #define USB_PID_AVERMEDIA_1867                         0x1867
>    #define USB_PID_AVERMEDIA_A867                         0xa867
> --------------------------------------------------------------------------------------
>
>   --- /drivers/media/usb/dvb-usb-v2/af9035.c
>   +++ /drivers/media/usb/dvb-usb-v2/af9035.c
>   @@ -1125,6 +1125,8 @@
>           { DVB_USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_B835,
>                 &af9035_props, "AVerMedia AVerTV Volar HD/PRO (A835)",
> NULL) },
>   +       { DVB_USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_A918R,
>   +             &af9035_props, "AVerMedia AverTV (A918R)", NULL) },
>           { DVB_USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_1867,
>                 &af9035_props, "AVerMedia HD Volar (A867)", NULL) },
> --------------------------------------------------------------------------------------
>
> If someone has some ideas to solve/understand the DMX_SET_PES_FILTER
> issue, please feel free to advise what should be tested or modified.

Patch looks correct.

If you are talking of that error I saw wiki you mentioned it is not 
error. You cannot use dvbsnoop like that. You have to tune to channel 
first and only after device is tuned successfully pidscan is possible.

  # dvbsnoop -s pidscan
  dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/
  Transponder PID-Scan...
  Error(22): DMX_SET_PES_FILTER: Invalid argument

If you are really sure your antenna is good (not that small antenna 
bundled) and it does not work then there is some bug. I bet some GPIO is 
wrong. Maybe you should take some sniffs using SniffUSB2.0 and look there...


> Thanks, and ... Happy New Year !
> Diorser.

regards
Antti

-- 
http://palosaari.fi/

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

Thanks for your so fast reply.
Unfortunately, scanning output is always empty with 100% signal strength   
(external antenna)
I also use a AverTV super_007 with the same external antenna on a  another  
PC with Kaffeine =Signal = 100%.

I also tried different dvb-usb-af9035-02.fw  firmware with different   
LINK/OFDM value (I don't understand but just tried.).
Never got any PID or channel.
Scanning and tuning work (or seem to with w_scan or kaffeine), but no   
data output.

I've noticed that videobuf_dvb and videobuf_dma_sg modules are need by a   
saa7134 card, and not by AF9035. (no videobuf / dvb_usb_af9035
dependency).
Don't know if it is normal or not.

A bit frustrating to be so close to the end, but also a bit pessimistic   
because really reaching the limit of my skills.
Anyway, I will stay tuned in case some values need to be modified in the   
source for test, or any updates I will try.

Many thanks.
Diorser.

On Tue, 01 Jan 2013 23:26:32 +0100, Antti Palosaari <crope@iki.fiwrote

> Patch looks correct.
>>
> If you are talking of that error I saw wiki you mentioned it is not  
> error. You cannot use dvbsnoop like that. You have to tune to channel  
> first and only after device is tuned successfully pidscan is possible.
>>
>  # dvbsnoop -s pidscan
>  dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/
>  Transponder PID-Scan...
>  Error(22): DMX_SET_PES_FILTER: Invalid argument
>>
> If you are really sure your antenna is good (not that small antenna  
> bundled) and it does not work then there is some bug. I bet some GPIO is  
> wrong. Maybe you should take some sniffs using SniffUSB2.0 and look  
> there...
>
> regards
> Antti

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Antti Palosaari]

On 01/02/2013 01:09 AM, Diorser wrote:
> Thanks for your so fast reply.
> Unfortunately, scanning output is always empty with 100% signal
> strength  (external antenna)
> I also use a AverTV super_007 with the same external antenna on a
> another PC with Kaffeine =Signal = 100%.

Does it show 100% even antenna is unplugged?

> I also tried different dvb-usb-af9035-02.fw  firmware with different
> LINK/OFDM value (I don't understand but just tried.).

I don't know exactly what are differences between all those firmwares, 
but I know all firmwares are not working with all devices.

> Never got any PID or channel.
> Scanning and tuning work (or seem to with w_scan or kaffeine), but no
> data output.

You mean you see LOCK flag gained, then there is maybe error pid filter 
timeouts?

> I've noticed that videobuf_dvb and videobuf_dma_sg modules are need by
> a  saa7134 card, and not by AF9035. (no videobuf / dvb_usb_af9035
> dependency).
> Don't know if it is normal or not.

It is normal.

> A bit frustrating to be so close to the end, but also a bit pessimistic
> because really reaching the limit of my skills.
> Anyway, I will stay tuned in case some values need to be modified in
> the  source for test, or any updates I will try.

Do you have some working device (saa7134?)?
If yes, use it to generate channels.conf and when you has working 
channels.conf you could use tzap to tune.

If not, then make channels conf by hand

make file .tzap/channels.conf
then add line to that file:
TEST:634000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:512:650:17

replace 634000000 (634MHz) frequency of your transmitter. I think 8Mhz 
bandwidth is used for your area too, but if not change it to 7MHz. Other 
values are not critical as those are detected automatically.

After that you could tune: tzap -r TEST

Antti

>
> Many thanks.
> Diorser.
>
> On Tue, 01 Jan 2013 23:26:32 +0100, Antti Palosaari <crope@iki.fiwrote
>
>> Patch looks correct.
>>>
>> If you are talking of that error I saw wiki you mentioned it is not
>> error. You cannot use dvbsnoop like that. You have to tune to channel
>> first and only after device is tuned successfully pidscan is possible.
>>>
>>  # dvbsnoop -s pidscan
>>  dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/
>>  Transponder PID-Scan...
>>  Error(22): DMX_SET_PES_FILTER: Invalid argument
>>>
>> If you are really sure your antenna is good (not that small antenna
>> bundled) and it does not work then there is some bug. I bet some GPIO
>> is wrong. Maybe you should take some sniffs using SniffUSB2.0 and look
>> there...
>>
>> regards
>> Antti
> --
> 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


-- 
http://palosaari.fi/

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

> Does it show 100% even antenna is unplugged ?

It seems in fact that signal indicator is not reliable.
I have to sometimes reset dvb with:

for I in dvb_usb_af9035 af9033 tda18218 dvb_usb_v2 dvb_core rc_core; do   
rmmod $I; done
modprobe dvb-usb-af9035

The antenna signal input is fine, this is at least the point I am sure.

> You mean you see LOCK flag gained, then there is maybe error pid filter  
> timeouts ?

Not sure of that. tzap test seems to show the opposite:

tzap -r TEST
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/test_r/.tzap/channels.conf'
tuning to 586167000 Hz
video pid 0x0200, audio pid 0x028a
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |

I also took the kaffeine dvb files perfectly working with saa7134 card,  
but A918R card does not tune on  any channel.
Then, the lack of signal strength stability / front-end problem is may be  
the root cause.
Thanks again for your time

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Antti Palosaari]

On 01/02/2013 02:12 AM, Diorser wrote:
>> Does it show 100% even antenna is unplugged ?
>
> It seems in fact that signal indicator is not reliable.
> I have to sometimes reset dvb with:
>
> for I in dvb_usb_af9035 af9033 tda18218 dvb_usb_v2 dvb_core rc_core; do
> rmmod $I; done
> modprobe dvb-usb-af9035
>
> The antenna signal input is fine, this is at least the point I am sure.
>
>> You mean you see LOCK flag gained, then there is maybe error pid
>> filter timeouts ?
>
> Not sure of that. tzap test seems to show the opposite:
>
> tzap -r TEST
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file '/home/test_r/.tzap/channels.conf'
> tuning to 586167000 Hz
> video pid 0x0200, audio pid 0x028a
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |

This says it quite clearly, it does not work at all. I don't know why 
you resists to remove antenna or unplug stick, but even you remove 
antenna I am quite sure you will see similar results.

> I also took the kaffeine dvb files perfectly working with saa7134 card,
> but A918R card does not tune on  any channel.
> Then, the lack of signal strength stability / front-end problem is may
> be the root cause.
> Thanks again for your time

Maybe there is some GPIO controlling antenna input or switching some other.

Antti

-- 
http://palosaari.fi/

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

>  I don't know why you resists to remove antenna or unplug stick, but  
> even you remove antenna I am quite sure you will see similar results.

I've been simply confused by the signal reported at ffff level most of the  
time, and the scanning working.
I thought the problem was a step behind with the demux error reported by  
dvbsnoop wrongly used.

Can you confirm, either you personally, or someone else you know, that  
AVerTV_Volar_HD_PRO_A835 using same components as A918R fully works  
including tuning+scanning ?
If so, it's hard to believe that Avermedia made something different when  
changing from a USB stick to Express card detected as USB, but who  
knows....

> Maybe there is some GPIO controlling antenna input or switching some  
> other.

I've noticed that af9035.c does not contain any GPIO settings for TDA18218  
(all other tuners have).
Would it be possible to implement gpio setting for TDA18218 so that they  
are used for implementations requesting it ? (just an assumption of  
course). Don't know at all if this kind of information is easily available.

If necessary, although not familiar at all with debugging, I can try co  
compile a specific kernel with CONFIG_DEBUG_KERNEL=y option to see if I  
can grab something interesting.

Finally, it seems that fresh implementation of TDA18218 needs a bit more  
investigation checked on more devices.

BTW, is the A918R patch proposal accepted to be taken into consideration,  
or do I have to make a more formal GIT request ?

Regards.
Diorser.

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Antti Palosaari]

On 01/03/2013 11:24 PM, Diorser wrote:
>
>>  I don't know why you resists to remove antenna or unplug stick, but
>> even you remove antenna I am quite sure you will see similar results.
>
> I've been simply confused by the signal reported at ffff level most of
> the time, and the scanning working.

hmm, you could say it is working as you don't see errors but for me 
working means you could tune to channels and see programs. "Tuning 
failed" is not working for me.

> I thought the problem was a step behind with the demux error reported by
> dvbsnoop wrongly used.
>
> Can you confirm, either you personally, or someone else you know, that
> AVerTV_Volar_HD_PRO_A835 using same components as A918R fully works
> including tuning+scanning ?
> If so, it's hard to believe that Avermedia made something different when
> changing from a USB stick to Express card detected as USB, but who
> knows....
>
>> Maybe there is some GPIO controlling antenna input or switching some
>> other.
>
> I've noticed that af9035.c does not contain any GPIO settings for
> TDA18218 (all other tuners have).
> Would it be possible to implement gpio setting for TDA18218 so that they
> are used for implementations requesting it ? (just an assumption of
> course). Don't know at all if this kind of information is easily available.

I am quite 100% sure problems is GPIOs. Those could be different from 
design to design, especially in case of AverMedia....

> If necessary, although not familiar at all with debugging, I can try co
> compile a specific kernel with CONFIG_DEBUG_KERNEL=y option to see if I
> can grab something interesting.
>
> Finally, it seems that fresh implementation of TDA18218 needs a bit more
> investigation checked on more devices.
>
> BTW, is the A918R patch proposal accepted to be taken into
> consideration, or do I have to make a more formal GIT request ?
>
> Regards.
> Diorser.

Without the hardware it is hard to do anything. I don't care to spend my 
time of debugging it remotely.

Surely it is only under 10 lines of new code to support that device, but 
finding out reason is thing which took time.

regards
Antti

-- 
http://palosaari.fi/

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

Just to compare, this is the same tzap test made on same channel with a  
AverTV 007 (saa7134) on a another PC, with same antenna.
It works perfectly.

tzap -r TEST
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '~/.tzap/channels.conf'
tuning to 586167000 Hz
video pid 0x0200, audio pid 0x028a
status 00 | signal b2b2 | snr 2929 | ber 0001fffe | unc 00000000 |
status 1f | signal b2b2 | snr fefe | ber 0000004e | unc ffffffff |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr fefe | ber 00000050 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr fefe | ber 0000005c | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b1b1 | snr fefe | ber 00000054 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr fefe | ber 0000004e | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 00000050 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 00000052 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 00000050 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 0000004a | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 00000050 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 0000004e | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 00000044 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 0000004a | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 0000004e | unc 00000000 |  
FE_HAS_LOCK

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

Hello,

Please find below some news for A918R
[details @  
http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_HD_Express_A918R ]

* the patch proposed to automatically load the right modules for A918R  
card is not yet available
=> http://www.mail-archive.com/linux-media@vger.kernel.org/msg56659.html
(I don't exactly know what is missing to make it accepted).
This patch would at least avoid having to modify dvb-usb-ids.h & af9035.c  
each time to test some git updates.

* previously, in December, the signal level detection was fuzzy and not  
reliable.
Now, the reported signal level is strictly at 0000 (good antenna RF signal  
confirmed with other device).

I am aware A918R card is not the most requested one (Express card), but  
that's all I can add in case it can help, even for another card.

Regards.


see details below:
------------------------------------------
UPDATE April 8th 2013: result with modules compiled from git:

tzap -r TEST
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/test_r/.tzap/channels.conf'
tuning to 586167000 Hz
video pid 0x0200, audio pid 0x028a
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |

kaffeine from command line

kaffeine(1584) DvbScanFilter::timerEvent: timeout while reading section;  
type = 0 pid = 0
kaffeine(1584) DvbScanFilter::timerEvent: timeout while reading section;  
type = 2 pid = 17
demux_wavpack: (open_wv_file:127) open_wv_file: non-seekable inputs aren't  
supported yet.
net_buf_ctrl: dvbspeed mode
kaffeine(1584) DvbScanFilter::timerEvent: timeout while reading section;  
type = 0 pid = 0
kaffeine(1584) DvbScanFilter::timerEvent: timeout while reading section;  
type = 2 pid = 17
net_buf_ctrl: dvbspeed OFF
kaffeine(2186) DvbLinuxDevice::getSignal: ioctl FE_READ_SIGNAL_STRENGTH  
failed for frontend "/dev/dvb/adapter0/frontend0"
kaffeine(2186) DvbLinuxDevice::getSnr:    ioctl FE_READ_SNR failed for  
frontend "/dev/dvb/adapter0/frontend0"
kaffeine(2186) DvbLinuxDevice::isTuned:   ioctl FE_READ_STATUS failed for  
frontend "/dev/dvb/adapter0/frontend0"
.../...
kaffeine(2186) DvbLinuxDevice::getSignal: ioctl FE_READ_SIGNAL_STRENGTH  
failed for frontend "/dev/dvb/adapter0/frontend0"
kaffeine(2186) DvbLinuxDevice::getSnr:    ioctl FE_READ_SNR failed for  
frontend "/dev/dvb/adapter0/frontend0"
kaffeine(2186) DvbLinuxDevice::isTuned:   ioctl FE_READ_STATUS failed for  
frontend "/dev/dvb/adapter0/frontend0"

demux_wavpack: (open_wv_file:127) open_wv_file: non-seekable inputs aren't  
supported yet.
net_buf_ctrl: dvbspeed mode
net_buf_ctrl: dvbspeed OFF
kaffeine(2215) DvbDevice::frontendEvent: tuning failed
------------------------------------------

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Antti Palosaari]

On 04/09/2013 05:46 PM, Diorser wrote:
> Hello,
>
> Please find below some news for A918R
> [details @
> http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_HD_Express_A918R ]
>
> * the patch proposed to automatically load the right modules for A918R
> card is not yet available
> => http://www.mail-archive.com/linux-media@vger.kernel.org/msg56659.html
> (I don't exactly know what is missing to make it accepted).
> This patch would at least avoid having to modify dvb-usb-ids.h &
> af9035.c each time to test some git updates.
>
> * previously, in December, the signal level detection was fuzzy and not
> reliable.
> Now, the reported signal level is strictly at 0000 (good antenna RF
> signal confirmed with other device).
>
> I am aware A918R card is not the most requested one (Express card), but
> that's all I can add in case it can help, even for another card.
>
> Regards.

Patch, which adds USB ID, is not acceptable unless device is know to be 
working. It currently works only partially by loading correct modules 
but tuning does not work. Surely, it is not very many lines code to fix 
it - most likely just some GPIO setting (antenna switch?).

regards
Antti

-- 
http://palosaari.fi/

Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal

[Diorser]

With RF signal input now clearly reported at 0000, antenna switch problem  
is a good assumption.
However, I don't have the right skills to "sniff" and imagine which file  
should be modified and how.
All I can do is recompiling git files and test.
If a list a "GPIO" values was available somewhere, and if I know where to  
modify the files, and with some luck, a miracle could may be happen.
However, I fully understand that an express card is too specific to create  
some interest.
Don't worry about this.
I just wanted to give some update on investigations done 3 months ago  
(quite some time spent on it....).
Thanks.
Rgds.

>
> Patch, which adds USB ID, is not acceptable unless device is know to be  
> working. It currently works only partially by loading correct modules  
> but tuning does not work. Surely, it is not very many lines code to fix  
> it - most likely just some GPIO setting (antenna switch?).
>
> regards
> Antti