Re: [linux-dvb] Switching tuner to analogue mode on Compro VideoMate DVB-T300

[Tomislav Bodor]

Tomislav Bodor wrote:
> Oops. I sent an empty message by mistake. Here's the real thing (at the
> bottom).
>
>
> Hartmut Hackmann wrote:
>   
>> Hi,
>>
>> Tomislav Bodor wrote:
>> 
>>> Hartmut Hackmann wrote:
>>>
>>>   
 Hi,

 Tomislav Bodor wrote:

 
> Hi,
>
> I am having problems getting the DVB-T300 to switch to analogue mode
> once the digital part of the tuner has been accessed. The only way I
> found seems to be to unload the saa7134-dvb module and reload saa7134.
> I'm using the drivers from vanilla 2.6.18 kernel, but I checked the
> relevant sections (see below) against mercurial and they seem to be
> the
> same.
>
> Now, I have had a look at how this is supposed to be switched back to
> analogue and have found the sleep function (the one used for
> DVB-T300 is
> philips_europa_tuner_sleep) and the way it's called from
> dvb_frontent.c
> after dvb_shutdown_timeout expires. This all seems to work (and the
> sleep function is called correctly), but the tuner stays in digital
> mode.
>
> Does anyone have an idea why this might not work? Maybe the i2c
> messages
> are wrong for this card? Unfortunately this is all completely new
> to me,
> but I'm happy to test any patches :)
>
>
>   
 There have been 2 big changes since i added support for this card.
 I worried about the tda9887 merge in the tuner module, but the
 effect i worried about is a bit different from what you describe.
 - are there any error messages in the kernel log?
 - does analog tv work immedeately after module load?
 Any additional information will help.
 
>>> Sure. Unfortunately, I don't know what's useful information and what's
>>> not, so I may overload you :)
>>>
>>> I'll tackle the latter first: analog works just fine after saa7134
>>> module is loaded (this for me happens automatically during boot). It
>>> continues working even after saa7134-dvb is loaded, all the way until I
>>> run any dvb application (e.g. scan or mythbackend with a DVB card
>>> configured). Once a dvb device is accessed the card is switched to
>>> digital mode (and I can watch digital TV just fine).
>>>
>>> Now for the first question: from that point onwards digital works fine,
>>> but accessing the card in analogue mode (say using tvtime or mythtv via
>>> the analogue tuner) produces the following errors in the kernel log:
>>>
>>> Oct  2 16:04:38 localhost kernel: [  540.007478] tuner 1-0061: i2c i/o
>>> error: rc == -5 (should be 4)
>>> Oct  2 16:04:38 localhost kernel: [  540.015462] tuner 1-0061: i2c i/o
>>> error: rc == -5 (should be 4)
>>> Oct  2 16:04:38 localhost kernel: [  540.023452] tuner 1-0061: i2c i/o
>>> error: rc == -5 (should be 4)
>>> Oct  2 16:04:38 localhost kernel: [  540.131306] tuner 1-0061: i2c i/o
>>> error: rc == -5 (should be 4)
>>> Oct  2 16:04:38 localhost kernel: [  540.139289] tuner 1-0061: i2c i/o
>>> error: rc == -5 (should be 4)
>>> Oct  2 16:04:38 localhost kernel: [  540.215214] tuner 1-0061: i2c i/o
>>> error: rc == -5 (should be 4)
>>>
>>>   
>> This is the information i was looking for. There is something going wrong
>> with the I2c bridge.
>>
>> 
>>> They come in batches of six at a time every time I start tvtime and then
>>> one at a time every time I change channels.
>>>
>>>   
>> 
>> 
>>> And this reminds me: I never downloaded any firmware for tda10046 - it
>>> just worked this way, though various documentation says that I should
>>> use the get_dvb_firmware script from linux/Documentation/dvb. Why is it
>>> working without firmware (out of curiosity)?
>>>
>>>   
>> Some cards have an eeprom with the Firmware. Yours too. In this case,
>> the channel decoder boots from this.
>>
>> This is a quick shot: can you please try to force the card type to69?
>> So:
>> modprobe saa7134 card=69
>> modprobe saa7134-dvb
>> (after you unloaded these modules)
>>
>> Hartmut
>>
>>
>> 
>
> That did it - it now works as expected: after a delay of about 5
> seconds, the tuner switches back to analogue mode. I have had a look at
> the way the reference Philips Europa card is set up in saa7134-dvb.c and
> I see that DVB-T300 is missing one of the sleep functions - tuner has
> one, but the front end doesn't. Maybe there's more, but I don't know.
> Not sure what went wrong and when. I presume you know what needs to be
> done from this point onwards?
>
> Anyway, this workaround seems perfectly fine for now. Do you think there
> is any functionality I will be missing compared to using card=70?
>   

Ah. I see something missing: the remote input device is not initialised
when I use card=69. With card=70 it's initialised correctly. This is a
problem - I need the remote. If I try tweaking the code for DVB-T300 in
saa7134-dvb to make it more similar to what's going on for Philips
Europa reference, will that take me anywhere? Or is it mor

Re: [linux-dvb] [patch 0/8] budget_ci: improve IR input handling

[Oliver Endriss]

Torgeir Veimo wrote:
> 
> On 3 Oct 2006, at 21:43, C.Y.M wrote:
> 
> > David Härdeman wrote:
> >> On Tue, October 3, 2006 2:33, C.Y.M said:
> >>> David Härdeman wrote:
>  This series of patches includes a number of bugfixes and changes  
>  to the
>  IR input handling of the budget-ci driver.
> >>> If these patches are successful, can they also be implemented  
> >>> into the
> >>> regular nexus-s ir drivers too?
> >>
> >> Which driver is that? av7110?
> >
> > Yes.
> >
> >>
> >>> I have the same lirc issues with my full featured
> >>> nexus card as others do with hauppauge budget cards.
> >>
> >> I'm sorry, but I don't quite follow...the ir driver for the av7110  
> >> uses
> >> the Linux input system (i.e. appears as a keyboard more or less),  
> >> why use
> >> LIRC? Exactly what issues do you have?
> >
> > If I want to use Mythtv with the Nexus-S, then I have to use LIRC.   
> > But,
> > everyone that I talk to with a hauppauge card seems to have a  
> > "double key press"
> > problem when trying to use LIRC with those built in IR sensors.
> 
> Those double keypress issues are also present when using the linux  
> input system, it's not LIRC dependent at all.

In fact there are _no_ double key press issues with the input system.

The 'problem' is that the keyboard driver and the the application
attached to /dev/input/eventX receive a key press from the remote
control.

Solution:
The application must grab the input device for exclusive access.
In other words: Get LIRC fixed. ;-)

Oliver

-- 

VDR Remote Plugin 0.3.8 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

[linux-dvb] SkyStar2 stops receiving data

[Dmitry V'yal]

Hello, everyone.

I'm using SkyStar2.6d on Gentoo Linux-2.6.16.28.
It works, but have some stability issues, if it can't be called so.
Card frequently lose the lock then it's rainy. Then weather clears, 
lock is
reacquired. Usually it's just a temporary inconvenience, but sometimes
strange(imo) things happen.
In that case femon, as usual, shows something around my usual signal level
# femon
using '/dev/dvb/adapter0/frontend0'
FE: ST STV0299 DVB-S (SAT)
status 1f | signal bba4 | snr c243 | ber 09b9 | unc  | FE_HAS_LOCK
status 1f | signal bbfb | snr c1e6 | ber 0028 | unc  | FE_HAS_LOCK
status 1f | signal bb21 | snr c23a | ber 0010 | unc  | FE_HAS_LOCK
status 1f | signal bb68 | snr c1da | ber 000f | unc  | FE_HAS_LOCK
status 1f | signal bbdf | snr c216 | ber 001c | unc  | FE_HAS_LOCK
status 1f | signal bba0 | snr c22e | ber 0040 | unc  | FE_HAS_LOCK

But no data is being received, and dvbtraffic can't find any pids, neither does
dvbsnoop.
I tried szapping to another transponders with no effect. The only option seems
to manually bring down dvb0_0 interface, remove it, and reload kernel modules
concerning dvb and bring up dvb0_0. After that all goes well again usually.
The box is used for sharing satellite internet on lan so I'm really 
concerned
about such a (mis)behavior. I would be happy with an advice.

Thanks in advance,

--

Dmitry V'yal.




# lsmod
Module  Size  Used by
b2c2_flexcop_pci6008  7
b2c2_flexcop   22060  1 b2c2_flexcop_pci
mt352   5348  1 b2c2_flexcop
mt312   6404  1 b2c2_flexcop
bcm3510 8772  1 b2c2_flexcop
stv0299 9000  1 b2c2_flexcop
dvb_core   65256  2 b2c2_flexcop,stv0299
stv0297 6464  1 b2c2_flexcop
nxt200x12068  1 b2c2_flexcop
dvb_pll 9284  2 b2c2_flexcop,nxt200x
lgdt330x6652  1 b2c2_flexcop
ppp_async   7712  4
crc_ccitt   1792  1 ppp_async
ipt_MASQUERADE  2496  1
iptable_nat 5924  1
ip_nat 12940  2 ipt_MASQUERADE,iptable_nat
ip_conntrack   38028  3 ipt_MASQUERADE,iptable_nat,ip_nat
xt_comment  1536  13
xt_mac  1760  7
iptable_filter  2176  1
ipt_TTL 1984  1
iptable_mangle  2176  1
ip_tables   9464  3 iptable_nat,iptable_filter,iptable_mangle
x_tables8708  6
ipt_MASQUERADE,iptable_nat,xt_comment,xt_mac,ipt_TTL,ip_tables
via_rhine  16964  0

# uname -a
Linux sat_servant 2.6.16.28 #3 Sun Sep 3 00:26:57 MSD 2006 i686 Pentium III
(Coppermine) GenuineIntel GNU/Linux

 # lspci
:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x]
(rev 01)
:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
MVP3/Pro133x AGP]
:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo
VP] (rev 47)
:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
:00:07.3 Host bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
:00:10.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] 
(rev 86)
:00:13.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB
chip / Technisat SkyStar2 DVB card (rev 02)
:01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200
PRO] (rev 01)
:01:00.1 Display controller: ATI Technologies Inc: Unknown device 5940 (rev 
01)

# equery list linuxtv
[ Searching for package 'linuxtv' in all categories among: ]
 * installed packages
[I--] [M~] media-tv/linuxtv-dvb-apps-1.1.1-r1 (0)
[I--] [  ] media-tv/linuxtv-dvb-headers-3.1 (0)

# sysctl -a |grep dvb
error: unknown error 1 reading key 'net.ipv4.route.flush'
net.ipv4.conf.dvb0_0.promote_secondaries = 0
net.ipv4.conf.dvb0_0.force_igmp_version = 0
net.ipv4.conf.dvb0_0.disable_policy = 0
net.ipv4.conf.dvb0_0.disable_xfrm = 0
net.ipv4.conf.dvb0_0.arp_ignore = 0
net.ipv4.conf.dvb0_0.arp_announce = 0
net.ipv4.conf.dvb0_0.arp_filter = 0
net.ipv4.conf.dvb0_0.tag = 0
net.ipv4.conf.dvb0_0.log_martians = 0
net.ipv4.conf.dvb0_0.bootp_relay = 0
net.ipv4.conf.dvb0_0.medium_id = 0
net.ipv4.conf.dvb0_0.proxy_arp = 0
net.ipv4.conf.dvb0_0.accept_source_route = 1
net.ipv4.conf.dvb0_0.send_redirects = 1
net.ipv4.conf.dvb0_0.rp_filter = 0
net.ipv4.conf.dvb0_0.shared_media = 1
net.ipv4.conf.dvb0_0.secure_redirects = 1
net.ipv4.conf.dvb0_0.accept_redirects = 1
net.ipv4.conf.dvb0_0.mc_forwarding = 0
net.ipv4.conf.dvb0_0.forwarding = 1
net.ipv4.neigh.dvb0_0.base_reachable_time_ms = 3
net.ipv4.neigh.dvb0_0.retrans_time_ms = 1000
net.ipv4.neigh.dvb0_0.locktime = 100
net.ipv4.neigh.dvb0_0.proxy_delay = 80
net.ipv4.neigh.dvb0_0.anycast_delay = 100
net.ipv4.neigh.dvb0_0.proxy_qlen = 64
net.ipv4.neigh.dvb0_0.unres_qlen = 3
net.ipv4.neigh

Re: [linux-dvb] m920x : Pinnacle PCTV 310e support

[KevinLuX]

cedbor ha scritto:

I recently purchased a Pinnacle PCTV 310e hybrid analog/dvb-t usb box
and discovered that there's no support for it under linux.

Windows drivers are m9205.sys and m9207bda.sys, so i suppose that m920x
should support it.

Is there anything i can do to help developpers add this device to v4l
trunk?

Regards
cedbor
  

Hi,
maybe your card differs from my (310i) only for the interface your USB 
..my PCI.
If this is true try to load module saa7134 with the option card=77, and 
see dmesg

this will enable the analog part, and try to get it working!
Try to search information about the chip on your card.!!

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

Re: [linux-dvb] [patch 0/8] budget_ci: improve IR input handling

[C.Y.M]

David Härdeman wrote:
> On Tue, October 3, 2006 2:33, C.Y.M said:
>> David Härdeman wrote:
>>> This series of patches includes a number of bugfixes and changes to the
>>> IR input handling of the budget-ci driver.
>> If these patches are successful, can they also be implemented into the
>> regular nexus-s ir drivers too?
> 
> Which driver is that? av7110?

Yes

> 
>> I have the same lirc issues with my full featured
>> nexus card as others do with hauppauge budget cards.
> 
> I'm sorry, but I don't quite follow...the ir driver for the av7110 uses
> the Linux input system (i.e. appears as a keyboard more or less), why use
> LIRC? Exactly what issues do you have?
> 

If I want to use Mythtv with the Nexus-S, then I have to use LIRC.  But,
everyone that I talk to with a hauppauge card seems to get double key presses
when they try to use LIRC on that built in IR sensors.

Best Regards.


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

Re: [linux-dvb] [patch 0/8] budget_ci: improve IR input handling

[Torgeir Veimo]

On 3 Oct 2006, at 21:43, C.Y.M wrote:


David Härdeman wrote:

On Tue, October 3, 2006 2:33, C.Y.M said:

David Härdeman wrote:
This series of patches includes a number of bugfixes and changes  
to the

IR input handling of the budget-ci driver.
If these patches are successful, can they also be implemented  
into the

regular nexus-s ir drivers too?


Which driver is that? av7110?


Yes.




I have the same lirc issues with my full featured
nexus card as others do with hauppauge budget cards.


I'm sorry, but I don't quite follow...the ir driver for the av7110  
uses
the Linux input system (i.e. appears as a keyboard more or less),  
why use

LIRC? Exactly what issues do you have?


If I want to use Mythtv with the Nexus-S, then I have to use LIRC.   
But,
everyone that I talk to with a hauppauge card seems to have a  
"double key press"

problem when trying to use LIRC with those built in IR sensors.


Those double keypress issues are also present when using the linux  
input system, it's not LIRC dependent at all.


--
Torgeir Veimo
[EMAIL PROTECTED]




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

Re: [linux-dvb] [patch 0/8] budget_ci: improve IR input handling

[C.Y.M]

David Härdeman wrote:
> On Tue, October 3, 2006 2:33, C.Y.M said:
>> David Härdeman wrote:
>>> This series of patches includes a number of bugfixes and changes to the
>>> IR input handling of the budget-ci driver.
>> If these patches are successful, can they also be implemented into the
>> regular nexus-s ir drivers too?
> 
> Which driver is that? av7110?

Yes.

> 
>> I have the same lirc issues with my full featured
>> nexus card as others do with hauppauge budget cards.
> 
> I'm sorry, but I don't quite follow...the ir driver for the av7110 uses
> the Linux input system (i.e. appears as a keyboard more or less), why use
> LIRC? Exactly what issues do you have?

If I want to use Mythtv with the Nexus-S, then I have to use LIRC.  But,
everyone that I talk to with a hauppauge card seems to have a "double key press"
problem when trying to use LIRC with those built in IR sensors.

Best Regards.



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

[linux-dvb] Winfast 2000XP (CX23880) with Y0400052 IR remote control

[Adam Kłobukowski]

Hello. I hope it is a correct list.

Card identification:
00:0a.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video 
and Audio Decoder (rev 05)


uname -a:
Linux adamk 2.6.17-10-386 #2 Tue Sep 26 16:51:46 UTC 2006 i686 GNU/Linux

Distro:
Ubuntu Edgy

I got some "unknown key" messages when I'm pressing some keys on the 
remote. Here they are with keys pressed:


TV key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x36 raw=0x36 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x36 raw=0x36 down=0

FM key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x37 raw=0x37 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x37 raw=0x37 down=0

DVD key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x38 raw=0x38 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x38 raw=0x38 down=0

BossKey key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x29 raw=0x29 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x29 raw=0x29 down=0

C key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x30 raw=0x30 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x30 raw=0x30 down=0

Menu key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x2f raw=0x2f down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x2f raw=0x2f down=0

CH.Surf key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x31 raw=0x31 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x31 raw=0x31 down=0

Subtitles key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x32 raw=0x32 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x32 raw=0x32 down=0

Rewind key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x34 raw=0x34 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x34 raw=0x34 down=0

Forward key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x35 raw=0x35 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x35 raw=0x35 down=0

Language key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x33 raw=0x33 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x33 raw=0x33 down=0

Audio key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x1b raw=0x1b down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x1b raw=0x1b down=0

Display key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x16 raw=0x16 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x16 raw=0x16 down=0

SnapShot key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x28 raw=0x28 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x28 raw=0x28 down=0

PIP key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x2a raw=0x2a down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x2a raw=0x2a down=0

Time Shifting key:
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x25 raw=0x25 down=1
cx88 IR (Leadtek Winfast 2000XP: unknown key: key=0x25 raw=0x25 down=0

Otherwise card works fine, out of the box :)

--
Semper Fidelis

Adam Klobukowski
[EMAIL PROTECTED]

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

Re: [linux-dvb] ASUSTEK P7131 Dual TV dvb mode?

[v+dvb]

On Tue, Oct 03, 2006 at 12:06:53AM +0200, you [hermann pitton] wrote:
> 
> oops, you mentioned you use "fm" from fmtools and I didn't remember
> immediately that there is an issue with it and this radio tuner, but I
> pointed to it in another mail today on the video4linux-list.
> 
> fm just tunes in and quits, but this tuner goes to standby, if not used.

Ah, ok. I noticed the quitting issue as well.

> Unfortunately after using "fm" it produces unmuted noise.
> Use kradio (v4l2!) or radio from xawtv. Gnomeradio should be fine too,
> but don't have it installed currently on that machine.

After finding out 'fm' does not work (fully) I've been solely using
gnomeradio.
 
> "while true; do ./fm -d /dev/radio1 102.5 62000; done"
> gives me continious cracks too. 

Yeah, those are not the cracks I was talking about. Sorry for the confusion.

The cracks I hear with gnomeradio (caused most likely weak signal) are
_much_ shorter and frequent.

> Must be caused by walking ioctls.
> With the other apps 
> "arecord -D hw:2,0 -r 32000 -c 2 -f S16_LE | aplay" in my case works
> fine.

It does work with gnomeradio, but as said there's the crackling sound (I
think we can conclude it's a signal issue and forget about it unless
something suggests otherwise) and the arecord|aplay issue going out of sync
issue. 
 
> Also don't get dsp access errors. 

They might be related to the arecord|aplay out of sync issue.

> Do they persist after reloading the modules? 

I think I did unload and reload once, and the issue reappeared, but I can
retry.

> Hmm, maybe some incompatible
> alsa stuff.

Perhaps.
 
> For the antenna input question in your previous mail, yes, you can just
> use the cable-tv input for DVB-T without using radio previously. This
> will change as soon Hartmut picks up the patch, which automates the DVB-
> T antenna input setting from within saa7134-dvb for that card.

Ok. Thanks!



-- v -- 

[EMAIL PROTECTED]


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

[linux-dvb] m920x : Pinnacle PCTV 310e support

[cedbor]

I recently purchased a Pinnacle PCTV 310e hybrid analog/dvb-t usb box
and discovered that there's no support for it under linux.

Windows drivers are m9205.sys and m9207bda.sys, so i suppose that m920x
should support it.

Is there anything i can do to help developpers add this device to v4l
trunk?

Regards
cedbor



Hardware : 

m9207 (ULi) a/v usb2 controller
mt352 (Zarlink) dvb-t demodulator
tvp5150 (Texas Instruments) video decoder
tda9887h (Philips) analog demodulator
Philips fmd1216me tuner (analog/dvb-t/fm)

Someone's posted pictures of the pcb here:
http://mypage.bluewin.ch/ac007/video4linux/Pinnacle_PCTV_310e-a.jpg
http://mypage.bluewin.ch/ac007/video4linux/Pinnacle_PCTV_310e-b.jpg


lsusb -v is here:
(finishes with : can't get debug descriptor: Connection timed out)


Bus 003 Device 004: ID 13d3:3211 IMC Networks
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x13d3 IMC Networks
  idProduct  0x3211
  bcdDevice0.91
  iManufacturer   0
  iProduct1 Pinnacle PCTV
  iSerial 2 09001FDE
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  223
bNumInterfaces  4
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xc0
  Self Powered
MaxPower   50mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   1
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x02bc  1x 700 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   2
  bNumEndpoints   1
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x1400  3x 0 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass 1 Audio
  bInterfaceSubClass  1 Control Device
  bInterfaceProtocol  0
  iInterface  0
  AudioControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdADC   1.00
wTotalLength   30
bInCollection   1
baInterfaceNr( 0)   2
  AudioControl Interface Descriptor:
bLength12
bDescriptorType36
bDescriptorSubtype  2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType  0x0201 Microphone
bAssocTerminal  0
bNrChannels 2
wChannelConfig 0x
iChannelNames   0
iTerminal   0
  AudioControl Interface Descriptor:
bLength   

[linux-dvb] Improved rmmod.pl script

[Klaus Schmidinger]

The rmmod.pl script that comes with the current driver source
blindly tries to load all modules it can find. While this is
good in case one has no idea which modules to load, there's
no easy way of finding out exactly which modules need to be loaded
to support just the installed hardware (unless I've missed it).

The attached version of this script accepts additional
parameters, which can be used to specify the "top level"
driver modules to load, and starting from there it loads
all other modules that the given ones depend on.

For a system with full featured and budget DVB cards, the call
might look like this:

  rmmod.pl load dvb-ttpci budget

The modified script also makes sure that the explicitly
mentioned modules are loaded in the given sequence, so
that the sequence of devices can be defined (for instance
making sure that the first device is a full featured card).

This also works with 'reload', as in

  rmmod.pl reload dvb-ttpci budget

So this could be the only line necessary in a 'runvdr'
script, because it first unloads all given modules and
the ones they depend on (if any are loaded) and then loads
the given ones plus the ones they depend on.

Without the additional parameters the behavior is as before.

Maybe this is also useful to others. If so, perhaps it could
be checked in to the Mercurial by somebody with write access.

Klaus


rmmod.pl
Description: Perl program
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] FusionHDTV DVB-T Dual Digital2

[Michael Krufky]

Michael Krufky wrote:
> Here is a quick way to get things working for your device... Please
> follow these instructions verbatim:
> 
> 1) hg clone http://linuxtv.org/hg/~mkrufky/cxusb
> 
> 2) cd cxusb
> 
> 3) hg export 56cb67d6c632 > FusionHDTVdual2.patch
> 
> 4) cd ..
> 
> 5) hg clone http://linuxtv.org/hg/~pascoe/v4l-dvb-rounding
> 
> 6) cd v4l-dvb-rounding
> 
> 7) hg import ../cxusb/FusionHDTVdual2.patch
> 
> 8) make
> 
> 9) sudo make install
> 
> That should do it!
> 
> Please reply-to-all after you've tested this... Chris is looking for
> feedback on the changes in his tree, and your testing will be helpful in
> evaluating whether or not this fixes your problem.

The list dropped the cc to Chris, so I'm resending... Sorry for the
double email. Please make sure that both Chris and I (and the linux-dvb
list, of course) are cc'd when you reply to this.

Cheers,

Michael Krufky


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

Re: [linux-dvb] FusionHDTV DVB-T Dual Digital2

[Michael Krufky]

Mark McKenzie wrote:
> I've tried a few things over the last few days:
> 
> - I grabbed a channels.conf from one of my collegues who lives quite close to 
> where I do, and configured mplayer to use it. No dice.
> 
> - Borrowed a similar tuner (DViCO FusionHDTV DVB-T USB usbid 0fe9:db11) and 
> got that working no problems. Generated a conf from it, watched a couple of 
> channels, etc so its definatly not a signal issue.
> 
> - Put the Dual Digital 2 back in and tried it with the newly generated conf; 
> the card locked up again.
> 
> I'm starting to think it might be something to do with when its locking onto 
> a 
> signal. I'm probably going to put some kprobes into the kernel and see whats 
> going on right before the lockup.
> 
> If you think it would be of some benefit, I can come onto IRC sometime and we 
> can try and work out whats going on. What timezone are you in?

G...

I know what the problem is...  It has everything to do with the tuning
code in that Dnos104z NIM (incorrectly labeled, 'dee1601' in the kernel
code)

Chris Pascoe has found a way to fix this, but the fix has not yet been
merged into the master branch.

See here:

http://linuxtv.org/hg/~pascoe/v4l-dvb-rounding

If you want to find me on irc, I am there right now.  I am in New York,
-0500 ...  #linuxtv on irc.freenode.net

Here is a quick way to get things working for your device... Please
follow these instructions verbatim:

1) hg clone http://linuxtv.org/hg/~mkrufky/cxusb

2) cd cxusb

3) hg export 56cb67d6c632 > FusionHDTVdual2.patch

4) cd ..

5) hg clone http://linuxtv.org/hg/~pascoe/v4l-dvb-rounding

6) cd v4l-dvb-rounding

7) hg import ../cxusb/FusionHDTVdual2.patch

8) make

9) sudo make install

That should do it!

Please reply-to-all after you've tested this... Chris is looking for
feedback on the changes in his tree, and your testing will be helpful in
evaluating whether or not this fixes your problem.

Regards,

Michael Krufky


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

Re: [linux-dvb] dvb noaudio

[Christophe Thommeret]

Le Mardi 03 Octobre 2006 13:11, Raena Lea-Shannon a écrit :

> mp3 will not play
> wav and ogg play

So, your xine-lib lacks mpeg (for patent reasons i guess).
You have to install an unrestricted xine-lib.

-- 
Christophe Thommeret

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

[linux-dvb] nvidia 3d module prevent to work module saa7134?

[KevinLuX]

Hi,
hi have ubuntu dapper with vanilla kernel and hg mercurial clone.
I have compiled and installed v4l-dvb.
My card is a pinnacle 310i both dvb and analog.
In analog mode with saa7134 card=77 if Xorg run with the new nvidia 
driver /(1.0-9625
Linux Display Driver – x86 
Release 
Date: September 21)/
and 3d accelleration active, tv time doesn't work is slow and give me a 
blu screen.

Also xawtv zapping and xtv. scan channel works good.
I have disabled nvidia module and all works good!

Any suggestions ?'

Thanks in advance!

ps. harmut i'm waiting for you patch to get working pinnacle 310i in dvb 
mode :P


byeee

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

Re: [linux-dvb] FusionHDTV DVB-T Dual Digital2

[Mark McKenzie]

I've tried a few things over the last few days:

- I grabbed a channels.conf from one of my collegues who lives quite close to 
where I do, and configured mplayer to use it. No dice.

- Borrowed a similar tuner (DViCO FusionHDTV DVB-T USB usbid 0fe9:db11) and 
got that working no problems. Generated a conf from it, watched a couple of 
channels, etc so its definatly not a signal issue.

- Put the Dual Digital 2 back in and tried it with the newly generated conf; 
the card locked up again.

I'm starting to think it might be something to do with when its locking onto a 
signal. I'm probably going to put some kprobes into the kernel and see whats 
going on right before the lockup.

If you think it would be of some benefit, I can come onto IRC sometime and we 
can try and work out whats going on. What timezone are you in?

Mark

On Friday 29 September 2006 22:27, Michael Krufky wrote:
> Mark wrote:
> > Incidentally, I checked the inf file from the windows driver that came on
> > the CD - it definatly has the USB id in it for the card. Is there any way
> > I can extract the firmware? Maybe they've updated it for this particular
> > card.
>
> Nope -- the firmware is the same, I checked.
>
> Scan seems to be working properly (except for the lockup) ... Can you
> try to get a video stream using your favorite tool?  ie: tzap + mplayer,
> mplayer alone, kaffeine, xine, whatever?
>
> ---
>
> Try unloading the dvb-usb-cxusb and dvb-usb modules, then turn on debug
> in the dvb-usb module... (see modinfo dvb-usb -- the debug settings are
> or-able) and load up the dvb -usb-cxusb module again... Try to reproduce
> the lockup above -- we should see better info in dmesg this time.
>
> Next time it locks up. does yanking out the usb plug unlock it?
> (Expect an oops if you yank it while it's in use)
>
> ---
>
> I think this locking up problem is not directly related to the new
> hardware or driver -- DViCO says it is exactly identical to the hardware
> used in the prior version.
>
> Thanks for testing, hopefully we can solve your lockup problem as well.
>
> Cheers,
>
> Mike

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

Re: [linux-dvb] TS Stream - null packets generation?

[Thomas Pinz]

Hi, 

On Tuesday 03 October 2006 10:29, Chun Chung Lo wrote:
> I am now using a STB (under development) which its hardware
> configuration is:
And if you are using GPL'd software, of course you are considering the legal 
sitation ?  [1]

> When I capture the TS stream (which is stream out by a DVB-T modulator),
> and compare the file with the original one, I found tones of NULL
> packets (which its header is 0x47 0x1F, 0xFF 0x10, and remains are 0x00
> ... Until the end of a TS packets, 188bytes).
> And where are the TS null packets come from?
Thats called bit-stuffing and is simply very normal in any DVB signal. 

Your video/audio/data-stream in your DVB-signal is coded at a variable data 
rate, depending on the content. The channel capacity of the desired 
DVB-channel is fixed. And so the unused part of the capacity is simply filled 
with Null-Packets. 
But this should be also described in the manual of your modulator. 

> This message (including any attachments) is for the named addressee(s)'s
> use only. It may contain sensitive, confidential, private proprietary or
> legally privileged information intended for a specific individual and
> purpose, and is protected by law. If you are not the intended recipient,
> please immediately delete it and all copies of it from your system, destroy
> any hard copies of it and notify the sender. Any use, disclosure, copying,
> or distribution of this message and/or any attachments is strictly
> prohibited.
Could you describe this a little bit more in detail ? Should i read this mail 
or not ? Do you need an answer to your question or not ? And please describe 
which different laws are you meaning ? 


Kind regards, 

Thomas 

[1]: Btw, does anybody know a translation of the GPL to the common asian 
languages ? Or is this not possible due missing vocabulary ? 

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

Re: [linux-dvb] dvb noaudio

[Raena Lea-Shannon]

On Mon, 2006-10-02 at 17:51 +0200, Christophe Thommeret wrote:
> Le Lundi 02 Octobre 2006 15:21, Raena Lea-Shannon a écrit :
> > Hi,
> >
> > I have just installed Kaffeine 0.7.1 (running on Ubuntu 6.06.1 AMD64
> > Asus M. Board Nvidia audio chip and Px7600 video with nvidia latest
> > drivers for Geforce 7600 Chip.
> >
> > Kaffeine is nice. Looks great easy to use. Big thanks up front to the
> > developers.
> >
> > I have installed latest v4l source and compiled and I did find that in
> > make I had to use Ncurses menuconfig and not compile with one of the
> > audio modules, I think it was *.oci ?
> >
> > I can play ABC HDTV (I am in Sydney) with sound but that is the only
> > channel that gives audio.
> >
> > I have set xine engine to alsa drivers and I have tried every setting in
> > alsamixer. I have tried ne tip which was to de-select the dvd.language.
> > That did not work for me.
> >
> > I have looked at audio pid in the channels edit and tried selecting ac3
> > but that does not work either. I also looked at the channels.conf pid
> > from scan reading and that did not work either.
> >
> > I looked at the mail list archive and apart from the above suggestions I
> > have not been able to find an answer.
> 
> Try to play mp3, ogg, and wav with Kaffeine and report which one(s) work.

mp3 will not play
wav and ogg play
> 


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

RE: [linux-dvb] TS Stream - null packets generation?

[Chun Chung Lo]

Hi,

Thanks! You are right.

The model of the modulator is PROMAX MO-170. It can be configured to
Master mode (with null packet stuffing) and Slave mode (without null
packet stuffing). But I am not sure how to make it to operate in Slave
mode.

I also found the player is operating follows the PCR. I see there is a
CBR can be set, but when I set, the modulator reports it cannot lock the
signal (or frequency?).

Please help. Thanks.

Best regards,
Lo Chun Chung

-Original Message-
From: Andrea Venturi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 03 October, 2006 5:29 PM
To: Chun Chung Lo; linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TS Stream - null packets generation?


Chun Chung Lo wrote:
> Hi all,
>
> I am now using a STB (under development) which its hardware
> configuration is:
>
> SAA7134 + TDA10046A + TD1316
>
> When I capture the TS stream (which is stream out by a DVB-T
> modulator), and compare the file with the original one, I found tones
> of NULL packets (which its header is 0x47 0x1F, 0xFF 0x10, and remains

> are 0x00 ... Until the end of a TS packets, 188bytes).
>
> The captured TS is corrupted in a random level, sometimes seriously,
> sometimes a bit.
>
> I found these null packets wasted lots of PCI bandwidth and, may these

> cause the above error?
>
> And where are the TS null packets come from?

hi,

usually, the DVB-T modulator fills the outgoing modulated TS with null
PIDs when the bitrate of the incoming TS is lower then the expected
outgoing bitrate.

 +--+   ++
 |  |ASI|| UHF
 | TS player|---| DVB-T modulator|-
 |  | IN|| OUT
 +--+   ++

with expected i mean the useful bitrate that comes from the other
parameters you put in the DVB-T modulator:

- channel BW (7/8 MHz)
- FEC
- guard interval
- modulation (QPSK/QAM16/QAM64)

there are preformatted tables about it on the net.

then you should look at the TS player, you are using; it's feeding the
modulator at a constant bit rate (CBR) or it follows the PCR?

but you need to detail more thoroughly your setup if you want us to
better understand what's going  on.

anyway, i really don't know how it can be corrupted

bye



andrea venturi

This message (including any attachments) is for the named addressee(s)'s use 
only. It may contain
sensitive, confidential, private proprietary or legally privileged information 
intended for a
specific individual and purpose, and is protected by law. If you are not the 
intended recipient,
please immediately delete it and all copies of it from your system, destroy any 
hard copies of it
and notify the sender. Any use, disclosure, copying, or distribution of this 
message and/or any
attachments is strictly prohibited.



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

Re: [linux-dvb] Hama dvb-t usb stick

[Christoph Höger]

Hello,

I built (after changing xmit_lock to _xmit_lock) and again the device
was not recognized. I really think its because the wrong vendor id.
If i wont be able to fix this, i'm going to return it to the shop in the
next to weeks. 

Am Freitag, den 29.09.2006, 20:42 +0100 schrieb Mike Choy:
> Christoph Höger wrote:
> > Hi,
> >
> > yesterday I bought a Hama dvb-t stick and, full of hope, plugged it in.
> > Ok, nothing worked, wo I installed the video4linux kernel-module package
> > (I am using FC5) and a bunch of firmware. Nothing happened then too. All
> > I saw was this:
> > usb 1-1: USB disconnect, address 4
> > usb 1-1: new high speed USB device using ehci_hcd and address 5
> > usb 1-1: configuration #1 chosen from 1 choice
> >
> > So I took a deeper look with lsusb, which told me that the vender/device
> > ID of my brandnew stick is: 
> > Bus 001 Device 005: ID 1584:6003
> >
> > When I searched for this ID I found, it is a NIC??
> > Can anybody help me out?
> >   
> > 
> >
> > ___
> > linux-dvb mailing list
> > linux-dvb@linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> Have you built from mercurial?
> 
> http://www.linuxtv.org/v4lwiki/index.php/How_to_build_from_mercurial
> 
> Mike C
> http://www.acaciaclose.co.uk
> the home of suse multimedia
> 
> 


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TS Stream - null packets generation?

[Andrea Venturi]

Chun Chung Lo wrote:
> Hi all,
> 
> I am now using a STB (under development) which its hardware
> configuration is:
> 
> SAA7134 + TDA10046A + TD1316
> 
> When I capture the TS stream (which is stream out by a DVB-T modulator),
> and compare the file with the original one, I found tones of NULL
> packets (which its header is 0x47 0x1F, 0xFF 0x10, and remains are 0x00
> ... Until the end of a TS packets, 188bytes).
> 
> The captured TS is corrupted in a random level, sometimes seriously,
> sometimes a bit.
> 
> I found these null packets wasted lots of PCI bandwidth and, may these
> cause the above error?
> 
> And where are the TS null packets come from?

hi,

usually, the DVB-T modulator fills the outgoing modulated TS with null
PIDs when the bitrate of the incoming TS is lower then the expected
outgoing bitrate.

 +--+   ++
 |  |ASI|| UHF
 | TS player|---| DVB-T modulator|-
 |  | IN|| OUT
 +--+   ++

with expected i mean the useful bitrate that comes from the other
parameters you put in the DVB-T modulator:

- channel BW (7/8 MHz)
- FEC
- guard interval
- modulation (QPSK/QAM16/QAM64)

there are preformatted tables about it on the net.

then you should look at the TS player, you are using; it's feeding the
modulator at a constant bit rate (CBR) or it follows the PCR?

but you need to detail more thoroughly your setup if you want us to
better understand what's going  on.

anyway, i really don't know how it can be corrupted

bye



andrea venturi

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

[linux-dvb] TS Stream - null packets generation?

[Chun Chung Lo]

Hi all,

I am now using a STB (under development) which its hardware
configuration is:

SAA7134 + TDA10046A + TD1316

When I capture the TS stream (which is stream out by a DVB-T modulator),
and compare the file with the original one, I found tones of NULL
packets (which its header is 0x47 0x1F, 0xFF 0x10, and remains are 0x00
... Until the end of a TS packets, 188bytes).

The captured TS is corrupted in a random level, sometimes seriously,
sometimes a bit.

I found these null packets wasted lots of PCI bandwidth and, may these
cause the above error?

And where are the TS null packets come from?

Please help. Thanks.

Best regards,
Lo Chun Chung

This message (including any attachments) is for the named addressee(s)'s use 
only. It may contain
sensitive, confidential, private proprietary or legally privileged information 
intended for a
specific individual and purpose, and is protected by law. If you are not the 
intended recipient,
please immediately delete it and all copies of it from your system, destroy any 
hard copies of it
and notify the sender. Any use, disclosure, copying, or distribution of this 
message and/or any
attachments is strictly prohibited.



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

Re: [linux-dvb] [patch 0/8] budget_ci: improve IR input handling

[David Härdeman]

On Tue, October 3, 2006 2:33, C.Y.M said:
> David Härdeman wrote:
>> This series of patches includes a number of bugfixes and changes to the
>> IR input handling of the budget-ci driver.
>
> If these patches are successful, can they also be implemented into the
> regular nexus-s ir drivers too?

Which driver is that? av7110?

> I have the same lirc issues with my full featured
> nexus card as others do with hauppauge budget cards.

I'm sorry, but I don't quite follow...the ir driver for the av7110 uses
the Linux input system (i.e. appears as a keyboard more or less), why use
LIRC? Exactly what issues do you have?

-- 
David Härdeman


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

[linux-dvb] Re: Supported radio card universal or PCI-X interface

[Robin Hill]

On Mon Oct 02, 2006 at 07:00:00PM +0200, Emilio Castellano wrote:

> 
> Robin Hill wrote:
> >On Mon Oct 02, 2006 at 12:20:34PM +0200, Emilio Castellano wrote:
> >
> >>Hiya,
> >>
> >>I've just try two cards with radio support. Hauppage WinTV primioFM and 
> >>Terratec 600, but none of this have universal or PCI-X interface,
> >>
> >>Does anybody know a board with this specs. covered?
> >>
> >Aren't they using standard PCI interfaces?  In which case they should be
> >forward compatible with PCI-X (unless they're 5V cards I guess).  I very
> >much doubt you'll get a PCI-X interface radio card - the only reason for
> >choosing PCI-X over PCI is the improved bandwidth.
> >
> >Or did you mean PCI-e rather than PCI-X?  And what do you mean by
> >universal?  I can't imagine any internal interface that could be
> >described as "universal".
> One of the projects I'm working on use HP servers with a backplane
> composed only with PCI-X slots, but many of the boards with radio
> support working on linux right now use old 5V connection.. (just one
> division at the external side of the botton).
> David was right, as universal I refer to those cards supporting multiple
> voltages (5V and 3.3V). These ones could be plugged in a PCI-X slot and
> they work the same way a normal PCI does.
> 
Ah, OK - got ya now.

> That's the reason I'd like to find out if there's a universal radio card
>  (only radio or multifunction) that works ok.
> 
Is USB an option for you?  I'd guess you'd have more luck with finding
something with USB than 3.3V PCI.

Cheers,
Robin
-- 
 ___
( ' } |   Robin Hill <[EMAIL PROTECTED]>  |
   / / )  | Little Jim says |
  // !!   |  "He fallen in de water !!" |


pgp88Sg6c6K7K.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb