Michael Krufky wrote:
Jarryd Beck wrote:
Takes half a minute to load when plugging in, keyboard is slow to respond
when tuning, and I get lots of this:
af9013_i2c_gate_ctrl: enable:0
af9013_i2c_gate_ctrl: enable:1
Applied the patch again and it was all fine.
Jarryd.
Thanks for the
On Sat, Mar 15, 2008 at 5:32 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
forgot attach patch...
Antti Palosaari wrote:
Michael Krufky wrote:
4.3 is not close enough to 3.8. If you don't know how to set the demod
to 3.8, then we can do some hacks to make it work, but signal
Michael's patch didn't produce any interesting dmesg output. I included
dmesg for plugging in and tuning with antti's patch.
Jarryd.
Just realised I didn't have debug enabled for Michael's patch. When
tuning I got lots of this:
tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0
Jarryd Beck wrote:
Michael's patch didn't produce any interesting dmesg output. I included
dmesg for plugging in and tuning with antti's patch.
First errors came from same situation as earlier, no_reconnect. But it
finally still worked.
Just realised I didn't have debug enabled for
On Sun, Mar 16, 2008 at 1:22 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
Michael's patch didn't produce any interesting dmesg output. I included
dmesg for plugging in and tuning with antti's patch.
First errors came from same situation as earlier, no_reconnect.
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 1:22 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Frequency control values of the demodulator seems to be ok now. Also adc
and coeff looks correct. It is hard to say where is problem...
Can you test if demodulator can detect TPS parameter
On Sun, Mar 16, 2008 at 11:08 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 1:22 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Frequency control values of the demodulator seems to be ok now. Also adc
and coeff looks correct. It is hard to say
Jarryd Beck wrote:
Here's the first frequency it tuned to, as you can see the
one you set auto on is still auto, it didn't seem to autodetect
anything. It was the same for all the other frequencies as well.
tune to:
On Sun, Mar 16, 2008 at 11:37 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
Here's the first frequency it tuned to, as you can see the
one you set auto on is still auto, it didn't seem to autodetect
anything. It was the same for all the other frequencies as well.
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 11:37 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
Here's the first frequency it tuned to, as you can see the
one you set auto on is still auto, it didn't seem to autodetect
anything. It was the same for all the other
Antti Palosaari wrote:
I have no idea how to debug more. Without device it is rather hard to
test many things. It will help a little if we know is tuner locked.
Mike, is it easy to add debug writing for tuner to indicate if tuner
is locked or not locked? I have used that method earlier with
On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote:
Antti Palosaari wrote:
I have no idea how to debug more. Without device it is rather hard to
test many things. It will help a little if we know is tuner locked.
Mike, is it easy to add debug writing for tuner to
Jarryd Beck wrote:
You won't believe this, but it worked. I think every time I tried both
patches together I left .no_reconnect in. I tried it again with both
patches applied, no other modifications, and it worked.
Thanks for all your help,
Jarryd.
Great. I will finalize support for this
On Sun, Mar 16, 2008 at 12:39 PM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
You won't believe this, but it worked. I think every time I tried both
patches together I left .no_reconnect in. I tried it again with both
patches applied, no other modifications, and it
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote:
Antti Palosaari wrote:
I have no idea how to debug more. Without device it is rather hard to
test many things. It will help a little if we know is tuner locked.
Mike, is it easy to add debug
Jarryd Beck wrote:
Also there's a blue light that comes on in windows when I tune, but it didn't
come on in linux when tuned. Would it be possible to work
out how to make that light come on when it has successfully tuned?
Should be peace of cake to fix. I will check it later...
Antti
--
On Sun, Mar 16, 2008 at 1:04 PM, Michael Krufky [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote:
Antti Palosaari wrote:
I have no idea how to debug more. Without device it is rather hard to
test many things. It
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 1:04 PM, Michael Krufky [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
Antti Palosaari wrote:
I have no idea how to debug more. Without device it is rather hard to
Antti Palosaari wrote:
Jarryd Beck wrote:
Also there's a blue light that comes on in windows when I tune, but
it didn't
come on in linux when tuned. Would it be possible to work
out how to make that light come on when it has successfully tuned?
Should be peace of cake to fix. I will check
Antti Palosaari wrote:
looks like possible bug found!
Jarryd Beck wrote:
On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED]
wrote:
This all happens very quickly on the hardware that I've tested ( a
cx23887-based pcie card and a cypress fx2-based usb device). I've
also
Michael Krufky wrote:
4.3 is not close enough to 3.8. If you don't know how to set the demod
to 3.8, then we can do some hacks to make it work, but signal reception
is likely to be very poor -- better off looking in his snoop log to see
how the windows driver sets the demod to 3.8
OI have
forgot attach patch...
Antti Palosaari wrote:
Michael Krufky wrote:
4.3 is not close enough to 3.8. If you don't know how to set the demod
to 3.8, then we can do some hacks to make it work, but signal reception
is likely to be very poor -- better off looking in his snoop log to see
how the
On Thu, Mar 13, 2008 at 1:20 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Then, please turn ON debug, repeat your tests, and post
Jarryd Beck wrote:
I found the problem, the driver I had set .no_reconnect = 1 in
af9015_properties, the one in af9015_new didn't. So after I changed
that I tried again, it still didn't work. I enabled debugging and tried
to tune to a channel and this is what I got in dmesg.
I know this
On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
I found the problem, the driver I had set .no_reconnect = 1 in
af9015_properties, the one in af9015_new didn't. So after I changed
that I tried again, it still didn't work. I enabled debugging
Jarryd Beck wrote:
On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
I found the problem, the driver I had set .no_reconnect = 1 in
af9015_properties, the one in af9015_new didn't. So after I changed
that I tried again, it still didn't
On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED]
wrote:
Jarryd Beck wrote:
I found the problem, the driver I had set .no_reconnect = 1 in
af9015_properties, the one
On Fri, Mar 14, 2008 at 2:22 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED]
wrote:
Jarryd Beck wrote:
I found
Jarryd Beck wrote:
and when I try to tune it I get this:
af9013_init
af9013_reset
af9013_power_ctrl: onoff:1
af9013_set_adc_ctrl: adc_clock:28000
af913_div: a:2800 b:100 x:19
af913_div: a:0 b:100 x:19 r:14680064 r:e0
af9013_init: load ofsm settings
af9013_init: load
Jarryd Beck wrote:
On Fri, Mar 14, 2008 at 2:22 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Here is dmesg with debug enabled on af9013 too:
usb 2-10: new high speed USB device using ehci_hcd and address 7
usb 2-10: configuration #1 chosen from 1 choice
af9015_usb_probe:
Michael Krufky wrote:
This all happens very quickly on the hardware that I've tested ( a
cx23887-based pcie card and a cypress fx2-based usb device). I've also
heard good reports on saa713x-based pci cards. Is the i2c slow in the
af9013 driver?
I will check this later, probably it is
Jarryd Beck wrote:
Somewhere along the way demod_address in a struct is set to AF9015_I2C_DEMOD
which is 0x38. Is that what you wanted?
No, it is demodulator i2c-address.
Antti
--
http://palosaari.fi/
___
linux-dvb mailing list
looks like possible bug found!
Jarryd Beck wrote:
On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote:
This all happens very quickly on the hardware that I've tested ( a
cx23887-based pcie card and a cypress fx2-based usb device). I've also
heard good reports on
On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Also when I plugged it in, it sat there for about 10 seconds before
finishing loading (dmesg printed another 5 lines about the device
after about 10 seconds), but still no tuning.
Can I see those five
hello
I looked sniffs and find correct demodulator initialization values for
this NXP tuner. Copy paste correct table from attached file and try.
Hopefully it works. I compared your sniff to mt2060 and qt1010 based
devices and there was still some minor differences to check.
regards,
Antti
Michael Krufky wrote:
On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Also when I plugged it in, it sat there for about 10 seconds
before
finishing loading (dmesg printed another 5 lines about the device
after about 10 seconds), but still no tuning.
Jarryd,
I've analyzed the snoop that you've taken of the windows driver, and I
conclude that the driver is basically doing exactly the same that the
linux driver would do. The only thing that I cannot verify is whether
or not the tda18211 uses the same table values as the
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Jarryd,
I've analyzed the snoop that you've taken of the windows driver, and I
conclude that the driver is basically doing exactly the same that the
linux driver would do. The only thing that I
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Jarryd,
I've analyzed the snoop that you've taken of the windows driver,
and I
conclude that the driver is
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Jarryd,
I've analyzed the snoop that you've taken of the windows
driver, and I
conclude that
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Jarryd,
I've analyzed
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Jarryd,
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Then, please turn ON debug, repeat your tests, and post again with
dmesg. I am not familiar with the af9015 driver, but for tda18271, set
debug=1. (you must unload all modules first -- do 'make unload' in
status 00 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
I'm not familiar enough with the hardware and I don't know if this will help
but this is the same thing I was seeing when I was getting the dvico dual
digital 4
On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Then, please turn ON debug, repeat your tests, and post again with
dmesg. I am not familiar with the af9015 driver, but for
Can you take logs with vendor WHQL driver and sent for further analysis?
http://www.afatech.com/EN/support.aspx
Antti
--
http://palosaari.fi
For some reason windows didn't like that driver. When I used the installer
nothing happened, and when I used device manager it said this folder
On Tue, Mar 11, 2008 at 5:05 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Can you take logs with vendor WHQL driver and sent for further analysis?
http://www.afatech.com/EN/support.aspx
Antti
--
http://palosaari.fi
For some reason windows didn't like that driver. When I
One thing I can say -- the Linux tda18271 driver should be able to
detect your tuner at 0xC0 (0x60) as a tda18271c1 -- It's worth a
try, and could certainly be possible that the driver *may* work as-is,
although I suspect that some tweaking will be needed.
Regards,
Mike
I changed
Jarryd Beck wrote:
One thing I can say -- the Linux tda18271 driver should be able to
detect your tuner at 0xC0 (0x60) as a tda18271c1 -- It's worth a
try, and could certainly be possible that the driver *may* work as-is,
although I suspect that some tweaking will be needed.
Regards,
You said that you tuned to channel 7, sydney, australia -- is that an 8 MHz
channel? What frequency is it on?
Australia uses 7MHz channels in VHF and UHF.
- Steve
___
linux-dvb mailing list
linux-dvb@linuxtv.org
Also when I plugged it in, it sat there for about 10 seconds before
finishing loading (dmesg printed another 5 lines about the device
after about 10 seconds), but still no tuning.
Can I see those five lines? ;-)
While you're at it, you may as well include dmesg from the point
I think that the tda18271 driver will work with your tuner, but we may
need to make some small adjustments. If you look in tda18271-fe.c ,
you'll find the code that autodetects between a TDA18271c1 and a
TDA18271c2 ...
I just realised there's a problem with versions of code. I'm using
Jarryd Beck wrote:
I think that the tda18271 driver will work with your tuner, but we may
need to make some small adjustments. If you look in tda18271-fe.c ,
you'll find the code that autodetects between a TDA18271c1 and a
TDA18271c2 ...
I just realised there's a problem with versions
You can update af9015-tree to master level easily:
hg pull -u http://linuxtv.org/hg/v4l-dvb
hg merge
Thanks, that worked well.
Also if I could somehow get this working with the right
code, I don't know how to set up the values in the tda182171_config
struct.
Take USB-sniffs
On Tue, Mar 11, 2008 at 12:38 AM, Michael Krufky [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
I think that the tda18271 driver will work with your tuner, but we may
need to make some small adjustments. If you look in tda18271-fe.c ,
you'll find the code that autodetects between a
Jarryd Beck wrote:
That didn't work, the problem is I can't tell where it's going wrong and
I don't understand usb sniffs. I have a few questions:
When af9015 reads the tuner, the existing tuners set the spectral
inversion state-gpio3. Do you know what state-gpio3 does?
It connects tuner,
Jarryd Beck wrote:
Would someone be interested in writing tuner drivers for the NXP
18211HDC1 tuner?
I recently bought the Winfast DTV Dongle Gold which uses an AF9015
chip and the NXP tuner.
I've managed to get it working up to the point of needing the tuner,
after that nothing works.
I
On Mon, Mar 10, 2008 at 12:46 PM, Michael Krufky [EMAIL PROTECTED]
wrote:
Jarryd Beck wrote:
Would someone be interested in writing tuner drivers for the NXP
18211HDC1 tuner?
I recently bought the Winfast DTV Dongle Gold which uses an AF9015
chip and the NXP tuner.
I've managed to
59 matches
Mail list logo
