Re: [linux-dvb] stb0899 troubles

2007-02-25 Thread Manu Abraham

On 2/25/07, Bernhard Rosenkraenzer [EMAIL PROTECTED] wrote:

On Saturday, 24. February 2007 23:56, Bernhard Rosenkraenzer wrote:
 Actual DVB-S2 channels don't seem to work either -- szap with the patches
 tunes there and claims to have a lock, but the dvr0 device remains empty.

I found some oddities in the patched szap code -- fixing them doesn't seem to
change anything, but maybe they cause odditites elsewhere (or maybe I'm
misreading things?):



the very same szap was used on dvb-s/dvb-s2 for a couple of people, so
the probability of szap not working is lesser.


1. do_tune() sets fe_params.delsys.*.fec = FEC_AUTO;
   but the type of the fec member is dvbfe_fec rather than fe_code_rate_t --
   shouldn't it be set to DVBFE_FEC_AUTO instead, especially because the value
   is not the same?



We use FEC_AUTO, with the API update DVBFE_FEC_AUTO.


2. Similarily, there's INVERSION_* vs. DVBFE_INVERSION_* --
   dvb_frontend_parameters takes a fe_spectral_inversion_t which matches
   the use of INVERSION_* in patched szap, but DVBFE_INVERSION_* is
   introduced by the multiproto patch and is set inside the kernel module
   if dvb_force_auto_inversion is on.



Inversion also doesn't matter.



3. Nothing in do_tune() sets fe_params.delsys.*.modulation -- but
   0 is DVBFE_MOD_NONE. Shouldn't it be set to DVBFE_MOD_AUTO
   (or DVBFE_MOD_QPSK/DVBFE_MOD_8PSK depending on dvbs vs. dvbs2)?
   If the modulation parameter is there for DVBFE_GET_PARAMS only, it should
   probably be pointed out in a comment in the header (the way it is done for
   e.g. dvbs2_params.rolloff)



Modulation also doesn't matter.

The only things that do matter

1) frequency
2) symbol rate
3) delivery system

As ralph said, probably wrong pids ?

regards,
manu

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Mantis driver: making cu1216.ko work for me

2007-02-25 Thread Manu Abraham

On 2/24/07, Marko Ristola [EMAIL PROTECTED] wrote:


Hi Manu,

I attached a minimal patch against mantis.tar.bz2.
It contains changes into cu1216.c.
Those changes enable dvb_core.c heuristics
so that both inversion=0 and inversion=1 work.

I didn't have to insert the get_tune_settings() function
that informs dvb_core.c about the 50ms delay.
cu1216.c works for me without that now.
I didn't have to fix the negative return value issue either:
no function seems to check the return value
of cu1216_set_parameters() anymore.

File cu1216_no_inversion_heuristics.patch
contains changes without fixing indentation.

File cu1216_no_inversion_heuristics_final.patch
contains same changes, but with fixing the indentation.


Without the patch, cu1216.c is stuck with inversion=0 :
it never tries inversion=1.

With me the fixed version works nicely:
Initially dvb_core.c tries with automatic mode inversion=0.
That fails for me and then dvb_core.c tries inversion=1.
That's successful for me.

When I switch into another frequency, dvb_core.c tries first inversion=1.
Thus it remembered the previous successfull inversion.

Thus I'd like to have Kaffeine inform dvb_core.c about using inversion=1
first.
That way I would save over two seconds for the first channel.


Cool. will pull it in. BTW can you give a round of tests with
http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2

The same patch can be applied to cu1216.c, as there weren't any
changes relevant to the cu1216.



Regards,
Marko



Thanks,
manu

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034

2007-02-25 Thread Manu Abraham

On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote:


 Just bought a new cpu and motherboard and made a clean install of FC6 and
made a vanilla 2.6.20 kernel.

 tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20
kernel.



Sorry for the delayed mail, somehow it skipped my eye.
Did quite a bit of work and ported the mantis tree ..
http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2

that warning, what you saw is fine, it came in after the i2c changes
in .20. It is fixed in the tree that i have put at the URL above.
diseqc stuff shouldn't be a problem though.

Would be interesting to know how it goes at your side.


regards,
manu

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Re: Nova-T 500 (dvb_usb_dib0700) usb disconnects

2007-02-25 Thread Antti P Miettinen
Chris Johns [EMAIL PROTECTED] writes:
 I see the same sequence that you do. Here is the specific part that
 matches what I see. Your trace has:

Hmm.. I guess I need to learn to decipher the logs. Meanwhile there's
another log at

  http://www.hut.fi/~apm/usb-disconnect2.txt.gz

where the disconnect should be approximately at timestamp
1493044489. It might be that the disconnect can be provoked by
interrupt load. I tried whether scanning/tuning/CPU load would trigger
the disconnect but no luck with those. The latest disconnect happened
while I was doing a big scp from the VDR box to another machine over
local ethernet. Might be just coincidence..

Anyone have a handy way of generating interrupt load?

-- 
http://www.iki.fi/~ananaza/


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034

2007-02-25 Thread Michel Verbraak

Manu Abraham schreef:

On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote:


 Just bought a new cpu and motherboard and made a clean install of 
FC6 and

made a vanilla 2.6.20 kernel.

 tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 
2.6.20

kernel.



Sorry for the delayed mail, somehow it skipped my eye.
Did quite a bit of work and ported the mantis tree ..
http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2

that warning, what you saw is fine, it came in after the i2c changes
in .20. It is fixed in the tree that i have put at the URL above.
diseqc stuff shouldn't be a problem though.

Would be interesting to know how it goes at your side.


regards,
manu

Manu,

I will test this version tonight and report back.
My rotor is working fine I discovered a small bug in my own software. 
When this was fixed I could rotate the dish without problems.


Regards,

Michel.


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Terratec Cinergy T USB XE

2007-02-25 Thread Dietmar Segbert
Empfaenger  : [EMAIL PROTECTED]
Absender: [EMAIL PROTECTED]  (Dietmar Segbert)
Betreff : Re: [linux-dvb] Terratec Cinergy t USB XE
Datum   : Sa 24.02.07, 14:43  (erhalten: 24.02.07, 17:27)
Groesse : 960 Bytes
--
hello Luca,

thanks for your answer. I have created the v4l-modules form cvs an add
your patch for the af9005 (. the kernel is 2.6.15. the module will
compile without errors.

If i plug in the terratec cinergy t usb xe dmesg will show the following:

usbcore: registered new driver dvb_usb_af9005
af9005: af9005_rc_decode function not found, disabling remote
usb 4-2: new full speed USB device using uhci_hcd and address 2
dvb-usb: found a 'TerraTec Cinergy T USB XE' in cold state, will try to load a 
firmware
dvb-usb: did not find the firmware file. (af9005.fw) Please see 
linux/Documentation/dvb/ for more details on firmware-problems. (-2)
dvb_usb_af9005: probe of 4-2:1.0 failed with error -2


I use slackware 10.2 and so the firmware file af9005.fw is in /lib/
firmware/.

I will be happy for any help, especially for an how-to to create the
af9005-driver for an 2.4.34 kernel, that i am normally use.

Regards

Dietmar

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Terratec Cinergy T USB XE

2007-02-25 Thread Luca Olivetti

En/na Dietmar Segbert ha escrit:


dvb-usb: did not find the firmware file. (af9005.fw) Please see 
linux/Documentation/dvb/ for more details on firmware-problems. (-2)
dvb_usb_af9005: probe of 4-2:1.0 failed with error -2


I use slackware 10.2 and so the firmware file af9005.fw is in /lib/
firmware/.


I suppose that you have to configure your hotplug so that it finds the 
firmware and sends it to the kernel.

Sorry, I cannot help you here since it just works(tm) here.
I can say that in my system where to look for the firmware and how to 
react to kernel requests is configured in /etc/hotplug/firmware.agent



I will be happy for any help, especially for an how-to to create the
af9005-driver for an 2.4.34 kernel, that i am normally use.


I think that'll be difficult :-(

Bye
--
Luca

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Terratec Cinergy T USB XE

2007-02-25 Thread Luca Olivetti

En/na Luca Olivetti ha escrit:

En/na Dietmar Segbert ha escrit:

dvb-usb: did not find the firmware file. (af9005.fw) Please see 
linux/Documentation/dvb/ for more details on firmware-problems. (-2)

dvb_usb_af9005: probe of 4-2:1.0 failed with error -2


I use slackware 10.2 and so the firmware file af9005.fw is in /lib/
firmware/.


I suppose that you have to configure your hotplug so that it finds the 
firmware and sends it to the kernel.

Sorry, I cannot help you here since it just works(tm) here.
I can say that in my system where to look for the firmware and how to 
react to kernel requests is configured in /etc/hotplug/firmware.agent



I will be happy for any help, especially for an how-to to create the
af9005-driver for an 2.4.34 kernel, that i am normally use.


I think that'll be difficult :-(


BTW, arcor.de refuses my mail, so I won't comment any further until they 
fix their mailserver. Surry, I'm tired of incompetent mail admins that 
just rely on stupid blacklists maintained by anti-spam vigilantes (that 
only amplify the problem, i.e. rendering communication difficult, 
instead of solving it) instead of intelligently dealing with spam.
I know it's not your fault, but be warned that, due to the incompetent 
mail admins of the isp you're using, you're surely losing legitimate email.
Note also that if you try to contact me directly you won't be able to, 
since a while ago I took the decision to only accept mail I can answer 
to (i.e. I verify that the sender address accepts my mail before 
accepting an incoming message).


Bye.

--
Luca


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Need firmware for M9206

2007-02-25 Thread Nick Andrew
Attached is the firmware for the LifeView TV Walker Twin (01fd:0514)

7119b154e7975a7fc2d5cb7c4bed5b28 
dvb-usb-lifeview-tv-walker-twin-0.95-20051010.bin

... as reconstructed from a dump of the usb transactions sent by
windows with the M9207BDA.sys driver loaded. However it's possible
that M9207BDA.sys contains more than one firmware.

This is the diff between the firmware reported by Pierre Willenbrock
and mine:

5,8c5,8
 100 8e 83 ed f0 22 00 f6 40 c3 00 40 00 12 01 00 02  [EMAIL 
PROTECTED]@.
 120 00 00 00 40 fd 10 13 15 95 00 00 00 00 01 00 00  [EMAIL PROTECTED]
 140 00 ff ff ff ff ff 08 4c 69 66 65 56 69 65 77 00  ...LifeView.
 160 00 00 00 00 00 00 08 44 56 42 54 20 20 20 20 00  ...DVBT.
---
 100 8e 83 ed f0 22 00 91 40 c3 00 40 00 12 01 00 02  [EMAIL 
 PROTECTED]@.
 120 00 00 00 40 fd 10 13 05 95 00 00 00 00 01 00 00  [EMAIL PROTECTED]
 140 01 ff ff ff ff ff 08 4c 69 66 65 56 69 65 77 00  ...LifeView.
 160 00 00 00 00 00 00 05 44 56 42 2d 54 00 00 00 00  ...DVB-T

The differences are:

byte  0106  f6 - 91  (load address??)
byte  0127  15 - 05  (this is the LSB of the PID after firmware download)
byte  0140  00 - 01  (no idea)
byte  0166  08 - 05  (length of the following device name string)
bytes 0167 - 0176 (different device name)

What are the first two bytes of every chunk in the firmware file
(the value)?

Nick.


dvb-usb-lifeview-tv-walker-twin-0.95-20051010.bin
Description: Binary data
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Anubis Electronics Lifeview(0x10fd:0x1513)

2007-02-25 Thread Pierre Willenbrock
Nick Andrew schrieb:
 This is very interesting to me because it's so similar to my
 LifeView TV Walker Twin (10fd:0514).
 
 I modified the m920x driver to detect my device and tried to
 send firmware to the device, but I found the firmware files I
 downloaded using Documentation/dvb/get_dvb_firmware are the
 wrong format. So I posted here yesterday asking if anyone can
 help me obtain firmware.
 
 Since posting I tried to make the device work under windows inside
 a VMWare virtual machine. I used the LifeView MVP software which
 comes on CD with the device. The software doesn't work (I get the
 error Cannot init dvb!) but I noticed that my device's ID changed
 from 10fd:0514 to 10fd:0513 afterward, so I suspected that Windows
 was loading the firmware.
 
 Today I tried to monitor the USB device transactions with usbmon
 and I got a 50k logfile to analyse. Then I found your posting
 with the attachment dvb-usb-digivox-02-0001.obj, and I compared
 the hex dump of that file against the usbmon output. I was right;
 Windows is sending firmware to the device, and furthermore it is
 nearly identical to your file.
 
 usbmon by default only logs the first 32 bytes of every packet but
 I could verify that it's sending the entire firmware. I'm about to
 rebuild the kernel to log all 64 bytes and then I will be able to
 easily extract the exact firmware for my device.
 
 By the way, the Windows device driver is from the LifeView MVP
 cdrom, specifically M9207BDA.sys, how about yours?

The windows driver for my device is named M9207_543.sys. MSI did their
own software bundle.

 After I have the firmware loaded I will start to explore the
 differences between my (very poorly) hacked m920x.c driver and yours.

Good luck.

Regards,
  Pierre

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Re: TDA8290/TDA8275 with LNA

2007-02-25 Thread Nico Sabbi

Hartmut Hackmann wrote:

Hi, Nico

Nico Sabbi schrieb:


Hi
I've just noticed that in your tree there's support for the
pre-amplifier of some Philips cards.
Does the Lifeview Trio already use your new code? Or do I need to add
support for it?



I copy this to the mailing lists because i think this is interesting
for more people.
First: the code went to mainstream yesterday.

Then i should give some explaination of what this is about:
Many recent cards with the TDA8275a silicon tuner have a preamplifier
(LNA) in front of the tuner chip. It is *not* inside the chip, and
since it costs some cents, it will not be on all recent cards.
This LNA needs to be controlled by the driver. I know about 3 variants
how this is done, currently, the driver doesn't detect the variant
automatically. So there is a new entry for the board configuration in
saa7134-cards.c. Possible values are:
.tuner_config   = 0, : no LNA present. This is the default
.tuner_config   = 1, : with LNA. This config is used on the Pinnacle 310i
.tuner_config   = 2, : with LNA. This is used on the Philips Tiger-S reference
 design and probably on most others.
.tuner_config   = 3,   with LNA. The new variant. Not sure who uses this.
There is an entry with the same meaning for the tda10046 configuration
in saa7134-dvb.c
I should add that the configurations 1 and 3 are untested. I am quite
sure that 1 is right but not so sure about config 3.



on a fresly compiled 2.6.20 + a fresh hg pull, after having set 
.tuner_config=2 in lifeview_trio_config  I got:


saa7133[0]/alsa: saa7133[0] at 0xf3115000 irq 21 registered as card -1
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
BUG: unable to handle kernel paging request at virtual address 6b6b6b6b
 printing eip:
e0f2713b
*pde = 
Oops:  [#1]
SMP
Modules linked in: saa7134_alsa tda827x saa7134_dvb tuner saa7134 
ir_kbd_i2c ir_common video_buf_dvb video_buf tda1004x binfmt_misc 
cpufreq_ondemand cpufreq_conservative cpufreq_powersave p4_clockmod 
speedstep_lib snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
snd_seq_device snd_pcm_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec 
ac97_bus snd_pcm snd_timer snd_page_alloc snd soundcore ipv6 eth1394 
sbs i2c_ec ide_cd cdrom ohci1394 ieee1394 loop nls_iso8859_15 ntfs 
intel_agp agpgart mt352 stv0299 b2c2_flexcop_pci b2c2_flexcop dvb_core 
firmware_class dvb_pll i2c_core fuse sn9c102 compat_ioctl32 tsdev 
videodev v4l1_compat v4l2_common usbmouse video usbhid ff_memless 
thermal processor fan dock container button battery ac ehci_hcd 
uhci_hcd usbcore sd_mod ahci ata_piix libata scsi_mod

CPU:1
EIP:0060:[e0f2713b]Not tainted VLI
EFLAGS: 00010246   (2.6.20 #1)
EIP is at tda1004x_read_byte+0x62/0xee [tda1004x]
eax: ca01dee6   ebx: 0001   ecx: 0001   edx: 6b6b6b6b
esi: d327ca00   edi: ca01dee4   ebp: ca01def4   esp: ca01deb8
ds: 007b   es: 007b   ss: 0068
Process kdvb-fe-1 (pid: 3707, ti=ca01c000 task=ca7ac030 task.ti=ca01c000)
Stack: 0009 0001 d327ca78 0009 0002  0001 
ca01dee7
   0001 0001 ca01dee6 01007222 0001 0001 d327ca00 
ca01df1c
   e0f2720b d327ca78 d327ca80 c9f22d24 ca01df1c e0f27a32 d327ca00 
d327ca80

Call Trace:
 [c0103c49] show_trace_log_lvl+0x19/0x2e
 [c0103cfb] show_stack_log_lvl+0x9d/0xa5
 [c0103f99] show_registers+0x1a0/0x277
 [c01042b1] die+0x116/0x1f0
 [c02c030a] do_page_fault+0x44a/0x51b
 [c02beb3c] error_code+0x7c/0x84
 [e0f2720b] tda1004x_write_mask+0x44/0x63 [tda1004x]
 [e0f286e4] tda1004x_set_fe+0x106/0x492 [tda1004x]
 [e0bba727] dvb_frontend_swzigzag_autotune+0x1ad/0x1d6 [dvb_core]
 [e0bbae5a] dvb_frontend_swzigzag+0x1ab/0x208 [dvb_core]
 [e0bbba08] dvb_frontend_thread+0x209/0x2a6 [dvb_core]
 [c012b4f7] kthread+0xb4/0xd9
 [c01039e7] kernel_thread_helper+0x7/0x10
 ===
Code: 00 8d 45 f2 89 45 ec 83 3d 80 a7 f2 e0 00 74 18 89 54 24 08 c7 
44 24 04 85 8a f2 e0 c7 04 24 20 8d f2 e0 e8 d0 40 1f df 8b 56 04 66 
0f b6 02 66 89 45 d8 66 0f b6 02 66 89 45 e4 8d 55 d8 b9 02
EIP: [e0f2713b] tda1004x_read_byte+0x62/0xee [tda1004x] SS:ESP 
0068:ca01deb8



do I need more changes to the code?

Thanks,

Nico

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Need firmware for M9206

2007-02-25 Thread Pierre Willenbrock
Nick Andrew schrieb:
 Attached is the firmware for the LifeView TV Walker Twin (01fd:0514)
 
 7119b154e7975a7fc2d5cb7c4bed5b28 
 dvb-usb-lifeview-tv-walker-twin-0.95-20051010.bin
 
 ... as reconstructed from a dump of the usb transactions sent by
 windows with the M9207BDA.sys driver loaded. However it's possible
 that M9207BDA.sys contains more than one firmware.
 
 This is the diff between the firmware reported by Pierre Willenbrock
 and mine:
 
 5,8c5,8
  100 8e 83 ed f0 22 00 f6 40 c3 00 40 00 12 01 00 02  [EMAIL 
 PROTECTED]@.
  120 00 00 00 40 fd 10 13 15 95 00 00 00 00 01 00 00  [EMAIL PROTECTED]
  140 00 ff ff ff ff ff 08 4c 69 66 65 56 69 65 77 00  ...LifeView.
  160 00 00 00 00 00 00 08 44 56 42 54 20 20 20 20 00  ...DVBT.
 ---
  100 8e 83 ed f0 22 00 91 40 c3 00 40 00 12 01 00 02  [EMAIL 
  PROTECTED]@.
  120 00 00 00 40 fd 10 13 05 95 00 00 00 00 01 00 00  [EMAIL PROTECTED]
  140 01 ff ff ff ff ff 08 4c 69 66 65 56 69 65 77 00  ...LifeView.
  160 00 00 00 00 00 00 05 44 56 42 2d 54 00 00 00 00  ...DVB-T
 
 The differences are:
 
 byte  0106  f6 - 91  (load address??)
 byte  0127  15 - 05  (this is the MSB of the PID after firmware download)
 byte  0140  00 - 01  (no idea)
 byte  0166  08 - 05  (length of the following device name string)
 bytes 0167 - 0176 (different device name)
 
 What are the first two bytes of every chunk in the firmware file
 (the value)?

My guess is that the lsb is a checksum over the packet. I have not tried
to reproduce it, yet. If you look for the firmware in the windows device
driver, you will probably find that the fields for pid and name are not
filled.

Regards,
  Pierre

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: TDA8290/TDA8275 with LNA

2007-02-25 Thread Nico Sabbi

Nico Sabbi wrote:

Hartmut Hackmann wrote:


Hi, Nico

Nico Sabbi schrieb:


Hi
I've just noticed that in your tree there's support for the
pre-amplifier of some Philips cards.
Does the Lifeview Trio already use your new code? Or do I need to add
support for it?



I copy this to the mailing lists because i think this is interesting
for more people.
First: the code went to mainstream yesterday.

Then i should give some explaination of what this is about:
Many recent cards with the TDA8275a silicon tuner have a preamplifier
(LNA) in front of the tuner chip. It is *not* inside the chip, and
since it costs some cents, it will not be on all recent cards.
This LNA needs to be controlled by the driver. I know about 3 variants
how this is done, currently, the driver doesn't detect the variant
automatically. So there is a new entry for the board configuration in
saa7134-cards.c. Possible values are:
.tuner_config   = 0, : no LNA present. This is the default
.tuner_config   = 1, : with LNA. This config is used on the Pinnacle 310i
.tuner_config   = 2, : with LNA. This is used on the Philips Tiger-S 
reference

 design and probably on most others.
.tuner_config   = 3,   with LNA. The new variant. Not sure who uses this.
There is an entry with the same meaning for the tda10046 configuration
in saa7134-dvb.c
I should add that the configurations 1 and 3 are untested. I am quite
sure that 1 is right but not so sure about config 3.




on a fresly compiled 2.6.20 + a fresh hg pull, after having set 
.tuner_config=2 in lifeview_trio_config  I got:


saa7133[0]/alsa: saa7133[0] at 0xf3115000 irq 21 registered as card -1
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
BUG: unable to handle kernel paging request at virtual address 6b6b6b6b
 printing eip:
e0f2713b


same crash without my change; it seems that 2.6.20 and saa7134-dvb 
don't get alone at all


--
Without a frontend, mplayer is useless - someone in mplayer-users

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] freecom usb stick troubles

2007-02-25 Thread James Shirley
Hi i've been trying to get my freecom usb dvb stick working with debian etch
(upto date, 2.6 kernel):

I've followed the instructions from

http://linuxtv.org/wiki/index.php/HOW_TO_Installing_DVB

and only deviated when i couldn't connect with

http://thadathil.net:8000/dvb/fw/

is this server down, or just refusing me for some reason?

anyway i found a redhat rpm somewhere with the firmware and my cksum is:

freak:/lib/firmware# cksum dvb-usb-wt220u-fc03.fw
592751328 12902 dvb-usb-wt220u-fc03.fw

The freecom stick has an art.no 28057, which is different to that suggested on
the linuxtv's website of 25451 for revision 3.

But anyway on usb plug in it says it uses this firmware file, and i get a

dvb-usb: recv bulk message failed: -110

which i assume is not good, can any body help?

cheers James

Feb 25 10:01:20 freak kernel: usb 1-5: new high speed USB device using
ehci_hcd and address 5
Feb 25 10:01:21 freak kernel: usb 1-5: configuration #1 chosen from 1 choice
Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.096625]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial').
Feb 25 10:01:21 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware
Feb 25 10:01:21 freak kernel: dvb-usb: downloading firmware from file
'dvb-usb-wt220u-fc03.fw'
Feb 25 10:01:21 freak kernel: usbcore: registered new driver dvb_usb_dtt200u
Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.317505]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_if0').
Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.332535]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_usbraw').
Feb 25 10:01:22 freak kernel: usb 1-5: USB disconnect, address 5
Feb 25 10:01:22 freak kernel: dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.723846]
nm_hal_device_removed (): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_if0').
Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.724727]
nm_hal_device_removed (): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_usbraw').
Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.726102]
nm_hal_device_removed (): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial').
Feb 25 10:01:23 freak kernel: usb 1-5: new high speed USB device using
ehci_hcd and address 6
Feb 25 10:01:24 freak kernel: usb 1-5: configuration #1 chosen from 1 choice
Feb 25 10:01:24 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
Receiver (Typhoon/Freecom)' in warm state.
Feb 25 10:01:24 freak kernel: dvb-usb: will use the device's hardware PID
filter (table count: 15).
Feb 25 10:01:24 freak kernel: DVB: registering new adapter (WideView WT-220U
PenType Receiver (Typhoon/Freecom)).
Feb 25 10:01:24 freak kernel: DVB: registering frontend 0 (WideView USB 
DVB-T)...
Feb 25 10:01:24 freak kernel: input: IR-receiver inside an USB DVB receiver as
/class/input/input3
Feb 25 10:01:24 freak kernel: dvb-usb: schedule remote query interval to 300
msecs.
Feb 25 10:01:24 freak kernel: dvb-usb: WideView WT-220U PenType Receiver
(Typhoon/Freecom) successfully initialized and connected.
Feb 25 10:01:24 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
Receiver (Typhoon/Freecom)' in warm state.
Feb 25 10:01:24 freak kernel: dvb-usb: will use the device's hardware PID
filter (table count: 15).
Feb 25 10:01:24 freak kernel: DVB: registering new adapter (WideView WT-220U
PenType Receiver (Typhoon/Freecom)).
Feb 25 10:01:24 freak kernel: DVB: registering frontend 1 (WideView USB 
DVB-T)...
Feb 25 10:01:24 freak kernel: input: IR-receiver inside an USB DVB receiver as
/class/input/input4
Feb 25 10:01:24 freak kernel: dvb-usb: schedule remote query interval to 300
msecs.
Feb 25 10:01:24 freak kernel: dvb-usb: WideView WT-220U PenType Receiver
(Typhoon/Freecom) successfully initialized and connected.
Feb 25 10:01:24 freak NetworkManager: debug info^I[1172397684.123024]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_226_20060503').
Feb 25 10:01:24 freak kernel: usbcore: registered new driver hiddev
Feb 25 10:01:24 freak kernel: usbcore: registered new driver usbhid
Feb 25 10:01:24 freak kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core
driver
Feb 25 10:01:24 freak NetworkManager: debug info^I[1172397684.199221]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_226_20060503_if0').
Feb 25 10:01:24 freak NetworkManager: debug info^I[1172397684.200119]
nm_hal_device_added (): New device added (hal udi is

[linux-dvb] terratec cinergy t usb xe

2007-02-25 Thread Dietmar Segbert
Hello Luca, hello list,

i found the error: After mounting sysfs, the terratec cinergy t usb xe  
will be detect and the firmware will be loaded. In the /dev directory will  
some devices /dev/dvb0:* created.

What is to do, that i can scan for senders with scan and to view tv?

If i do ./scan Scanlist channel.conf i will become an error /dev/dvb/ 
adapter0 not found.

Thanks for your help.

Dietmar

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] freecom usb stick troubles

2007-02-25 Thread Morfsta

Hi,

This is the same problem that I posted on the 14th Feb, titled Freecom
DVB-T USB Stick 25451-rev.3 Problems.

No one has answered it. :-(

I would be more than happy to help someone fix this.

Kind Regards,

Morfsta


On 2/25/07, James Shirley [EMAIL PROTECTED] wrote:


Hi i've been trying to get my freecom usb dvb stick working with debian
etch
(upto date, 2.6 kernel):

I've followed the instructions from

http://linuxtv.org/wiki/index.php/HOW_TO_Installing_DVB

and only deviated when i couldn't connect with

http://thadathil.net:8000/dvb/fw/

is this server down, or just refusing me for some reason?

anyway i found a redhat rpm somewhere with the firmware and my cksum is:

freak:/lib/firmware# cksum dvb-usb-wt220u-fc03.fw
592751328 12902 dvb-usb-wt220u-fc03.fw

The freecom stick has an art.no 28057, which is different to that
suggested on
the linuxtv's website of 25451 for revision 3.

But anyway on usb plug in it says it uses this firmware file, and i get a

dvb-usb: recv bulk message failed: -110

which i assume is not good, can any body help?

cheers James

Feb 25 10:01:20 freak kernel: usb 1-5: new high speed USB device using
ehci_hcd and address 5
Feb 25 10:01:21 freak kernel: usb 1-5: configuration #1 chosen from 1
choice
Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.096625]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial').
Feb 25 10:01:21 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware
Feb 25 10:01:21 freak kernel: dvb-usb: downloading firmware from file
'dvb-usb-wt220u-fc03.fw'
Feb 25 10:01:21 freak kernel: usbcore: registered new driver
dvb_usb_dtt200u
Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.317505]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_if0').
Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.332535]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_usbraw').
Feb 25 10:01:22 freak kernel: usb 1-5: USB disconnect, address 5
Feb 25 10:01:22 freak kernel: dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.723846]
nm_hal_device_removed (): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_if0').
Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.724727]
nm_hal_device_removed (): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_usbraw').
Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.726102]
nm_hal_device_removed (): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial').
Feb 25 10:01:23 freak kernel: usb 1-5: new high speed USB device using
ehci_hcd and address 6
Feb 25 10:01:24 freak kernel: usb 1-5: configuration #1 chosen from 1
choice
Feb 25 10:01:24 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
Receiver (Typhoon/Freecom)' in warm state.
Feb 25 10:01:24 freak kernel: dvb-usb: will use the device's hardware PID
filter (table count: 15).
Feb 25 10:01:24 freak kernel: DVB: registering new adapter (WideView
WT-220U
PenType Receiver (Typhoon/Freecom)).
Feb 25 10:01:24 freak kernel: DVB: registering frontend 0 (WideView USB
DVB-T)...
Feb 25 10:01:24 freak kernel: input: IR-receiver inside an USB DVB
receiver as
/class/input/input3
Feb 25 10:01:24 freak kernel: dvb-usb: schedule remote query interval to
300
msecs.
Feb 25 10:01:24 freak kernel: dvb-usb: WideView WT-220U PenType Receiver
(Typhoon/Freecom) successfully initialized and connected.
Feb 25 10:01:24 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
Receiver (Typhoon/Freecom)' in warm state.
Feb 25 10:01:24 freak kernel: dvb-usb: will use the device's hardware PID
filter (table count: 15).
Feb 25 10:01:24 freak kernel: DVB: registering new adapter (WideView
WT-220U
PenType Receiver (Typhoon/Freecom)).
Feb 25 10:01:24 freak kernel: DVB: registering frontend 1 (WideView USB
DVB-T)...
Feb 25 10:01:24 freak kernel: input: IR-receiver inside an USB DVB
receiver as
/class/input/input4
Feb 25 10:01:24 freak kernel: dvb-usb: schedule remote query interval to
300
msecs.
Feb 25 10:01:24 freak kernel: dvb-usb: WideView WT-220U PenType Receiver
(Typhoon/Freecom) successfully initialized and connected.
Feb 25 10:01:24 freak NetworkManager: debug info^I[1172397684.123024]
nm_hal_device_added (): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_14aa_226_20060503').
Feb 25 10:01:24 freak kernel: usbcore: registered new driver hiddev
Feb 25 10:01:24 freak kernel: usbcore: registered new driver usbhid
Feb 25 10:01:24 freak kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
core
driver
Feb 25 10:01:24 freak NetworkManager: debug info^I[1172397684.199221]
nm_hal_device_added (): 

[linux-dvb] Glitches in audio and video when recording from BTTV Twinhan VP-1025

2007-02-25 Thread Tim Hewett
I have a Twinhan VP-1025 PCI card (BTTV). It tunes fine and records  
ok except that every few minutes the recording has glitches which  
disrupt the audio and video at irregular intervals. The Twinhan card  
works fine using Twinhan's windows software and the same feed as when  
used from Linux, so it seems to be a pure Linux issue. The drivers  
load and detect the card without any errors.


I've tried running the latest drivers (extracted using Mercuurial and  
rebuilt and re-tested just before sending this message) with kernel  
2.6.20, but the problem still happens.


Can anyone help?

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034

2007-02-25 Thread Marian Zahariev
На 25.2.2007 11:41 Manu Abraham написа:
 On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote:
   Just bought a new cpu and motherboard and made a clean install of FC6
  and made a vanilla 2.6.20 kernel.
 
   tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20
  kernel.

 Sorry for the delayed mail, somehow it skipped my eye.
 Did quite a bit of work and ported the mantis tree ..
 http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2

 that warning, what you saw is fine, it came in after the i2c changes
 in .20. It is fixed in the tree that i have put at the URL above.
 diseqc stuff shouldn't be a problem though.

 Would be interesting to know how it goes at your side.


 regards,
 manu

Wors fine.

ACPI: PCI Interrupt :02:0b.0[A] - GSI 23 (level, low) - IRQ 18
irq: 18, latency: 32
 memory: 0xef00, mmio: 0xe081c000
found a VP-1034 PCI DVB-S/DSS device on (02:0b.0),
Mantis Rev 1 [1822:0014], irq: 18, latency: 32
memory: 0xef00, mmio: 0xe081c000
MAC Address=[00:08:ca:1a:99:3e]
mantis_alloc_buffers (0): DMA=0x1ed3 cpu=0xded3 size=65536
mantis_alloc_buffers (0): RISC=0x1ec43000 cpu=0xdec43000 size=1000
DVB: registering new adapter (Mantis dvb adapter).
mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS)
mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08
DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)...
ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 19
PCI: Setting latency timer of device :00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 61099 usecs
intel8x0: clocking to 48000
agpgart: Detected an Intel i850 Chipset.
agpgart: AGP aperture is 64M @ 0xf800


Linux 2.6.20 #1 SMP Sun Feb 25 15:42:20 EET 2007 i686 pentium4 i386 GNU/Linux

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] freecom usb stick troubles

2007-02-25 Thread Christophe Cattelain
I am not sure it applies to your stick (mine is a ''WideView WT-220U
PenType Receiver (based on ZL353)' with a different firmware...), but :

With a 'Moka DVB Digital TV receiver'
http://wiki.ubuntu-fr.org/materiel/moka_dvb_digital_tv_receiver (french
but look at the dmesg output)
I get the __same message__, but it seems to work : I can watch DVB-T
__if__ I get a good signal.

(of course, it would be better not to get such a message...)

So, go ahead?

and try 'kaffeine' (or scan/dvbscan) with the right configuration file
for your city.
(~/.kde/share/apps/kaffeine/dvb-t/au_* if you are using kaffeine with
DapperDrake)

(look if the scan generates more error messages, hangs,...)

But remember : you need to get the signal. (check with Windows?, try to
get a clear view to the emitter, being not to far... In Liège/Belgium,
The DBV-T channel is UHF-C66/834 MHz, one almost need a clear line of
sight to the emitter to get the signal...).


xof
==
James Shirley a écrit :
 Hi i've been trying to get my freecom usb dvb stick working with debian etch
 (upto date, 2.6 kernel):

 I've followed the instructions from

 http://linuxtv.org/wiki/index.php/HOW_TO_Installing_DVB

 and only deviated when i couldn't connect with

 http://thadathil.net:8000/dvb/fw/

 is this server down, or just refusing me for some reason?

 anyway i found a redhat rpm somewhere with the firmware and my cksum is:

 freak:/lib/firmware# cksum dvb-usb-wt220u-fc03.fw
 592751328 12902 dvb-usb-wt220u-fc03.fw

 The freecom stick has an art.no 28057, which is different to that suggested on
 the linuxtv's website of 25451 for revision 3.

 But anyway on usb plug in it says it uses this firmware file, and i get a

 dvb-usb: recv bulk message failed: -110

 which i assume is not good, can any body help?

 cheers James

 Feb 25 10:01:20 freak kernel: usb 1-5: new high speed USB device using
 ehci_hcd and address 5
 Feb 25 10:01:21 freak kernel: usb 1-5: configuration #1 chosen from 1 choice
 Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.096625]
 nm_hal_device_added (): New device added (hal udi is
 '/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial').
 Feb 25 10:01:21 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
 Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware
 Feb 25 10:01:21 freak kernel: dvb-usb: downloading firmware from file
 'dvb-usb-wt220u-fc03.fw'
 Feb 25 10:01:21 freak kernel: usbcore: registered new driver dvb_usb_dtt200u
 Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.317505]
 nm_hal_device_added (): New device added (hal udi is
 '/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_if0').
 Feb 25 10:01:21 freak NetworkManager: debug info^I[1172397681.332535]
 nm_hal_device_added (): New device added (hal udi is
 '/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_usbraw').
 Feb 25 10:01:22 freak kernel: usb 1-5: USB disconnect, address 5
 Feb 25 10:01:22 freak kernel: dvb-usb: generic DVB-USB module successfully
 deinitialized and disconnected.
 Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.723846]
 nm_hal_device_removed (): Device removed (hal udi is
 '/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_if0').
 Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.724727]
 nm_hal_device_removed (): Device removed (hal udi is
 '/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial_usbraw').
 Feb 25 10:01:22 freak NetworkManager: debug info^I[1172397682.726102]
 nm_hal_device_removed (): Device removed (hal udi is
 '/org/freedesktop/Hal/devices/usb_device_14aa_225_noserial').
 Feb 25 10:01:23 freak kernel: usb 1-5: new high speed USB device using
 ehci_hcd and address 6
 Feb 25 10:01:24 freak kernel: usb 1-5: configuration #1 chosen from 1 choice
 Feb 25 10:01:24 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
 Receiver (Typhoon/Freecom)' in warm state.
 Feb 25 10:01:24 freak kernel: dvb-usb: will use the device's hardware PID
 filter (table count: 15).
 Feb 25 10:01:24 freak kernel: DVB: registering new adapter (WideView WT-220U
 PenType Receiver (Typhoon/Freecom)).
 Feb 25 10:01:24 freak kernel: DVB: registering frontend 0 (WideView USB 
 DVB-T)...
 Feb 25 10:01:24 freak kernel: input: IR-receiver inside an USB DVB receiver as
 /class/input/input3
 Feb 25 10:01:24 freak kernel: dvb-usb: schedule remote query interval to 300
 msecs.
 Feb 25 10:01:24 freak kernel: dvb-usb: WideView WT-220U PenType Receiver
 (Typhoon/Freecom) successfully initialized and connected.
 Feb 25 10:01:24 freak kernel: dvb-usb: found a 'WideView WT-220U PenType
 Receiver (Typhoon/Freecom)' in warm state.
 Feb 25 10:01:24 freak kernel: dvb-usb: will use the device's hardware PID
 filter (table count: 15).
 Feb 25 10:01:24 freak kernel: DVB: registering new adapter (WideView WT-220U
 PenType Receiver (Typhoon/Freecom)).
 Feb 25 10:01:24 freak kernel: DVB: registering frontend 1 (WideView USB 
 DVB-T)...
 Feb 25 

Re: [linux-dvb] Problem tuning with Freecom USB DVB-T receiver

2007-02-25 Thread Måns Rullgård
Måns Rullgård [EMAIL PROTECTED] writes:

 I'm having some trouble getting a Freecom-branded USB DVB-T receiver
 working properly.  It gets firmware loaded, and is detected seemingly
 correctly.  This is where the fun ends:

 Using a channels.conf generated by dvbscan with a properly working PCI
 card, tzap fails to lock when trying to tune to BBC1:

[...]

 Some frequencies seem fine, though:

[...]

 Testing all frequencies in my channel list, I get these results:

 48980 BAD
 51380 BAD
 530167000 OK
 54580 BAD
 562166670 OK
 570166670 OK

 Does anyone have an idea what's going on here?  I've tried the drivers
 that come with Linux 2.6.20 and the latest development tree, getting
 the same results with both.  I'm getting no error messages from the
 drivers.

As is typical, more googling after sending this mail turned up the
answer.  This card seems to need an offset added to some frequencies.
MythTV appears to be coping with this, so all is well for now.

-- 
Måns Rullgård
[EMAIL PROTECTED]

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] freecom usb stick troubles

2007-02-25 Thread Måns Rullgård
James Shirley [EMAIL PROTECTED] writes:

 Hi i've been trying to get my freecom usb dvb stick working with debian etch
 (upto date, 2.6 kernel):

 I've followed the instructions from

 http://linuxtv.org/wiki/index.php/HOW_TO_Installing_DVB

 and only deviated when i couldn't connect with

 http://thadathil.net:8000/dvb/fw/

 is this server down, or just refusing me for some reason?

 anyway i found a redhat rpm somewhere with the firmware and my cksum is:

 freak:/lib/firmware# cksum dvb-usb-wt220u-fc03.fw
 592751328 12902 dvb-usb-wt220u-fc03.fw

 The freecom stick has an art.no 28057, which is different to that
 suggested on the linuxtv's website of 25451 for revision 3.

 But anyway on usb plug in it says it uses this firmware file, and i get a

 dvb-usb: recv bulk message failed: -110

 which i assume is not good, can any body help?

I have a receiver just like yours.  It appears to be working fine,
despite that message.

The one bit of trouble I ran into was that, for some reason, I have to
apply an offset to some frequencies, but not all, when tuning.  MythTV
handles this, but I suspect that it might get confused if other cards
without this quirk were present.

-- 
Måns Rullgård
[EMAIL PROTECTED]

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: [PATCH] Implement repeat key handling in budget-ci IR

2007-02-25 Thread Jouni
During make I get this:

/usr/local/src/v4ltesti/v4l-dvb/v4l/budget-ci.c:110: error: expected
identifier before numeric constant
make[3]: *** [/usr/local/src/v4ltesti/v4l-dvb/v4l/budget-ci.o] Error 1
make[2]: *** [_module_/usr/local/src/v4ltesti/v4l-dvb/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-50-generic'
make[1]: *** [default] Virhe 2
make[1]: Poistutaan hakemistosta /usr/local/src/v4ltesti/v4l-dvb/v4l
make: *** [all] Virhe 2

Did I botch something or is there a glitch in the code?





On Sun, 25 Feb 2007 02:17:54 +0100, Oliver Endriss [EMAIL PROTECTED]
said:
 David Härdeman wrote:
  The attached patch contains the last set of changes to the budget-ci IR 
  handling which makes it use the repeat handling of the input subsystem. 
  
  This allows some code simplification, makes sure that repeat key presses 
  are reported as such and also allows the debounce hack to be removed 
  altogether.
  
  In addition a couple of static variables were removed which would have 
  confused the IR code if more than one card is used.
 
 Thanks, applied.
 
 CU
 Oliver
 
 -- 
 
 VDR Remote Plugin 0.3.9 available at
 http://www.escape-edv.de/endriss/vdr/
 
 
 
 ___
 linux-dvb mailing list
 linux-dvb@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
-- 
  Jouni
  [EMAIL PROTECTED]

-- 
http://www.fastmail.fm - Access your email from home and the web


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] compile error

2007-02-25 Thread e9hack
Hi,

the current hg-tree won't compile for kernel 2.6.18.8:

/usr/src/v4l-dvb/v4l/budget-ci.c:110: error: expected identifier before numeric 
constant
make[3]: *** [/usr/src/v4l-dvb/v4l/budget-ci.o] Error 1
make[2]: *** [_module_/usr/src/v4l-dvb/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.18.8'
make[1]: *** [default] Fehler 2
make[1]: Leaving directory `/usr/src/v4l-dvb/v4l'
make: *** [all] Fehler 2
very-new-darkstar:/usr/src/DVB #

budget-ci.c:
103 #if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,19)
104 bool have_command;
105 };
106 #else
107 int have_command;
108 };
109 enum {
110 false = 0,
111 true = 1
112 };
113 #endif

If I remove the definition of true and false, I don't get an error.

- Hartmut

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] m920x script for extracting fw and i2c messages

2007-02-25 Thread Aapo Tahkola
This script allows generation of binary firmware files and i2c logs.
Supports three input formats:
-usbmon
-usb snoop
-snoopy pro

Syntax:
NN: addr AA reg RR = RW
NN: addr AA reg RR = RV read

NN is the first line of input source that initiated the
i2c command - this might be little broken at the moment.
AA = address
RR = register
RW = write value
RV = read value

Have fun.

-- 
Aapo Tahkola

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] m920x script for extracting fw and i2c messages

2007-02-25 Thread Aapo Tahkola
On Sun, 25 Feb 2007 17:28:57 +0200
Aapo Tahkola [EMAIL PROTECTED] wrote:

 This script allows generation of binary firmware files and i2c logs.
 Supports three input formats:
 -usbmon
 -usb snoop
 -snoopy pro
 
 Syntax:
 NN: addr AA reg RR = RW
 NN: addr AA reg RR = RV read
 
 NN is the first line of input source that initiated the
 i2c command - this might be little broken at the moment.
 AA = address
 RR = register
 RW = write value
 RV = read value
 
 Have fun.
 

D'oh, here it is.

-- 
Aapo Tahkola


m920x_parse
Description: Binary data
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [PATCH] Implement repeat key handling in budget-ci IR

2007-02-25 Thread Oliver Endriss
Jouni wrote:
 During make I get this:
 
 /usr/local/src/v4ltesti/v4l-dvb/v4l/budget-ci.c:110: error: expected
 identifier before numeric constant
 make[3]: *** [/usr/local/src/v4ltesti/v4l-dvb/v4l/budget-ci.o] Error 1
 make[2]: *** [_module_/usr/local/src/v4ltesti/v4l-dvb/v4l] Error 2
 make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-50-generic'
 make[1]: *** [default] Virhe 2
 make[1]: Poistutaan hakemistosta /usr/local/src/v4ltesti/v4l-dvb/v4l
 make: *** [all] Virhe 2
 
 Did I botch something or is there a glitch in the code?

Does the attached patch fix it for you?

@David:
This kind of stuff should go to compat.h anyway.
Fortunately, false/true are already defined there. ;-)

CU
Oliver

-- 

VDR Remote Plugin 0.3.9 available at
http://www.escape-edv.de/endriss/vdr/

diff -r 065567ae3ae0 linux/drivers/media/dvb/ttpci/budget-ci.c
--- a/linux/drivers/media/dvb/ttpci/budget-ci.c	Sun Feb 25 10:09:33 2007 -0200
+++ b/linux/drivers/media/dvb/ttpci/budget-ci.c	Sun Feb 25 19:11:17 2007 +0100
@@ -100,17 +100,8 @@ struct budget_ci_ir {
 	int rc5_device;
 	u32 last_raw;
 	u32 ir_key;
-#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,19)
 	bool have_command;
 };
-#else
-	int have_command;
-};
-enum {
-	false	= 0,
-	true	= 1
-};
-#endif
 
 struct budget_ci {
 	struct budget budget;
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034

2007-02-25 Thread Michel Verbraak

Michel Verbraak schreef:

Manu Abraham schreef:

On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote:


 Just bought a new cpu and motherboard and made a clean install of 
FC6 and

made a vanilla 2.6.20 kernel.

 tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 
2.6.20

kernel.



Sorry for the delayed mail, somehow it skipped my eye.
Did quite a bit of work and ported the mantis tree ..
http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2

that warning, what you saw is fine, it came in after the i2c changes
in .20. It is fixed in the tree that i have put at the URL above.
diseqc stuff shouldn't be a problem though.

Would be interesting to know how it goes at your side.


regards,
manu

Manu,

I will test this version tonight and report back.
My rotor is working fine I discovered a small bug in my own software. 
When this was fixed I could rotate the dish without problems.


Regards,

Michel.


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Manu,

The 24th of february 2007 version works allright for me. Following in 
messagelog:


ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 19 (level, 
low) - IRQ 19

irq: 19, latency: 32
memory: 0xf68ff000, mmio: 0xc202e000
found a VP-1034 PCI DVB-S/DSS device on (02:05.0),
   Mantis Rev 1 [1822:0014], irq: 19, latency: 32
   memory: 0xf68ff000, mmio: 0xc202e000
   MAC Address=[00:08:ca:19:9f:0b]
mantis_alloc_buffers (0): DMA=0xde5 cpu=0x81000de5 size=65536
mantis_alloc_buffers (0): RISC=0x30a04000 cpu=0x810030a04000 size=1000
DVB: registering new adapter (Mantis dvb adapter).
mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS)
mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08
DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)...

Rotor is working allright so DiseqC is transfered normal.
I merged only the mantis part into my kernel sources. This is a x86_64 
kernel.


What should be the differences to the previous version?

I did not yet try a scan for the missing channels to see if they are 
visible right now because my dish needs reallignement, reception is 
poort, after a storm a few weeks ago and currently it is pooring rain 
here so I was not able to get on my roof.


Regards,

Michel.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [PATCH] Implement repeat key handling in budget-ci IR

2007-02-25 Thread Oliver Endriss
Oliver Endriss wrote:
 Jouni wrote:
  During make I get this:
  
  /usr/local/src/v4ltesti/v4l-dvb/v4l/budget-ci.c:110: error: expected
  identifier before numeric constant
  make[3]: *** [/usr/local/src/v4ltesti/v4l-dvb/v4l/budget-ci.o] Error 1
  make[2]: *** [_module_/usr/local/src/v4ltesti/v4l-dvb/v4l] Error 2
  make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-50-generic'
  make[1]: *** [default] Virhe 2
  make[1]: Poistutaan hakemistosta /usr/local/src/v4ltesti/v4l-dvb/v4l
  make: *** [all] Virhe 2
  
  Did I botch something or is there a glitch in the code?
 
 Does the attached patch fix it for you?

Ok, I tried to compile against 2.6.18 and it still doesn't work.
The attached patch fixes it...

CU
Oliver

-- 

VDR Remote Plugin 0.3.9 available at
http://www.escape-edv.de/endriss/vdr/

diff -r 1697764d339d linux/drivers/media/dvb/ttpci/budget-ci.c
--- a/linux/drivers/media/dvb/ttpci/budget-ci.c	Sun Feb 25 14:40:47 2007 +0100
+++ b/linux/drivers/media/dvb/ttpci/budget-ci.c	Sun Feb 25 20:02:58 2007 +0100
@@ -100,17 +100,8 @@ struct budget_ci_ir {
 	int rc5_device;
 	u32 last_raw;
 	u32 ir_key;
-#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,19)
 	bool have_command;
 };
-#else
-	int have_command;
-};
-enum {
-	false	= 0,
-	true	= 1
-};
-#endif
 
 struct budget_ci {
 	struct budget budget;
diff -r 1697764d339d v4l/compat.h
--- a/v4l/compat.h	Sun Feb 25 14:40:47 2007 +0100
+++ b/v4l/compat.h	Sun Feb 25 20:02:39 2007 +0100
@@ -357,6 +357,8 @@ usb_to_input_id(const struct usb_device 
 # define PCIAGP_FAIL 0
 
 #define vmalloc_32_user(a) vmalloc_32(a)
+
+typedef int bool;
 #endif
 
 #ifndef true
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] DVB/V4L/VDR MediaWiki update

2007-02-25 Thread Johannes Stezenbach
Hi,

I updated the DVB, V4L and VDR Wikis on linuxtv.org
to MediaWiki version 1.9.3.

If you experience any problems due to the update, then
please let me know about it.


Thanks,
Johannes

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: Re : Re : [linux-dvb] Working DVB-S + CAM question

2007-02-25 Thread Dominique Dumont
Klaus Schmidinger [EMAIL PROTECTED] writes:

 Can you give me a hint how the high level API should be accessed
 through the LinuxDVB driver?

As Christophe said, it's mostly a matter of sending PMT messages.

There used to be a ca_zap program written by Manu Abraham, but I can't
find any reference about it now. 

Looks like ca_zap was renamed to zap_ca:
http://linuxtv.org/hg/dvb-apps?f=04b7e6c5335a;file=util/zap/zap_ca.c;style=gitweb

And here's a small command line to send message to CAM through
hi-level API:
http://linuxtv.org/hg/dvb-apps?mf=8b37590c8695;path=/util/dst-utils/;style=gitweb

And this libdvben50221 library may be quite interesting for vdr
(though it may be a part of libdvb that Christophe mentioned):
http://linuxtv.org/hg/dvb-apps?mf=8b37590c8695;path=/lib/libdvben50221/;style=gitweb

HTH

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Re: twinhan alpha vp7045A newer rev, firmware

2007-02-25 Thread Henrik Beckman

Making progress,

I´ve managed to parse and upload data to the device

/Henrik

On 2/23/07, Henrik Beckman [EMAIL PROTECTED] wrote:


Hi,

I have managed to capture some traffic with usbsnoop, I´ve captured from
insertion of the stick to a few seconds of tuning.

The snoop can be found here,
http://www.struct.se/usbsnoop.log-1.bz2

Any hints on extracting the firmware ?
http://www.isely.net/pvrusb2/utils.html been looking at the code but
nothing further yet.

Anyone ?

/Henrik


On 2/22/07, Henrik Beckman [EMAIL PROTECTED] wrote:

 Hi,

 Anyone had any succes with getting the newer alphas to work ?
 http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html

 If not I will try to extract the firmware from the latest windows
 driver, can anyone help me with hints on how to do this.
 Would it be possible to initialize the stick in windows and then without
 deinitializing it connect it to linux and download the firmware ?
 (thinking vmware or a powered hub here).

 TIA
 /Henrik




___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] DVB/V4L/VDR MediaWiki update

2007-02-25 Thread Oliver Endriss
Johannes Stezenbach wrote:
 Hi,
 
 I updated the DVB, V4L and VDR Wikis on linuxtv.org
 to MediaWiki version 1.9.3.
 
 If you experience any problems due to the update, then
 please let me know about it.

Don't know whether this is related:
linuxtv.org is no longer reachable from a web browser,
www.linuxtv.org works as usual.

Unfortunately, the HG repository pages use linuxtv.org... ;-(

CU
Oliver

-- 

VDR Remote Plugin 0.3.9 available at
http://www.escape-edv.de/endriss/vdr/



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DVB/V4L/VDR MediaWiki update

2007-02-25 Thread Johannes Stezenbach
On Sun, Feb 25, 2007 at 09:54:05PM +0100, Oliver Endriss wrote:
 Johannes Stezenbach wrote:
  
  I updated the DVB, V4L and VDR Wikis on linuxtv.org
  to MediaWiki version 1.9.3.
  
  If you experience any problems due to the update, then
  please let me know about it.
 
 Don't know whether this is related:
 linuxtv.org is no longer reachable from a web browser,
 www.linuxtv.org works as usual.

Hm, works for me.

 Unfortunately, the HG repository pages use linuxtv.org... ;-(

linuxtv.org and www.linuxtv.org resolve to the same address,
you can use either to pull from hg.


Johannes

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: TDA8290/TDA8275 with LNA

2007-02-25 Thread Hartmut Hackmann
Hi, Nico

Nico Sabbi schrieb:
 Nico Sabbi wrote:
 Hartmut Hackmann wrote:

 Hi, Nico

 Nico Sabbi schrieb:

 Hi
 I've just noticed that in your tree there's support for the
 pre-amplifier of some Philips cards.
 Does the Lifeview Trio already use your new code? Or do I need to add
 support for it?


 I copy this to the mailing lists because i think this is interesting
 for more people.
 First: the code went to mainstream yesterday.

 Then i should give some explaination of what this is about:
 Many recent cards with the TDA8275a silicon tuner have a preamplifier
 (LNA) in front of the tuner chip. It is *not* inside the chip, and
 since it costs some cents, it will not be on all recent cards.
 This LNA needs to be controlled by the driver. I know about 3 variants
 how this is done, currently, the driver doesn't detect the variant
 automatically. So there is a new entry for the board configuration in
 saa7134-cards.c. Possible values are:
 .tuner_config   = 0, : no LNA present. This is the default
 .tuner_config   = 1, : with LNA. This config is used on the Pinnacle
 310i
 .tuner_config   = 2, : with LNA. This is used on the Philips Tiger-S
 reference
  design and probably on most others.
 .tuner_config   = 3,   with LNA. The new variant. Not sure who uses
 this.
 There is an entry with the same meaning for the tda10046 configuration
 in saa7134-dvb.c
 I should add that the configurations 1 and 3 are untested. I am quite
 sure that 1 is right but not so sure about config 3.



 on a fresly compiled 2.6.20 + a fresh hg pull, after having set
 .tuner_config=2 in lifeview_trio_config  I got:

 saa7133[0]/alsa: saa7133[0] at 0xf3115000 irq 21 registered as card -1
 tda1004x: setting up plls for 48MHz sampling clock
 tda1004x: found firmware revision 29 -- ok
 BUG: unable to handle kernel paging request at virtual address 6b6b6b6b
  printing eip:
 e0f2713b
 
 same crash without my change; it seems that 2.6.20 and saa7134-dvb don't
 get alone at all
 
Thats really strange, i have 2.6.20 running here too and i can't reproduce
this yet.
If i understand the dump right, the crash occurs in a function that has
been called a hundred times before...
I have the impression that the crash did not occur during driver initialization
but in an application. Is that right? Which one was it?
Can you please load the tda1004x module with the option debug=1?

Hartmut

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: TDA8290/TDA8275 with LNA

2007-02-25 Thread Nico Sabbi

Hartmut Hackmann wrote:

Hi, Nico

Nico Sabbi schrieb:



same crash without my change; it seems that 2.6.20 and saa7134-dvb don't
get alone at all



Thats really strange, i have 2.6.20 running here too and i can't reproduce
this yet.
If i understand the dump right, the crash occurs in a function that has
been called a hundred times before...
I have the impression that the crash did not occur during driver initialization
but in an application. Is that right? Which one was it?
Can you please load the tda1004x module with the option debug=1?

Hartmut



yes, during tzap. I re-loaded all modules as you described, but this 
time I had a hard lock, so I can't tell what went wrong ;(


--
Without a frontend, mplayer is useless - someone in mplayer-users

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: [PATCH] Implement repeat key handling in budget-ci IR

2007-02-25 Thread Trent Piepho
On Sun, 25 Feb 2007, Oliver Endriss wrote:
  Does the attached patch fix it for you?

 Ok, I tried to compile against 2.6.18 and it still doesn't work.
 The attached patch fixes it...

The bool type was added here, oct 1 2006:
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6e21828743247270d09a86756a0c11702500dbfb

This was for kernel 2.6.19.  It looks like budget-ci is the first v4l-dvb
driver to use it, so there wasn't any pre-2.6.19 compat code for it yet.

I suggest adding to compat.h:

#ifndef bool
#define int bool
#endif

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DVB/V4L/VDR MediaWiki update

2007-02-25 Thread Oliver Endriss
Johannes Stezenbach wrote:
 On Sun, Feb 25, 2007 at 09:54:05PM +0100, Oliver Endriss wrote:
  Johannes Stezenbach wrote:
   
   I updated the DVB, V4L and VDR Wikis on linuxtv.org
   to MediaWiki version 1.9.3.
   
   If you experience any problems due to the update, then
   please let me know about it.
  
  Don't know whether this is related:
  linuxtv.org is no longer reachable from a web browser,
  www.linuxtv.org works as usual.
 
 Hm, works for me.
 
  Unfortunately, the HG repository pages use linuxtv.org... ;-(
 
 linuxtv.org and www.linuxtv.org resolve to the same address,
 you can use either to pull from hg.

Sure. Pulling from and pushing to HG worked with linuxtv.org, but HTTP
did not work. :-(

Anyway, the problem seems to be solved. Maybe a temporary problem with
address resolution...

Thanks,

Oliver

-- 

VDR Remote Plugin 0.3.9 available at
http://www.escape-edv.de/endriss/vdr/



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: [PATCH] Implement repeat key handling in budget-ci IR

2007-02-25 Thread Oliver Endriss
Trent Piepho wrote:
 On Sun, 25 Feb 2007, Oliver Endriss wrote:
   Does the attached patch fix it for you?
 
  Ok, I tried to compile against 2.6.18 and it still doesn't work.
  The attached patch fixes it...
 
 The bool type was added here, oct 1 2006:
 http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6e21828743247270d09a86756a0c11702500dbfb
 
 This was for kernel 2.6.19.  It looks like budget-ci is the first v4l-dvb
 driver to use it, so there wasn't any pre-2.6.19 compat code for it yet.
 
 I suggest adding to compat.h:
 
 #ifndef bool
 #define int bool
 #endif

Well, should be
  #define bool int
;-)

Anyway, bool is a typedef, and the C preprocessor cannot detect a
typedef. So your #define would replace all occurrences of bool with int,
no matter which kernel you run.

It has already been fixed in HG master:
I added 'typedef int bool;' for kernel  2.6.19.
Tested ok with 2.6.18 and 2.6.20.

Oliver

-- 

VDR Remote Plugin 0.3.9 available at
http://www.escape-edv.de/endriss/vdr/



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Need firmware for M9206

2007-02-25 Thread Nick Andrew
On Sun, Feb 25, 2007 at 02:22:57PM +0100, Pierre Willenbrock wrote:
 My guess is that the lsb is a checksum over the packet.

That makes sense; all the changes are within one packet.

 I have not tried
 to reproduce it, yet. If you look for the firmware in the windows device
 driver, you will probably find that the fields for pid and name are not
 filled.

I looked and found the Ver 0.95 string twice inside the windows device
driver. I dumped 3k of data from those locations in the file and did a
comparison, and I found big differences, but I can't be sure that I
dumped the correct data. Anyway I have a firmware file now so I won't
dig any deeper into windows.

Nick.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: TDA8290/TDA8275 with LNA

2007-02-25 Thread Hartmut Hackmann
HI, Nico

Nico Sabbi schrieb:
 Hartmut Hackmann wrote:
 Hi, Nico

 Nico Sabbi schrieb:
 
 same crash without my change; it seems that 2.6.20 and saa7134-dvb don't
 get alone at all


 Thats really strange, i have 2.6.20 running here too and i can't
 reproduce
 this yet.
 If i understand the dump right, the crash occurs in a function that has
 been called a hundred times before...
 I have the impression that the crash did not occur during driver
 initialization
 but in an application. Is that right? Which one was it?
 Can you please load the tda1004x module with the option debug=1?

 Hartmut

 
 yes, during tzap. I re-loaded all modules as you described, but this
 time I had a hard lock, so I can't tell what went wrong ;(
 
Hm, there seems to be a mad pointer or a buffer overflow somewhere.
Any additional hint is welcome so that i at least can reproduce
the problem.
Do you run a 64 bit system. Did your card work with the drivers
from the kernel distribution?

Hartmut

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: TDA8290/TDA8275 with LNA

2007-02-25 Thread Nico Sabbi

Hartmut Hackmann wrote:



Hm, there seems to be a mad pointer or a buffer overflow somewhere.
Any additional hint is welcome so that i at least can reproduce
the problem.
Do you run a 64 bit system. Did your card work with the drivers
from the kernel distribution?

Hartmut



my system is a 32-bit p4, running everything from vanilla 2.6.20,
except for the dvb drivers (taken from hg of course).
my gcc is 4.0.2; may it lead to problems? yet it worked well
with Steve Thoth's multi-frontend branch and older hg pulls.
Tomorrow I'll recompile everything from scratch after having removed
the modules directory, then I'll let you know

--
Without a frontend, mplayer is useless - someone in mplayer-users

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Need firmware for M9206

2007-02-25 Thread Aapo Tahkola
On Mon, 26 Feb 2007 10:58:52 +1100
Nick Andrew [EMAIL PROTECTED] wrote:

 On Sun, Feb 25, 2007 at 02:22:57PM +0100, Pierre Willenbrock wrote:
  My guess is that the lsb is a checksum over the packet.
 
 That makes sense; all the changes are within one packet.
 
  I have not tried
  to reproduce it, yet. If you look for the firmware in the windows
  device driver, you will probably find that the fields for pid and
  name are not filled.

Could be that it copies them on the fly.

 
 I looked and found the Ver 0.95 string twice inside the windows
 device driver. I dumped 3k of data from those locations in the file
 and did a comparison, and I found big differences, but I can't be
 sure that I dumped the correct data. Anyway I have a firmware file
 now so I won't dig any deeper into windows.

There have been some problems with some host controllers in the past
that might explain those two firmwares. Also, one digivox we got
working earlier has had stability issues on another computer.

-- 
Aapo Tahkola

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] freecom usb stick troubles

2007-02-25 Thread Nick Andrew
On Sun, Feb 25, 2007 at 09:49:03PM +0800, James Shirley wrote:
 and only deviated when i couldn't connect with
 http://thadathil.net:8000/dvb/fw/
 is this server down, or just refusing me for some reason?

I got the same, over a few days. If they can't keep the server up
it should be taken out of the wiki.

Also the Documentation/dvb/get_dvb_firmware script specifies:
http://linuxtv.org/ sometimes and http://www.linuxtv.org/
at other times. It should be a consistent URL, and the other
day it looked like linuxtv.org didn't have an A record, but
it has one now.

Nick.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Need firmware for M9206

2007-02-25 Thread Nick Andrew
On Mon, Feb 26, 2007 at 02:30:02AM +0200, Aapo Tahkola wrote:
 Could be that it copies them on the fly.

That's certain, because the earlier bytes don't appear in the
.sys file.  I guess the first few bytes of the firmware are data
constants rather than code, and windows fills them in.

I got the device working under (real) Windows XP; the blue power
light doesn't come on when the firmware is loaded, only when the
Windows application is running.

Is further firmware required for the TDA10046A ?

 There have been some problems with some host controllers in the past
 that might explain those two firmwares. Also, one digivox we got
 working earlier has had stability issues on another computer.

Has it got enough power?

Nick.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] skystar 1 and 2.6

2007-02-25 Thread tasos
hello ppl and nice  to meet you.
every time i re install my slackware i always have
problems make my card to work.i own a skystar 1.

so i decided to use 2.6.20.1 but i don't see anything
related to skystar1.
any ideas please?

#
# Supported SAA7146 based PCI Adapters
#

thank you in advance!



 

We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265 

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Re: [PATCH] Implement repeat key handling in budget IR

2007-02-25 Thread Trent Piepho
On Mon, 26 Feb 2007, Oliver Endriss wrote:
 Trent Piepho wrote:
  The bool type was added here, oct 1 2006:
  http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6e21828743247270d09a86756a0c11702500dbfb
 
  This was for kernel 2.6.19.  It looks like budget-ci is the first v4l-dvb
  driver to use it, so there wasn't any pre-2.6.19 compat code for it yet.
 
  I suggest adding to compat.h:
 
  #ifndef bool
  #define int bool
  #endif

 Well, should be
   #define bool int

I meant typedef int bool actually, but it doesn't matter.

 Anyway, bool is a typedef, and the C preprocessor cannot detect a
 typedef. So your #define would replace all occurrences of bool with int,
 no matter which kernel you run.

You're right.  I also realize that the existing check for #ifndef true in
compat.h doesn't work either!  true and false are part of an enum defined
in linux/stddef.h, not macros.

If compat.h appears before linux/stddef.h, then stddef.h doesn't compile
because of the #define true 1 bit.  But if stddef.h is first, then
everything appears to work.  I thought this must be because the
#ifndef true
in compat.h was working, which wasn't what I expected, but seemed to
explain why there were no errors.  But now I realize that changing true to
1 on current kernels, while unnecessary, isn't actually going to cause a
problem (other than the definition of true in stddef.h).

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] AGC settings for dtt761x, removal of lgh06xf driver

2007-02-25 Thread Trent Piepho
Some tuners benefit from changing the AGC take over point from its default
value.  For my HD-3000 with a Thomson DTT7612, it appears to increase SNR
by 0.19 dB.  I tested it against my weakest (20.0 dB) and strongest (28.2
dB) OTA stations.  Both SNR readings went up by an average 0.19 dB from
when the agc-top was set to 103 dBuV (which was the best) from the default
value of 112 dBuV.  There was no significant difference in the effect of
agc-top between the two stations.  I observed this same effect earlier when
testing with digital cable.

http://linuxtv.org/hg/~tap/v4l-dvb

These patches add support in dvb-pll for sending an initialization sequence
to the pll when the tuner is opened.  A sequence to adjust the AGC TOP to
103 dBuV by setting the aux byte to 0x50 is added for the Thomson DTT761x
and LG H06xF tuners.  Since the lgh06xf driver's only significant
difference from dvb-pll is that it sets this value, it is no longer
necessary and can be removed.

I would appreciate it if anyone with a card with a DTT761x or LG-H06xF
tuner could test this patch and see if it improves their SNR (DTT761x) or
continues to work as it did before (lgh06xf).

Specifically, I'm worried about this possible problem, from my patch
comments:

There is one other difference.  dvb-pll will probe for the presence of an
I2C pll chip by doing a one byte read, the lgh06xf driver did not do
this.  In some devices the PLL is not reachable over I2C at the time the
tuner is attached.  Some more initialization, such as firmware loading,
must take place first.  If any of these devices are former LG-H06xF
users, something must be done to disable this probe or enable I2C before
attaching the tuner.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] HW reco's for Toroidal dish in US

2007-02-25 Thread Philip Prindeville
Hi.

I'm trying to set up a T90 dish for FTA reception here in the US,
but I'm having a hard time finding switches that would have having
7 or 8 LNB's worth the trouble (especially if the LNB's are
unswitched with LH and RH routed to different outputs)...   None
of the retails (or wholesalers?) seem to have a switch that can
handle 16 or 20 inputs.

Also, what's a good LNB to use on the T90's?  If I'm setting up
the channel configurations myself, I can always replace 'V' with
'H' and vice versa to get the polarization inverted...  Oh, wait,
it's only the circular transponders that are affected, right?  Not
the linear ones.

Are there any popular universal LP budget tuner cards out there?
Has anyone used the VP1020A's?

And lastly...  I'm thinking of setting up a 2m motorized dish with
stacked C and Ku band LNB's.  I looked at the BSC621, but it
looks like the C is switched... actually the Ku is switched also.
I was hoping to be able to have receivers on the C band, and
Ku band polarizations simultaneously (i.e. both V and H
polarization).

Is there such a beast?

Thanks,

-Philip


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb