PULL-request update.
On 30.03.2012 15:33, Antti Palosaari wrote:
Terve Mauro and all the other hackers,
I did some massive rewrite for my old AF9035/AF9033 driver that was
never merged. Anyhow, here it is.
New drivers here are:
Infineon TUA 9001 silicon tuner driver
Afatech AF9033 DVB-T demodu
On Sun, 01 Apr 2012 19:39:56 +0300
Antti Palosaari wrote:
> > Well I didn't retry at that level, but at the fc0011 driver level.
> > It does already retry once in fc0011 (with complete tuner reset).
> > I increased it to 6 times (3 was not enough).
>
> Maybe some delay is needed in order to wait
On 01.04.2012 19:32, Michael Büsch wrote:
On Sun, 01 Apr 2012 19:20:21 +0300
Antti Palosaari wrote:
On 01.04.2012 19:15, Michael Büsch wrote:
On Sun, 1 Apr 2012 15:11:53 +0200
Michael Büsch wrote:
[ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
Ok, it turns out t
On Sun, 1 Apr 2012 18:24:09 +0200
"Hans-Frieder Vogt" wrote:
> However, I found the problem: the buffer
> length needs to be msg[1].len, see below.
I spotted this bug, too, but it didn't fix the problem, as len is 1 for
both packets in my specific case. So it doesn't make a difference in this ca
On Sun, 01 Apr 2012 19:20:21 +0300
Antti Palosaari wrote:
> On 01.04.2012 19:15, Michael Büsch wrote:
> > On Sun, 1 Apr 2012 15:11:53 +0200
> > Michael Büsch wrote:
> >
> >> [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
> >
> > Ok, it turns out that it doesn't fail all
Am Sonntag, 1. April 2012 schrieb Michael Büsch:
> On Sun, 1 Apr 2012 16:42:34 +0200
>
> "Hans-Frieder Vogt" wrote:
> > > [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
> > >
> > > It doesn't run into this check on the other af903x driver.
> > > So I suspect an i2c read
On 01.04.2012 19:15, Michael Büsch wrote:
On Sun, 1 Apr 2012 15:11:53 +0200
Michael Büsch wrote:
[ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
Ok, it turns out that it doesn't fail all the time, but only sporadically.
So increasing the number of retries fixes (or at
On Sun, 1 Apr 2012 15:11:53 +0200
Michael Büsch wrote:
> [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
Ok, it turns out that it doesn't fail all the time, but only sporadically.
So increasing the number of retries fixes (or at least works around) it.
No idea why this b
Am Sonntag, 1. April 2012 schrieb Antti Palosaari:
> On 01.04.2012 17:31, Hans-Frieder Vogt wrote:
> > Antti,
> >
> > I could provide the SNR, BER and UCB implementation (simply porting from
> > my draft driver to yours).
> > But I first need to implement the support for my AverMedia A867R device
On 01.04.2012 17:31, Hans-Frieder Vogt wrote:
Antti,
I could provide the SNR, BER and UCB implementation (simply porting from my
draft driver to yours).
But I first need to implement the support for my AverMedia A867R device so that
I am able to test the implementation. Therefore it could take a
On Sun, 1 Apr 2012 16:42:34 +0200
"Hans-Frieder Vogt" wrote:
> > [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
> >
> > It doesn't run into this check on the other af903x driver.
> > So I suspect an i2c read issue here.
>
> I would first uncomment the i2c read functional
Michael,
Am Sonntag, 1. April 2012 schrieb Michael Büsch:
> On Sun, 01 Apr 2012 15:29:07 +0300
>
> Antti Palosaari wrote:
> > buf[1] = msg[0].addr << 1;
> > Maybe you have given I2C address as a "8bit" format?
>
> Uhh, the address is leftshifted by one.
> So I changed the i2c address from 0xC0
Antti,
I could provide the SNR, BER and UCB implementation (simply porting from my
draft driver to yours).
But I first need to implement the support for my AverMedia A867R device so that
I am able to test the implementation. Therefore it could take a few hours
(maybe until tomorrow).
Regards,
On 01.04.2012 16:11, Michael Büsch wrote:
On Sun, 01 Apr 2012 15:29:07 +0300
Antti Palosaari wrote:
buf[1] = msg[0].addr<< 1;
Maybe you have given I2C address as a "8bit" format?
Uhh, the address is leftshifted by one.
So I changed the i2c address from 0xC0 to 0x60.
That's a very common mi
On Sun, 01 Apr 2012 15:29:07 +0300
Antti Palosaari wrote:
> buf[1] = msg[0].addr << 1;
> Maybe you have given I2C address as a "8bit" format?
Uhh, the address is leftshifted by one.
So I changed the i2c address from 0xC0 to 0x60.
The i2c write seems to work now. At least it doesn't complain anym
Ooops forget to comment these...
On 01.04.2012 13:27, Hans-Frieder Vogt wrote:
Your new firmware loader implies that the firmware is available as a type
"download firmware". It seems this is indeed the case for most (all?) of the
AF9035 devices. If the IT9135 driver should be merged, the "copy f
On 01.04.2012 13:27, Hans-Frieder Vogt wrote:
nice work! I'll try to port the features that I have in my implementation of
an af9035 driver into yours.
You are welcome! But please tell me what you are doing to avoid
duplicate work. My today plan was to implement af9033 SNR, BER, UCB, but
if y
On 01.04.2012 15:19, Michael Büsch wrote:
Great work. I'll rebase my tree on the new branch and check those firmware
files asap.
Hm, none of these firmwares fix the problem. Maybe it's not a firmware
problem after all, but just incorrectly setup tuner-i2c.
Here's the dmesg log:
[...]
[ 132.
On Sun, 1 Apr 2012 10:33:15 +0200
Michael Büsch wrote:
> On Sun, 01 Apr 2012 07:51:33 +0300
> Antti Palosaari wrote:
> > > I have no clue about the firmware format, so it will probably be easier
> > > if you'd dive into that stuff as you already seem to know it.
> >
> > Done. I didn't have neit
Antti,
nice work! I'll try to port the features that I have in my implementation of
an af9035 driver into yours.
Am Sonntag, 1. April 2012 schrieb Antti Palosaari:
> On 31.03.2012 19:52, Michael Büsch wrote:
> > On Sat, 31 Mar 2012 19:48:34 +0300
> >
> > Antti Palosaari wrote:
> >> And about t
Il 01/04/2012 06:51, Antti Palosaari ha scritto:
[snip]
> I need more AF903x hardware, please give links to cheap eBay devices
> etc. Also I would like to get one device where is AF9033 but no AF9035
> at all just for stand-alone demodulator implementation. I know there is
> few such devices, lik
On Sun, 01 Apr 2012 07:51:33 +0300
Antti Palosaari wrote:
> > I have no clue about the firmware format, so it will probably be easier
> > if you'd dive into that stuff as you already seem to know it.
>
> Done. I didn't have neither info, but there was good posting from Daniel
> Glöckner that doc
On 31.03.2012 19:52, Michael Büsch wrote:
On Sat, 31 Mar 2012 19:48:34 +0300
Antti Palosaari wrote:
And about the new FW downloader, that supports those new firmwares, feel
free to implement it if you wish too. I will now goto out of house and
will back during few hours. If you wish to do it j
On Sat, 31 Mar 2012 19:48:34 +0300
Antti Palosaari wrote:
> And about the new FW downloader, that supports those new firmwares, feel
> free to implement it if you wish too. I will now goto out of house and
> will back during few hours. If you wish to do it just reply during 4
> hours, and I wi
On Sat, 31 Mar 2012 19:34:23 +0300
Antti Palosaari wrote:
> On 31.03.2012 19:29, Michael Büsch wrote:
> > On Sat, 31 Mar 2012 17:28:38 +0300
> > Antti Palosaari wrote:
> >
> >> Googling the filename reveals many links, here is one:
> >> http://xgazza.altervista.org/Linux/DVB/dvb-usb-af9035-01.fw
I dropped Mauro from cc since he is not likely interested of that
development.
On 31.03.2012 19:34, Antti Palosaari wrote:
On 31.03.2012 19:29, Michael Büsch wrote:
On Sat, 31 Mar 2012 17:28:38 +0300
Antti Palosaari wrote:
Googling the filename reveals many links, here is one:
http://xgazza.
On 31.03.2012 19:29, Michael Büsch wrote:
On Sat, 31 Mar 2012 17:28:38 +0300
Antti Palosaari wrote:
Googling the filename reveals many links, here is one:
http://xgazza.altervista.org/Linux/DVB/dvb-usb-af9035-01.fw
Hm, on tuner register access I get these errors:
[ 9259.080907] af9035_ctrl_
On Sat, 31 Mar 2012 17:28:38 +0300
Antti Palosaari wrote:
> Googling the filename reveals many links, here is one:
> http://xgazza.altervista.org/Linux/DVB/dvb-usb-af9035-01.fw
Hm, on tuner register access I get these errors:
[ 9259.080907] af9035_ctrl_msg: command=03 failed fw error=2
[ 9259.0
On 31.03.2012 17:04, Michael Büsch wrote:
On Sat, 31 Mar 2012 00:14:58 +0200
Michael Büsch wrote:
On Sat, 31 Mar 2012 01:00:21 +0300
Antti Palosaari wrote:
Feel free to do that. Actually, I just tried it about 2 hours ago. But I
failed, since there callbacks given as a param for tuner attac
On Sat, 31 Mar 2012 00:14:58 +0200
Michael Büsch wrote:
> On Sat, 31 Mar 2012 01:00:21 +0300
> Antti Palosaari wrote:
>
> > Feel free to do that. Actually, I just tried it about 2 hours ago. But I
> > failed, since there callbacks given as a param for tuner attach and it
> > is wrong. There i
On Sat, 31 Mar 2012 01:00:21 +0300
Antti Palosaari wrote:
> Feel free to do that. Actually, I just tried it about 2 hours ago. But I
> failed, since there callbacks given as a param for tuner attach and it
> is wrong. There is frontend callback defined just for that. Look example
> from some X
On 31.03.2012 00:45, Michael Büsch wrote:
On Fri, 30 Mar 2012 15:33:02 +0300
Antti Palosaari wrote:
Terve Mauro and all the other hackers,
I did some massive rewrite for my old AF9035/AF9033 driver that was
never merged. Anyhow, here it is.
New drivers here are:
Infineon TUA 9001 silicon tun
On Fri, 30 Mar 2012 15:33:02 +0300
Antti Palosaari wrote:
> Terve Mauro and all the other hackers,
>
> I did some massive rewrite for my old AF9035/AF9033 driver that was
> never merged. Anyhow, here it is.
>
> New drivers here are:
> Infineon TUA 9001 silicon tuner driver
> Afatech AF9033 DVB
Terve Mauro and all the other hackers,
I did some massive rewrite for my old AF9035/AF9033 driver that was
never merged. Anyhow, here it is.
New drivers here are:
Infineon TUA 9001 silicon tuner driver
Afatech AF9033 DVB-T demodulator driver
Afatech AF9035 DVB USB driver
AF9035 integrates AF9
34 matches
Mail list logo
