[linux-dvb] Re: Nebula DigiTV and nxt6000 problems

["Robert Cook" <robert@softek.com.au>]

Look like the driver is loading and registering the frontend but no joy
using ztap.

Robert

#dmesg
i2c-core.o: i2c core module version 2.8.1 (20031005)
Linux video capture interface: v1.00
bttv: driver version 0.9.12 loaded
bttv: snapshot date 2004-01-21
bttv: using 4 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 02:0b.0, irq: 23, latency: 64, mmio: 0xfbefc000
bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem ID
is 0071:0101
bttv0: using: Nebula Electronics DigiTV [card=104,insmod option]
bttv0: gpio: en=00000000, out=00000000 in=00ff48cb [init]
bttv0: using tuner=-1
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
bttv: Bt8xx card found (1).
bttv1: Bt878 (rev 17) at 02:0a.0, irq: 22, latency: 64, mmio: 0xfbefe000
bttv1: subsystem: 1461:0761 (UNKNOWN)
please mail id, board name and the correct card= insmod option to
kraxel@bytesex.org
bttv1: using:  *** UNKNOWN/GENERIC ***  [card=0,autodetected]
bttv1: gpio: en=00000000, out=00000000 in=009c004d [init]
bttv1: using tuner=-1
bttv1: i2c: checking for MSP34xx @ 0x80... not found
bttv1: i2c: checking for TDA9875 @ 0xb0... not found
bttv1: i2c: checking for TDA7432 @ 0x8a... not found
bttv1: registered device video1
bttv1: registered device vbi1
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
bt878(0): Bt878 (rev 17) at 02:0b.1, irq: 23, latency: 64, memory:
0xfbefd000
bt878: Bt878 AUDIO function found (1).
bt878(1): Bt878 (rev 17) at 02:0a.1, irq: 22, latency: 64, memory:
0xfbeff000
DVB: registering new adapter (Neb).
DVB: registering new adapter (Ave).
DVB: registering frontend 0:0 (NxtWave NXT6000)...

#linuxtv-dvb-apps-1.1.0/util/szap/tzap -c channels.conf "sbs digital 1"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 536500000 Hz
video pid 0x00a1, audio pid 0x0051
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |



-----Original Message-----
From: linux-dvb-bounce@linuxtv.org [mailto:linux-dvb-bounce@linuxtv.org]
On Behalf Of Holger Waechtler
Sent: Monday, 26 January 2004 9:53 PM
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Re: Nebula DigiTV and nxt6000 problems


Robert Cook wrote:
> The board revision is E 03/2003
> 
> It has the following chips:
> 
> About 1cm square
> NxtWave communications
> Nxt 6000
> DD8376
> 1A1 0304

Ok, then they still have the Ntx6000 onboard. Hmmm - I read again your 
first mail and there you mentioned that it was already working, so sorry

for confusion. But now I remember the problem: Gerd Knorr said that the 
bt8xx it is not able to send zero-byte messages using the hardware i2c 
controller thus you get -EINVAL when trying to check which PLL is 
onboard - so you need the software bitbanging driver for the nxt6000.

I modified the nxt6000 driver so that it does not sends zero-length 
messages anymore, can you please test and report whether it works for
you?

Holger



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe
linux-dvb" as subject.



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.