[linux-dvb] [Fwd: Mantis gpio_set_bits() fix]
---BeginMessage---
Hi Manu,
Here is a bugfix for gpio_set_bits().
What do you think about this bugfix?
The bug is that the function is only able to turn the given
bit on, but it can never turn a bit off.
My patch fixes that issue.
With my patched version gpio_set_bits is able to turn a single bit
on or off.
I haven't verified that it actually does turn the device's power off
when requested.
I tested only rmmod and insmod. It seems to work with this version:
I haven't seen a lost frontend.
Regards,
Marko Ristola
Index: linux/drivers/media/dvb/mantis/mantis_core.c
===
RCS file: /var/cvs/mantis/linux/drivers/media/dvb/mantis/mantis_core.c,v
retrieving revision 1.2.2.2
retrieving revision 1.2.2.2.2.1
diff -u -p -r1.2.2.2 -r1.2.2.2.2.1
--- linux/drivers/media/dvb/mantis/mantis_core.c 15 Feb 2007 17:25:59 - 1.2.2.2
+++ linux/drivers/media/dvb/mantis/mantis_core.c 24 Feb 2007 17:54:25 - 1.2.2.2.2.1
@@ -194,22 +194,22 @@ int mantis_core_exit(struct mantis_pci *
return 0;
}
+// Turn the given bit on or off.
void gpio_set_bits(struct mantis_pci *mantis, u32 bitpos, u8 value)
{
- u32 reg;
+ u32 currVal;
+ u32 newVal;
- if (value)
- reg = 0x;
+ currVal = mmread(MANTIS_GPIF_ADDR);
+
+ if ( value )
+ newVal = currVal | ( 1 bitpos );
else
- reg = 0x;
-
- reg = (value bitpos);
+ newVal = currVal ( ~ ( 1 bitpos ) );
- mmwrite(mmread(MANTIS_GPIF_ADDR) | reg, MANTIS_GPIF_ADDR);
+ mmwrite( newVal, MANTIS_GPIF_ADDR);
mmwrite(0x00, MANTIS_GPIF_DOUT);
udelay(100);
- mmwrite(mmread(MANTIS_GPIF_ADDR) | reg, MANTIS_GPIF_ADDR);
- mmwrite(0x00, MANTIS_GPIF_DOUT);
}
---End Message---
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] pinnacle 310i fail on some channels
hi hartmut, Hi, Kevin KevinLuX schrieb: Hi, Kevin Hi Harmut Few weeks ago, i modified the driver to support the LNA on this card. So can you please try the recent version of the driver? You might set the option debug=1 for the modules tuner and tda827x. Another possible cause is that many drivers ignore the channel parameters while the tda10046 doesn't. You can set all to auto except bandwidth. Best regards Hartmut i've installed new driver from mercurial this morning. Then loaded modules tuner and tda827x with debug=1. On modules loading this is kernel output tuner 2-004b: chip at addr 4b is a tda8290 tuner 2-004b: Setting mode_mask to 0x0e tuner 2-004b: chip found @ 0x96 (saa7133[0]) tuner 2-004b: Calling set_type_addr for type=54, addr=0xff, mode=0x04, config=0x01 tuner 2-004b: set addr for type -1 tuner 2-004b: defining GPIO callback tuner 2-004b: tuner 0x4b: called during i2c_client register by adapter's attach_inform tuner 2-004b: defining GPIO callback tuner 2-004b: setting tuner address to 61 tuner 2-004b: type set to tda8290+75a tuner 2-004b: saa7133[0] tuner I2C addr 0x96 with type 54 used for 0x0e tda827x: tda827x_attach: tda827x: tda827xa tuner found DVB: registering new adapter (saa7133[0]). DVB: registering frontend 0 (Philips TDA10046H DVB-T)... Later as you said i've try to scan on differnt settings particulary T 48200 8MHz AUTO AUTO AUTO AUTO AUTO NONE T 50600 8MHz AUTO AUTO AUTO AUTO AUTO NONE During scan kernel output is : tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 20 -- ok tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 .. and this last message is continuely repeated during scan Result is : Filter timoet for frequency 506 and channels from 482 ( and other frequencies) With w_scan, i'm also able to see many others channels unfortunately xine give me a message : input_dvb: ERROR: Trying to get lock... kaffeine with its scan, show me only few channels (20 on 70), probably because it find during scan more noise than good quality signal on some channel and unfortunately i can't use channels.conf from scan because it's not compatible with kaff. Thanks Best Regards You log shows me 2 things: - you seem to have a very low antenna energy (or there is something wrong with my LNA handler. I don't have such a card, so i can't test) - You should download the firmware from Lifeview. It is more recent (2.9) and locks better on bad signals. In my personal repository http://linuxtv.org/hg/~hhackmann/v4l-dvb there is a bug fix which might affect your card as well. I originally considered it minor but this seems not to be the case. Can you please check this before we continue? Hartmut I have replaced my firmware with new firmware from lifeview and then i have pull down your personal repository, compiled and installed it. Result is the same, xine and mplayer are both blocked (tryng to get lock ) i can view channel only in kaffeine. Scan give much more result from kaffeine scan but i can't test it because as i said mplayer and xine doesn't works. Scan results and log from kernel is the same from previous maybe a little number channel ( those that have bad signal) from scan result now are not present. tuner 2-004b: set addr for type -1 tuner 2-004b: defining GPIO callback tuner 2-004b: tuner 0x4b: called during i2c_client register by adapter's attach_inform tuner 2-004b: defining GPIO callback tuner 2-004b: setting tuner address to 61 tuner 2-004b: type set to tda8290+75a tuner 2-004b: saa7133[0] tuner I2C addr 0x96 with type 54 used for 0x0e tda827x: tda827x_attach: tda827x: tda827xa tuner found DVB: registering new adapter (saa7133[0]). DVB: registering frontend 0 (Philips TDA10046H DVB-T)... tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 20 -- ok tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 -- this message all time scanning no new channel and timeout pid from some frequence 506. Now I use a new (3 month) central antenna from the top of building. Today i will test another antenna (a little mobile) to discovery if something change. Because u have not this cards, if u wanna test something (new code etc) also in the future, mail me, there's no problem. I can test for u send the output Best Regards kev ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Improve support of CX88_BOARD_WINFAST_DTV2000H
Le mardi 13 mars 2007 07:45, vous avez écrit : For what it's worth, I've compiled and am running this patch with no problems. Haven't tested the extra functionality yet, though. I just tried it with updated source, and though it builds I cannot access inputs other than tv tuner - which only displays parasites. -- Vincent Pelletier pgpGoYHplckVy.pgp Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HVR-4000: questions and status of driver?
Hi! I'm going to buy a DVB-S2 card and I've been looking at the Hauppauge HVR-4000 (or should I go for another card, like the S2-3200?), but I have som questions I can't find the answer of, maybe someone here that's using a HVR-4000 can answer it? What is the status of the driver, I saw that a S2-firmware were posted by [EMAIL PROTECTED] quite recently and http://linuxtv.org/hg/~stoth/hvr4000 +seems to have been updated quite recently. Is it possible to use the DVB-T and the DVB-S(2) tuner at the same time? Does they appear as two diffeent frontends in Linux? Thanks for any answer, Lars Fredriksson ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] STB0899, STB6200 and TT 3200-S2
I have a Technotrend TT-budget S2-3200. Can I help to develop/test drivers? Best regards. Max. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] WinTV HVR-1300 MCE edition not working
It looks like the I2C gate on the demod is closed, and the tuning code is unable to reprogram the tuner. I don't know why off hand, I've never used radio personally. It also looks like the demod is also not responding to i2c read requests. After this error occurs, does DVB-T and/or analog tv work correctly? Ie. Does the problem clear itself. No, I first checked that I was able to see DVB-T, and that worked without problems. Then I've started gnomeradio, and the errors were back into the dmesg. I've tried to restart the TV, but this gives now also : [ 7744.066068] cx22702_readreg: readreg error (ret == -121) [ 7744.066416] cx22702_writereg: writereg error (reg == 0x0b, val == 0x00, ret == -121) [ 7744.066765] cx22702_readreg: readreg error (ret == -121) [ 7744.067116] cx22702_writereg: writereg error (reg == 0x0c, val == 0x40, ret == -121) However, I see only error messages for cx22702. Next I tried to unload the cx22702 module and to reload it. To remove it I also had to remove cx88_dvb. The modprobe failed however: [ 7957.052276] cx8802_unregister_driver() -unregistering driver type=dvb [ 7957.052283] CORE cx88[0]: subsystem: 0070:9600, board: Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encoder [card=56] Unload Tried to launch gnome-radio: [ 8008.391208] tda9887 2-0043: i2c i/o error: rc == -121 (should be 4) [ 8008.391647] tuner 2-0061: i2c i/o error: rc == -121 (should be 4) [ 8008.395280] tda9887 2-0043: i2c i/o error: rc == -121 (should be 4) [ 8008.395700] tda9887 2-0043: i2c i/o error: rc == -121 (should be 4) [ 8008.396122] tuner 2-0061: i2c i/o error: rc == -121 (should be 4) [ 8008.399158] tda9887 2-0043: i2c i/o error: rc == -121 (should be 4) [ 8008.399585] tda9887 2-0043: i2c i/o error: rc == -121 (should be 4) [ 8008.45] tuner 2-0061: i2c i/o error: rc == -121 (should be 4) [ 8011.129912] tda9887 2-0043: i2c i/o error: rc == -121 (should be 4) modprobe cx88_dvb: [ 8038.842489] cx2388x dvb driver version 0.0.6 loaded [ 8038.842496] cx8802_register_driver() -registering driver type=dvb access=shared [ 8038.842501] CORE cx88[0]: subsystem: 0070:9600, board: Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encoder [card=56] [ 8038.842783] cx88[0]/2: cx2388x based dvb card [ 8038.855169] cx22702_readreg: readreg error (ret == -121) [ 8038.855196] cx88[0]: frontend initialization failed [ 8038.855199] cx8802_dvb_probe dvb_register failed err = -1 [ 8038.855201] cx8802_register_driver() -probe failed err = -1 modprobe failed with: FATAL: Error inserting cx88_dvb (/lib/modules/2.6.20-11-generic/kernel/drivers/media/video/cx88/cx88-dvb.ko): No such device Could be a GPIO issue which I could look into. Let me know the the answer to the above question. I'm running AMD64 on Ubuntu (both edgy and Feist) and have Gentoo available if needed. Let me know what info you need ... Manfred -- --- Manfred Haelters ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-4000: questions and status of driver?
What is the status of the driver, I saw that a S2-firmware were posted by [EMAIL PROTECTED] quite recently and http://linuxtv.org/hg/~stoth/hvr4000 +seems to have been updated quite recently. It's currently being developed, the hvr4000 tree is the best place to find any recent patches. Is it possible to use the DVB-T and the DVB-S(2) tuner at the same time? Does they appear as two diffeent frontends in Linux? Not currently. The kernel does not currently support this type of dynamic switching, for the HVR4000 or any similar product. However, the HVR3000 tree http://linuxtv.org/hg/~stoth/hvr3000 contains some prototype patches for an RFC I am about to release, suggest some kernel improvements to allow DVB-T and DVB-S to be used dynamically, with the hardware resources shared correctly. If the RFC is goes through the review/revise cycle quickly then those patches should appear in the dvb tree soon, meaning that DVB-S, DVB-T can be used on both the HVR4000, HVR3000 and some Medion based Philips products. They are also dependant on Manu's multiproto patches, which are not currently accepted for mainline merge. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] WinTV HVR-1300 MCE edition not working
modprobe failed with: FATAL: Error inserting cx88_dvb (/lib/modules/2.6.20-11-generic/kernel/drivers/media/video/cx88/cx88-dvb.ko): No such device Could be a GPIO issue which I could look into. Let me know the the answer to the above question. I'm running AMD64 on Ubuntu (both edgy and Feist) and have Gentoo available if needed. Let me know what info you need ... Switching between DVB-T and analog TV should work fine though, right? Does attempting to use radio break analog and/or digital tv? Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] WinTV HVR-1300 MCE edition not working
Switching between DVB-T and analog TV should work fine though, right? Yes, no problem, as long as I don't enable radio Does attempting to use radio break analog and/or digital tv? Once I use radio, I'm unable to use Digital TV. Analog still passes ... Manfred -- --- Manfred Haelters ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
Darron Broad wrote:
In message [EMAIL PROTECTED], Steven Toth wrote:
hi
Darron Broad wrote:
In message [EMAIL PROTECTED], Steven Toth wrote:
Hi Steve.
Darron Broad wrote:
...
Has anyone had a chance to try the stoth/hvr4000 tree after the recent
fixes? It's certainly going through the correct motioned for tuning now.
(I don't have a feed available for testing right now).
I just pulled and installed the repo and DVB-S works fine in kaffeine.
The combined bug fixes are a success.
I don't know how to test DVB-S2, but I will hunt around for a clue.
I hand modified dvbtune with some extra args to send via the new API (as
well as the old). I can make that available if you need it, that what I
used for testing in Europe on Astra 19.2. I patches version 0.05, now
that I look at the sourceforge.net site, it hasn't changed from 0.5 for
3 years. :(
This won't help you unless you're running with the multiproto API.
I just assumed other dvb tools (by now) would be updated and I'd drop my
patches.
Please make this available and I will see if I am able to receive the
HD tests on W3A 7'E. At this time I don't know if my signal is
adequate to pick them up though.
Remember, DiSEqC is not implemented.
Understood. I've resorted to using a nokia 9600s on a priority
switch to send diseqc down the wire :-) If you have any idea how
Diseqc is done on the hvr4000 please say, it would appreciated
and I am willing to investigate and implement if possible.
I have to look back through my notes but this is pretty trivial, let me
look into this. From memory, we receive a buffer of bytes, we reformat
the buffer into a cx24116 firmware command and execute it.
Ok. My box describes itself as disecq1.0+burst, therefore I assume
I can test either mode, but is this something you have taken note of?
In summary then: existing DVBS tuning is working fine (without DiSEqC)
using the current hvr4000 tree. That's good news.
Yes, it is working very well. Well done, and thanks.
BTW, this is with 2.6.20.2-rc1 and I will test the repo on another machine
running a similar kernel which has various DVB interfaces next week.
Bye
darron
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi all,
HVR4000 is now running on my 2.6.20(64bit) box, great. There is one
problem however: if I scan with kaffeine I only get about 12
stations. Switching between ASTRA and Eutelsat (Diseq) doesn't
seem to work. Can anyone help please?
In addition used diseqc tester and saw a diseq_msg call inside the log
but this is a standalone tool and may act different from the kaffeine
scanner.
regards Uwe
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Improvemts to dvbstream in cvs
I've just finished to add to dvbstream in cvs a basic PAT and PMT parser that automatically adds to every map all the PAT and PMT pids corresponding to the program(s) enclosing the chosen pids. Multi-sections tables are not supported. The change is completely transparent to users, so no special command line switch is required; just remember that for the time being only maps are handled (thus -o:file and -net ip:port syntaxes, not -o and -i). If you find regressions let me know asap, please. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Uwe Schmeling wrote:
lo
Hi all,
HVR4000 is now running on my 2.6.20(64bit) box, great. There is one
problem however: if I scan with kaffeine I only get about 12
stations. Switching between ASTRA and Eutelsat (Diseq) doesn't
seem to work. Can anyone help please?
In addition used diseqc tester and saw a diseq_msg call inside the log
but this is a standalone tool and may act different from the kaffeine
scanner.
regards Uwe
diseqc is not implemented in the driver so whatever tools you use
there will be no effect.
in my case, i used an external device to send the diseqc command/burst.
you can try that, else wait.
cya
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Steven Toth wrote:
Darron Broad wrote:
Has anyone had a chance to try the stoth/hvr4000 tree after the recent
fixes? It's certainly going through the correct motioned for tuning now.
(I don't have a feed available for testing right now).
Remember, DiSEqC is not implemented.
Hi Steve.
I have more news to report.
I have hacked some extra args to the kromtek multiproto szap and am able
to tune to a DVB-S2 channel.
However, I can't actually tune to a channel I am able to view, just
get a lock on, so someone else must confirm that it actually streams
correctly.
An updated szap is here:
http://dev.kewl.org/tmp/hvr4000/szap2.tgz
An example use:
# szap2 -x -a 0 -r -c ./Astra-28.2E.conf -t 2 -e 3 -m q Sky HD Promo
reading channels from file './Astra-28.2E.conf'
zapping to 1 'Sky HD Promo':
sat 0, frequency = 12324 MHz V, symbolrate 2825, vpid = 0x0200, apid =
0x0280 sid = 0x0ed9 (fec = 64, mod = 2)
Querying info .. Delivery system=DVB-S2
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_DISEQC_SEND_MASTER_CMD failed: Operation not supported
FE_DISEQC_SEND_BURST failed: Operation not supported
-- Using 'Conexant CX24116 DVB-S2' DVB-S2
do_tune: API version=2, delivery system = 2
do_tune: Frequency = 1724000, Srate = 2825 (DVB-S2)
do_tune: Frequency = 1724000, Srate = 2825 (SET_PARAMS)
status 1f | signal 008c | snr | ber | unc | FE_HAS_LOCK
The args to make the hvr4000 work are:
-f: fec (1=1/2, 2=2/3, 3=3/4, 4=4/5, 5=5/6, 6=6/7, 8=8/9, 0=AUTO)
-m: mod (q=QPSK, 8=8PSK)
If anyone can confirm that it works on FTA DVB-S2 that would be useful.
cya
darron
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Twinhan DTV Ter 3028 frontend
Hi, I have the Twinhan DTV Ter 3028 and have downloaded the mantis.tar.bz2. I compiled and installed the drivers under 2.6.17 (Ubuntu Edgy). That much went fine. The problem is that no frontend is found in the /dev/dvb/adapter directory. Is this card supported? Does anyone know which frontend should be in use? lspci -vv gives: 02:02.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Twinhan Technology Co. Ltd Unknown device 0028 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 3 Region 0: Memory at ec00 (32-bit, prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- This is the dmesg from when DVB is loaded to the last DVB related message: [17179583.528000] Linux video capture interface: v2.00 [17179584.008000] saa7146: register extension 'budget dvb'. [17179584.008000] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 4 [17179584.008000] PCI: setting IRQ 4 as level-triggered [17179584.008000] ACPI: PCI Interrupt :02:01.0[A] - Link [LNKC] - GSI 4 (level, low) - IRQ 4 [17179584.008000] saa7146: found saa7146 @ mem f8904000 (revision 1, irq 4) (0x13c2,0x1005). [17179584.008000] saa7146 (0): dma buffer size 192512 [17179584.008000] DVB: registering new adapter (TT-Budget/WinTV-NOVA-T PCI). [17179584.044000] adapter has MAC addr = 00:d0:5c:21:2a:b6 [17179584.108000] bttv: driver version 0.9.16 loaded [17179584.108000] bttv: using 8 buffers with 2080k (520 pages) each for capture [17179584.12] DVB: registering frontend 0 (LSI L64781 DVB-T)... [17179584.12] bttv: Bt8xx card found (0). [17179584.12] ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 7 [17179584.12] PCI: setting IRQ 7 as level-triggered [17179584.12] ACPI: PCI Interrupt :02:03.0[A] - Link [LNKF] - GSI 7 (level, low) - IRQ 7 [17179584.12] bttv0: Bt878 (rev 17) at :02:03.0, irq: 7, latency: 32, mmio: 0xec001000 [17179584.12] bttv0: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID is 1822:0001 [17179584.12] bttv0: using: Twinhan DST + clones [card=113,autodetected] [17179584.12] bttv0: gpio: en=, out= in=00f3edfe [init] [17179584.12] bttv0: using tuner=4 [17179584.148000] bttv0: add subdevice dvb0 [17179584.148000] bttv: Bt8xx card found (1). [17179584.148000] ACPI: PCI Interrupt Link [LNK0] enabled at IRQ 5 [17179584.148000] PCI: setting IRQ 5 as level-triggered [17179584.148000] ACPI: PCI Interrupt :02:04.0[A] - Link [LNK0] - GSI 5 (level, low) - IRQ 5 [17179584.148000] bttv1: Bt878 (rev 17) at :02:04.0, irq: 5, latency: 32, mmio: 0xec003000 [17179584.148000] bttv1: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID is 1822:0001 [17179584.148000] bttv1: using: Twinhan DST + clones [card=113,autodetected] [17179584.148000] bttv1: gpio: en=, out= in=00f3edfe [init] [17179584.148000] bttv1: using tuner=4 [17179584.164000] bttv1: add subdevice dvb1 [17179584.164000] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 [17179584.164000] PCI: setting IRQ 10 as level-triggered [17179584.164000] ACPI: PCI Interrupt :02:00.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 [17179584.164000] 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html [17179584.164000] :02:00.0: 3Com PCI 3c905C Tornado at f8b16000. [17179584.188000] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 3 [17179584.188000] PCI: setting IRQ 3 as level-triggered [17179584.188000] ACPI: PCI Interrupt :02:02.0[A] - Link [LNKD] - GSI 3 (level, low) - IRQ 3 [17179584.188000] Mantis Rev 1, irq: 3, latency: 32 [17179584.188000] memory: 0xec00, mmio: 0xf8966000 [17179584.24] sd 0:0:0:0: Attached scsi generic sg0 type 0 [17179584.244000] sd 0:0:1:0: Attached scsi generic sg1 type 0 [17179584.256000] bt878: AUDIO driver version 0.0.0 loaded [17179584.264000] ACPI: PCI Interrupt :02:00.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 [17179584.268000] eth0: setting full-duplex. [17179584.356000] get_mac_address (1): MAC Address=[00:08:ca:00:00:00] [17179584.428000] get_subvendor_id (1): Sub Vendor ID=[0x1822] [17179584.50] get_subdevice_id (1): Sub Device ID=[0x0028] [17179584.50] mantis_alloc_buffers (1): DMA=0x37a2 cpu=0xf7a2 size=65536 [17179584.50] mantis_alloc_buffers (1): RISC=0x190a000 cpu=0xc190a000 size=1000 [17179584.50] DVB: registering new adapter (Mantis dvb adapter). [17179584.628000] NET: Registered protocol family 10 [17179584.628000] lo: Disabled Privacy Extensions [17179584.628000] IPv6 over IPv4 tunneling driver [17179585.02]
Re: [linux-dvb] [Fwd: Mantis gpio_set_bits() fix]
On 3/17/07, Marko Ristola [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Marko Ristola [EMAIL PROTECTED] To: Manu Abraham [EMAIL PROTECTED] Date: Sat, 17 Mar 2007 11:14:08 +0200 Subject: Mantis gpio_set_bits() fix Hi Manu, Here is a bugfix for gpio_set_bits(). What do you think about this bugfix? The bug is that the function is only able to turn the given bit on, but it can never turn a bit off. Ah, i saw that bug a day back, but didn't care to fix it. My patch fixes that issue. Cool, Thanks. With my patched version gpio_set_bits is able to turn a single bit on or off. I haven't verified that it actually does turn the device's power off when requested. thanks, manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DTV Ter 3028 frontend
On 3/17/07, Simeon Walker [EMAIL PROTECTED] wrote: Hi, I have the Twinhan DTV Ter 3028 and have downloaded the mantis.tar.bz2. I compiled and installed the drivers under 2.6.17 (Ubuntu Edgy). That much went fine. The problem is that no frontend is found in the /dev/dvb/adapter directory. Is this card supported? Does anyone know which frontend should be in use? It is not yet supported. The frontend on the card is the zl10353 chip from Zarlink. manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] pinnacle 310i fail on some channels
Today i will test another antenna (a little mobile) to discovery if something change. I have try another antenna like this : http://www.3dnews.ru/documents/10598/Antenna.jpg away from pc and out of window. Bad result, very few channel (10) and the message from kernel log is the same: tda827x: tda8275a AGC2 gain is: 10 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
On Saturday 17 March 2007 18:16, Darron Broad wrote: In message [EMAIL PROTECTED], Steven Toth wrote: Darron Broad wrote: Has anyone had a chance to try the stoth/hvr4000 tree after the recent fixes? It's certainly going through the correct motioned for tuning now. (I don't have a feed available for testing right now). Remember, DiSEqC is not implemented. Hi Steve. I have more news to report. I have hacked some extra args to the kromtek multiproto szap and am able to tune to a DVB-S2 channel. However, I can't actually tune to a channel I am able to view, just get a lock on, so someone else must confirm that it actually streams correctly. An updated szap is here: http://dev.kewl.org/tmp/hvr4000/szap2.tgz An example use: # szap2 -x -a 0 -r -c ./Astra-28.2E.conf -t 2 -e 3 -m q Sky HD Promo reading channels from file './Astra-28.2E.conf' zapping to 1 'Sky HD Promo': sat 0, frequency = 12324 MHz V, symbolrate 2825, vpid = 0x0200, apid = 0x0280 sid = 0x0ed9 (fec = 64, mod = 2) Querying info .. Delivery system=DVB-S2 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' FE_DISEQC_SEND_MASTER_CMD failed: Operation not supported FE_DISEQC_SEND_BURST failed: Operation not supported -- Using 'Conexant CX24116 DVB-S2' DVB-S2 do_tune: API version=2, delivery system = 2 do_tune: Frequency = 1724000, Srate = 2825 (DVB-S2) do_tune: Frequency = 1724000, Srate = 2825 (SET_PARAMS) status 1f | signal 008c | snr | ber | unc | FE_HAS_LOCK The args to make the hvr4000 work are: -f: fec (1=1/2, 2=2/3, 3=3/4, 4=4/5, 5=5/6, 6=6/7, 8=8/9, 0=AUTO) -m: mod (q=QPSK, 8=8PSK) If anyone can confirm that it works on FTA DVB-S2 that would be useful. Hi Darron I connected to the BBC HD feed: BBC HD:10847:v:0:22000:0:2320:6940 With the following results... eth5:~/szap2 # ./szap2 -x -a 1 -r -c ./Astra-28.2E.conf -t 2 -e 3 -m q BBC HD reading channels from file './Astra-28.2E.conf' zapping to 35 'BBC HD': sat 0, frequency = 10847 MHz V, symbolrate 2200, vpid = 0x1fff, apid = 0x0910 sid = 0x1b1c (fec = 64, mod = 2) Querying info .. Delivery system=DVB-S2 using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' FE_DISEQC_SEND_MASTER_CMD failed: Invalid argument FE_DISEQC_SEND_BURST failed: Operation not supported -- Using 'Conexant CX24116 DVB-S2' DVB-S2 do_tune: API version=2, delivery system = 2 do_tune: Frequency = 1097000, Srate = 2200 (DVB-S2) do_tune: Frequency = 1097000, Srate = 2200 (SET_PARAMS) status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | Stracing on mplayer shows that it open drv0, but just sits there waiting on data to be read. The HVR4000 is adaptor 1, with a DVB-T card at 0; Bob ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
On 3/17/07, Darron Broad [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Steven Toth wrote: Darron Broad wrote: Has anyone had a chance to try the stoth/hvr4000 tree after the recent fixes? It's certainly going through the correct motioned for tuning now. (I don't have a feed available for testing right now). Remember, DiSEqC is not implemented. Hi Steve. I have more news to report. I have hacked some extra args to the kromtek multiproto szap and am able to tune to a DVB-S2 channel. szap (http://kromtek.com/dvb/szap.c) should work as it is with multiproto manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] pinnacle 310i fail on some channels
Hey, Kevin KevinLuX schrieb: hi hartmut, Hi, Kevin KevinLuX schrieb: Hi, Kevin Hi Harmut Few weeks ago, i modified the driver to support the LNA on this card. So can you please try the recent version of the driver? You might set the option debug=1 for the modules tuner and tda827x. Another possible cause is that many drivers ignore the channel parameters while the tda10046 doesn't. You can set all to auto except bandwidth. Best regards Hartmut i've installed new driver from mercurial this morning. Then loaded modules tuner and tda827x with debug=1. On modules loading this is kernel output tuner 2-004b: chip at addr 4b is a tda8290 tuner 2-004b: Setting mode_mask to 0x0e tuner 2-004b: chip found @ 0x96 (saa7133[0]) tuner 2-004b: Calling set_type_addr for type=54, addr=0xff, mode=0x04, config=0x01 tuner 2-004b: set addr for type -1 tuner 2-004b: defining GPIO callback tuner 2-004b: tuner 0x4b: called during i2c_client register by adapter's attach_inform tuner 2-004b: defining GPIO callback tuner 2-004b: setting tuner address to 61 tuner 2-004b: type set to tda8290+75a tuner 2-004b: saa7133[0] tuner I2C addr 0x96 with type 54 used for 0x0e tda827x: tda827x_attach: tda827x: tda827xa tuner found DVB: registering new adapter (saa7133[0]). DVB: registering frontend 0 (Philips TDA10046H DVB-T)... Later as you said i've try to scan on differnt settings particulary T 48200 8MHz AUTO AUTO AUTO AUTO AUTO NONE T 50600 8MHz AUTO AUTO AUTO AUTO AUTO NONE During scan kernel output is : tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 20 -- ok tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 .. and this last message is continuely repeated during scan Result is : Filter timoet for frequency 506 and channels from 482 ( and other frequencies) With w_scan, i'm also able to see many others channels unfortunately xine give me a message : input_dvb: ERROR: Trying to get lock... kaffeine with its scan, show me only few channels (20 on 70), probably because it find during scan more noise than good quality signal on some channel and unfortunately i can't use channels.conf from scan because it's not compatible with kaff. Thanks Best Regards You log shows me 2 things: - you seem to have a very low antenna energy (or there is something wrong with my LNA handler. I don't have such a card, so i can't test) - You should download the firmware from Lifeview. It is more recent (2.9) and locks better on bad signals. In my personal repository http://linuxtv.org/hg/~hhackmann/v4l-dvb there is a bug fix which might affect your card as well. I originally considered it minor but this seems not to be the case. Can you please check this before we continue? Hartmut I have replaced my firmware with new firmware from lifeview and then i have pull down your personal repository, compiled and installed it. Result is the same, xine and mplayer are both blocked (tryng to get lock ) i can view channel only in kaffeine. Scan give much more result from kaffeine scan but i can't test it because as i said mplayer and xine doesn't works. Scan results and log from kernel is the same from previous maybe a little number channel ( those that have bad signal) from scan result now are not present. If kaffeine works but xine and scan not, the reason lies in your initial tuning file. If channel parameters - i.e. the guard interval - are wrong, the tda10046 won't lock. This can easily be the case since some other drivers just ignore these values. tuner 2-004b: set addr for type -1 tuner 2-004b: defining GPIO callback tuner 2-004b: tuner 0x4b: called during i2c_client register by adapter's attach_inform tuner 2-004b: defining GPIO callback tuner 2-004b: setting tuner address to 61 tuner 2-004b: type set to tda8290+75a tuner 2-004b: saa7133[0] tuner I2C addr 0x96 with type 54 used for 0x0e tda827x: tda827x_attach: tda827x: tda827xa tuner found DVB: registering new adapter (saa7133[0]). DVB: registering frontend 0 (Philips TDA10046H DVB-T)... tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 20 -- ok This is still the old firmware. Sorry, i didn't mention this: Depending on the card wiring, you either need to reload the saa7134 and saa7134-dvb module or even do a power cycle to get the new firmware loaded. tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 tda827x: tda8275a AGC2 gain is: 10 -- this message all time scanning Thats ok. If debugging is on, this message occurs at every tuning attempt. BTW: this is maximum gain, is your antenna energy low? no new channel and timeout pid from some frequence 506. Now I use a new (3 month) central antenna from the top of building. Today i will test another antenna (a little mobile) to discovery if something
Re: [linux-dvb] Anubis Electronics Lifeview(0x10fd:0x1513)
Hi, Pierre Hartmut Hackmann schrieb: Hi, Pierre Pierre Willenbrock schrieb: Hi Hartmut, Hartmut Hackmann schrieb: Hi, Pierre Pierre Willenbrock schrieb: Hartmut Hackmann schrieb: Hi, Aapo Tahkola schrieb: On Sat, 3 Mar 2007 03:10:41 +0200 Aapo Tahkola [EMAIL PROTECTED] wrote: On Fri, 02 Mar 2007 23:06:15 +0100 Pierre Willenbrock [EMAIL PROTECTED] wrote: Michael Krufky schrieb: Pierre Willenbrock wrote: Hi list, I am owner of a MSI DIGIVOX mini-II. I got it to work using the attached patch and firmware. The patch and firmware are the result of analyzing some usb logs from windows. The patch breaks all users of tda10046, as i don't understand how that chip is supposed to work. The same goes for my driver implementation of the Philips 8275a. So this mess needs to be fixed before it can go into the repository. The patch is against a fresh hg checkout from http://linuxtv.org/hg/v4l-dvb at 2007-02-22 21:00 UTC. Regards, Pierre Pierre- I am very happy to hear that you got this device working... Interestingly enough, we have already created a new tda827x dvb fe module, which might be better for your device... This new tda827x module has not yet been merged into the master v4l-dvb repository, but it will be soon. Could you try to use the code located in: http://linuxtv.org/hg/~hhackmann/v4l-dvb The tda827x module will be able to detect the difference between the tda8275 and the tda8275a ... You do not have to fill the callback functions in the config struct -- that is really meant as a hack for some required GPIO handling in the saa7134-dvb driver for input switching. If you can generate a new patch against the repository above, it would make it _much_ easier to integrate your patch into the sources. After you get that done, we can work out the tda1004x differences. You might also want to speak to aett and friedrich, regulars of the #linuxtv irc chat room on irc.freenode.net ... aet is the author of the m920x driver, and friedrich has the same device that you have. They have been working on it, but haven't yet gotten successful results. Good work! Hopefully we can clean this up after you generate a new patch using the tda827x module from hhackmann's repository. Regards, Mike Krufky Hi Mike and Hartmut, this time, the patch does not change tda827x.c at all. I fiddled with the PHY2 value in tda1004x.c and found it to be related to the IF(there seems to be some factor between the IF and PHY2 introduced somewhere else). This leaves some differences in tda1004x.c. I don't know what to do with these, so i would be glad to get any hints. Updated patch. I'm fine with these m920x changes. Signed-of-by: Aapo Tahkola [EMAIL PROTECTED] PHY2 indeed defines the IF frequency relative to the sampling frequency. If you need a different value here, the reason most probably is the following: In some countries, i.e. Britain, France and Australia, the tranmitters are +/- 166kHz off the channel center frequency. This isn't documented. You can compensate this by simply tuning to the actually used channel center frequency. The windows driver used an IF of 4.75MHz for UHF, so i resorted to hardcoding it to 4.75MHz in tda827x.c, while using PHY2, WREF and the other settings from an usb log. After changing PHY2 the hack in tda827x.c is no longer needed. This leaves me with these settings for UHF(cannot test VHF -- i don't get any channels in that range): CONFPLL2=7 //52MHz sampling clock? yes FREQ_PHY2=0xc4f TIME_WREF1..5=0x5b, 0x02, 0xd0, 0x2d, 0x03 This gives a IF center frequency of 5.0MHz and a bandwidth of 8MHz. A note: Some channel decoders can compensate this offset automatically. The tda10046 needs assistance from the driver for this. This is not built in yet. Hartmut Regards, Pierre The only difference is that you use a sampling clock of 52MHz while the original driver uses 48MHz. This btw is the same as the Philips default driver for windows uses. We could have a long discussion now about ideal sampling frequencies but believe me: as long as your board does not have a weird interference problem, 48MHz is the better choice for the sampling clock and adding a additional one would only make life more difficult. I thought i checked that it does not easily work with 48MHz, but obviously i did not. The reception part works now perfectly without any modifications. Ok, fine. This leaves me with a last difference: CONF_TRISTATE1 must be -0-- -0-1 (binary, msb first, - is don't care) in tda10046_init. The only difference i see here is bit 6 which enables the serial TS output. All known applications yet use the parallel output but this can be different in your case. RFC: should we make this a configuration option? I would tend to add an entry ts_mode to tda1004x_config which defaults to parallel (0) to remain backward compatible. At least the standard modes should turn the other output off
[Fwd: Re: [linux-dvb] pinnacle 310i fail on some channels]
---BeginMessage--- Hartmut Hackmann ha scritto: If kaffeine works but xine and scan not, the reason lies in your initial tuning file. If channel parameters - i.e. the guard interval - are wrong, the tda10046 won't lock. This can easily be the case since some other drivers just ignore these values. Thanks, i replaced AUTO with correct value of QAM FEC...infact the output produced by scan channels.conf now works with xine and mplayer with almost all channel. On the other hand, scan find a large number of channel that i can't view with xine/mplayer and i think that this is due to poor signal of this channels or maybe problem is antenna. I don't know if it is a board problem. From now i view 50% (*the very most important*) of all 60 channels. This is still the old firmware. Sorry, i didn't mention this: Depending on the card wiring, you either need to reload the saa7134 and saa7134-dvb module or even do a power cycle to get the new firmware loaded. okay... sorry for my inexperience... the result now is this : tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 29 -- ok i think it shoud be correct. tda827x: tda8275a AGC2 gain is: 10 -- this message all time scanning Thats ok. If debugging is on, this message occurs at every tuning attempt. BTW: this is maximum gain, is your antenna energy low? i don't know about energy low.. i use normally an terrestrial antenna like this : http://personal.inet.fi/cool/lwgt/myoldvdr/uhf-antenna.jpg but i try to use also a mobile antenna similar to this one : http://www.3dnews.ru/documents/10598/Antenna.jpg with the mobile antenna results are very very bad... but the message about gain is the same in both case. Thanks a lot for the offer, i will come back on this. no problem u're welcome. Can you please follow the hints i gave you before we continue? I hope that's you're request are satisfied, i'm not sure that i have done the right thing that u have requested :) my english is not perfect and many times i don't understand perfectly what people want or say. .) Best regards Hartmut ciaooo kev ---End Message--- ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] pinnacle 310i fail on some channels
Hartmut Hackmann ha scritto: If kaffeine works but xine and scan not, the reason lies in your initial tuning file. If channel parameters - i.e. the guard interval - are wrong, the tda10046 won't lock. This can easily be the case since some other drivers just ignore these values. Thanks, i replaced AUTO with correct value of QAM FEC...infact the output produced by scan channels.conf now works with xine and mplayer with almost all channel. On the other hand, scan find a large number of channel that i can't view with xine/mplayer and i think that this is due to poor signal of this channels or maybe problem is antenna. I don't know if it is a board problem. From now i view 50% (*the very most important*) of all 60 channels. This is still the old firmware. Sorry, i didn't mention this: Depending on the card wiring, you either need to reload the saa7134 and saa7134-dvb module or even do a power cycle to get the new firmware loaded. okay... sorry for my inexperience... the result now is this : tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 29 -- ok i think it shoud be correct. tda827x: tda8275a AGC2 gain is: 10 -- this message all time scanning Thats ok. If debugging is on, this message occurs at every tuning attempt. BTW: this is maximum gain, is your antenna energy low? i don't know about energy low.. i use normally an terrestrial antenna like this : http://personal.inet.fi/cool/lwgt/myoldvdr/uhf-antenna.jpg but i try to use also a mobile antenna similar to this one : http://www.3dnews.ru/documents/10598/Antenna.jpg with the mobile antenna results are very very bad... but the message about gain is the same in both case. Thanks a lot for the offer, i will come back on this. no problem u're welcome. Can you please follow the hints i gave you before we continue? I hope that's you're request are satisfied, i'm not sure that i have done the right thing that u have requested :) my english is not perfect and many times i don't understand perfectly what people want or say. .) Best regards Hartmut ciaooo kev ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Manu Abraham wrote:
lo
On 3/17/07, Darron Broad [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Steven Toth wrote:
Darron Broad wrote:
Has anyone had a chance to try the stoth/hvr4000 tree after the recent
fixes? It's certainly going through the correct motioned for tuning now.
(I don't have a feed available for testing right now).
Remember, DiSEqC is not implemented.
Hi Steve.
I have more news to report.
I have hacked some extra args to the kromtek multiproto szap and am able
to tune to a DVB-S2 channel.
szap (http://kromtek.com/dvb/szap.c) should work as it is with multiproto
this is the base of the hack. there are three reasons it doesn't work
with the hvr4000 demod driver.
1. the modulation type needs to be explicit
2. fec_auto isn't available as stated in driver:
Not all S2 mmodulation schemes are support and not all rates with
a scheme are support. Especially, no auto detect when in S2 mode
3. the delivery field has to be set
Once the above are done it appears to works ok.
cya and thx.
darron
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Gregoire Favre wrote:
lo
On Sat, Mar 17, 2007 at 06:05:28PM +, Darron Broad wrote:
diseqc is not implemented in the driver so whatever tools you use
there will be no effect.
Well, what does `hg log|less` says for you ?
Here I got :
changeset: 5416:03afdb635ed2
tag: tip
user:Steven Toth [EMAIL PROTECTED]
date:Fri Mar 16 14:37:06 2007 -0400
summary: DiSEqC support via diseqc_send_master_cmd
But as it don't seems to works here, you shall be right anyway...
ok. i will check out this new development and see what happens.
in my case, i used an external device to send the diseqc command/burst.
you can try that, else wait.
I think you are the only one who can tune to anything with this card,
but it's a more or less as you use some other hardware to help the
tuning...
the external hardware selects either the band, polarity or feed with
the driver being able to select the band using a tone.
if you discover what a priority switch does you will find that
what it does is allow a master device to control the above with
the slave being able to tune only frequencies on the same
band and polarity as the master.
it cannot affect the integral tuner of the slave, they are independant
in that regard.
It would be interesting to see what will happen when you only plug the
card and try to tune.
if i do that it works, but can't select a feed with diseqc. it
can control a universal LNB feed alone.
From the mail of Bob I can see he also can't tune (which is the
reason he don't receive anything in mplayer).
this is not true, Bob is able to tune, and if you are not able
to tune then you have some other problem.
l8r
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Bob wrote:
Hello Bob.
Hi Darron
I connected to the BBC HD feed:
BBC HD:10847:v:0:22000:0:2320:6940
With the following results...
eth5:~/szap2 # ./szap2 -x -a 1 -r -c ./Astra-28.2E.conf -t 2 -e 3 -m q BBC HD
reading channels from file './Astra-28.2E.conf'
zapping to 35 'BBC HD':
sat 0, frequency = 10847 MHz V, symbolrate 2200, vpid = 0x1fff, apid =
0x0910 sid = 0x1b1c (fec = 64, mod = 2)
Querying info .. Delivery system=DVB-S2
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
FE_DISEQC_SEND_MASTER_CMD failed: Invalid argument
FE_DISEQC_SEND_BURST failed: Operation not supported
-- Using 'Conexant CX24116 DVB-S2' DVB-S2
do_tune: API version=2, delivery system = 2
do_tune: Frequency = 1097000, Srate = 2200 (DVB-S2)
do_tune: Frequency = 1097000, Srate = 2200 (SET_PARAMS)
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
Stracing on mplayer shows that it open drv0, but just sits there waiting
on data to be read.
The HVR4000 is adaptor 1, with a DVB-T card at 0;
The problem above is that BBC HD on Astra 28.2E is DVB-S and not DVB-S2
Refer to kingofsat.net or elsewhere:
Astra 2D (28.2E) - 10847.00 V - Txp:50 - Beam:Astra 2D DVB-S (QPSK) - 22000
5/6 - NID:2 - TID:2050
My example was tuning to Sky on same satellite, however, as it is
encrypted there is little to see.
The only FTA DVB-S2 i was able to at least look at is on W3A yet
there is no signal, therefore someone with access to 23.5? or 19.2?
DVB-S2 can test this.
Thanks for trying.
darron
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb][Patch] Anubis Electronics Lifeview(0x10fd:0x1513)
Hi Hartmut, Hartmut Hackmann schrieb: Hi, Pierre Hartmut Hackmann schrieb: Hi, Pierre Pierre Willenbrock schrieb: Hi Hartmut, Hartmut Hackmann schrieb: Hi, Pierre Pierre Willenbrock schrieb: Hartmut Hackmann schrieb: Hi, Aapo Tahkola schrieb: On Sat, 3 Mar 2007 03:10:41 +0200 Aapo Tahkola [EMAIL PROTECTED] wrote: On Fri, 02 Mar 2007 23:06:15 +0100 Pierre Willenbrock [EMAIL PROTECTED] wrote: Michael Krufky schrieb: Pierre Willenbrock wrote: Hi list, I am owner of a MSI DIGIVOX mini-II. I got it to work using the attached patch and firmware. The patch and firmware are the result of analyzing some usb logs from windows. The patch breaks all users of tda10046, as i don't understand how that chip is supposed to work. The same goes for my driver implementation of the Philips 8275a. So this mess needs to be fixed before it can go into the repository. The patch is against a fresh hg checkout from http://linuxtv.org/hg/v4l-dvb at 2007-02-22 21:00 UTC. Regards, Pierre Pierre- I am very happy to hear that you got this device working... Interestingly enough, we have already created a new tda827x dvb fe module, which might be better for your device... This new tda827x module has not yet been merged into the master v4l-dvb repository, but it will be soon. Could you try to use the code located in: http://linuxtv.org/hg/~hhackmann/v4l-dvb The tda827x module will be able to detect the difference between the tda8275 and the tda8275a ... You do not have to fill the callback functions in the config struct -- that is really meant as a hack for some required GPIO handling in the saa7134-dvb driver for input switching. If you can generate a new patch against the repository above, it would make it _much_ easier to integrate your patch into the sources. After you get that done, we can work out the tda1004x differences. You might also want to speak to aett and friedrich, regulars of the #linuxtv irc chat room on irc.freenode.net ... aet is the author of the m920x driver, and friedrich has the same device that you have. They have been working on it, but haven't yet gotten successful results. Good work! Hopefully we can clean this up after you generate a new patch using the tda827x module from hhackmann's repository. Regards, Mike Krufky Hi Mike and Hartmut, this time, the patch does not change tda827x.c at all. I fiddled with the PHY2 value in tda1004x.c and found it to be related to the IF(there seems to be some factor between the IF and PHY2 introduced somewhere else). This leaves some differences in tda1004x.c. I don't know what to do with these, so i would be glad to get any hints. Updated patch. I'm fine with these m920x changes. Signed-of-by: Aapo Tahkola [EMAIL PROTECTED] PHY2 indeed defines the IF frequency relative to the sampling frequency. If you need a different value here, the reason most probably is the following: In some countries, i.e. Britain, France and Australia, the tranmitters are +/- 166kHz off the channel center frequency. This isn't documented. You can compensate this by simply tuning to the actually used channel center frequency. The windows driver used an IF of 4.75MHz for UHF, so i resorted to hardcoding it to 4.75MHz in tda827x.c, while using PHY2, WREF and the other settings from an usb log. After changing PHY2 the hack in tda827x.c is no longer needed. This leaves me with these settings for UHF(cannot test VHF -- i don't get any channels in that range): CONFPLL2=7 //52MHz sampling clock? yes FREQ_PHY2=0xc4f TIME_WREF1..5=0x5b, 0x02, 0xd0, 0x2d, 0x03 This gives a IF center frequency of 5.0MHz and a bandwidth of 8MHz. A note: Some channel decoders can compensate this offset automatically. The tda10046 needs assistance from the driver for this. This is not built in yet. Hartmut Regards, Pierre The only difference is that you use a sampling clock of 52MHz while the original driver uses 48MHz. This btw is the same as the Philips default driver for windows uses. We could have a long discussion now about ideal sampling frequencies but believe me: as long as your board does not have a weird interference problem, 48MHz is the better choice for the sampling clock and adding a additional one would only make life more difficult. I thought i checked that it does not easily work with 48MHz, but obviously i did not. The reception part works now perfectly without any modifications. Ok, fine. This leaves me with a last difference: CONF_TRISTATE1 must be -0-- -0-1 (binary, msb first, - is don't care) in tda10046_init. The only difference i see here is bit 6 which enables the serial TS output. All known applications yet use the parallel output but this can be different in your case. RFC: should we make this a configuration option? I would tend to add an entry ts_mode to tda1004x_config which defaults to parallel (0) to remain backward compatible. At least the standard
Re: [linux-dvb] HVR4000 Support
On Saturday 17 March 2007 22:55, Darron Broad wrote: In message [EMAIL PROTECTED], Bob wrote: Hello Bob. Hi Darron I connected to the BBC HD feed: BBC HD:10847:v:0:22000:0:2320:6940 With the following results... eth5:~/szap2 # ./szap2 -x -a 1 -r -c ./Astra-28.2E.conf -t 2 -e 3 -m q BBC HD reading channels from file './Astra-28.2E.conf' zapping to 35 'BBC HD': sat 0, frequency = 10847 MHz V, symbolrate 2200, vpid = 0x1fff, apid = 0x0910 sid = 0x1b1c (fec = 64, mod = 2) Querying info .. Delivery system=DVB-S2 using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' FE_DISEQC_SEND_MASTER_CMD failed: Invalid argument FE_DISEQC_SEND_BURST failed: Operation not supported -- Using 'Conexant CX24116 DVB-S2' DVB-S2 do_tune: API version=2, delivery system = 2 do_tune: Frequency = 1097000, Srate = 2200 (DVB-S2) do_tune: Frequency = 1097000, Srate = 2200 (SET_PARAMS) status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | Stracing on mplayer shows that it open drv0, but just sits there waiting on data to be read. The HVR4000 is adaptor 1, with a DVB-T card at 0; The problem above is that BBC HD on Astra 28.2E is DVB-S and not DVB-S2 Refer to kingofsat.net or elsewhere: Astra 2D (28.2E) - 10847.00 V - Txp:50 - Beam:Astra 2D DVB-S (QPSK) - 22000 5/6 - NID:2 - TID:2050 My example was tuning to Sky on same satellite, however, as it is encrypted there is little to see. The only FTA DVB-S2 i was able to at least look at is on W3A yet there is no signal, therefore someone with access to 23.5? or 19.2? DVB-S2 can test this. Thanks for trying. I would have thought though, that if it was DVB-S, then I would be able to view it. I also thought that HD only happened over DVB-S2? So much to learn... B ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Darron Broad wrote:
Steven.
Your diseqc addition introduces a new bug.
The problem occurs because you have a lookup table with fixed
command lengths and the diseqc command is:
1. omitted from the table, so is assumed to be an invalid command.
2. has a variable length so can't be added to that table.
there are two solutions, either hack it to work OR remove the table
and put the lengths in the calling functions.
in order to test diseqc i will do (2) above and determine if
it works.
cheers
In message [EMAIL PROTECTED], Gregoire Favre wrote:
lo
On Sat, Mar 17, 2007 at 06:05:28PM +, Darron Broad wrote:
diseqc is not implemented in the driver so whatever tools you use
there will be no effect.
Well, what does `hg log|less` says for you ?
Here I got :
changeset: 5416:03afdb635ed2
tag: tip
user:Steven Toth [EMAIL PROTECTED]
date:Fri Mar 16 14:37:06 2007 -0400
summary: DiSEqC support via diseqc_send_master_cmd
But as it don't seems to works here, you shall be right anyway...
ok. i will check out this new development and see what happens.
in my case, i used an external device to send the diseqc command/burst.
you can try that, else wait.
I think you are the only one who can tune to anything with this card,
but it's a more or less as you use some other hardware to help the
tuning...
the external hardware selects either the band, polarity or feed with
the driver being able to select the band using a tone.
if you discover what a priority switch does you will find that
what it does is allow a master device to control the above with
the slave being able to tune only frequencies on the same
band and polarity as the master.
it cannot affect the integral tuner of the slave, they are independant
in that regard.
It would be interesting to see what will happen when you only plug the
card and try to tune.
if i do that it works, but can't select a feed with diseqc. it
can control a universal LNB feed alone.
From the mail of Bob I can see he also can't tune (which is the
reason he don't receive anything in mplayer).
this is not true, Bob is able to tune, and if you are not able
to tune then you have some other problem.
l8r
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Gregoire Favre wrote:
hi.
please apply the patch here:
http://dev.kewl.org/tmp/hvr4000/stoth.diff
and see if diseqc now works for you.
it doesn't work for me, but this may be due to my switch
not supporting messages even though it says it does.
turning burst off on my nokia receiver works, however, that
receiver runs the old and legendary doctor overflow firmware
and it may be lying (apologies dr. if it isn't).
please report success or failure, thanks.
darron
PS. i can't test another switch at this time.
On Sat, Mar 17, 2007 at 06:05:28PM +, Darron Broad wrote:
diseqc is not implemented in the driver so whatever tools you use
there will be no effect.
Well, what does `hg log|less` says for you ?
Here I got :
changeset: 5416:03afdb635ed2
tag: tip
user:Steven Toth [EMAIL PROTECTED]
date:Fri Mar 16 14:37:06 2007 -0400
summary: DiSEqC support via diseqc_send_master_cmd
But as it don't seems to works here, you shall be right anyway...
in my case, i used an external device to send the diseqc command/burst.
you can try that, else wait.
I think you are the only one who can tune to anything with this card,
but it's a more or less as you use some other hardware to help the
tuning...
It would be interesting to see what will happen when you only plug the
card and try to tune.
From the mail of Bob I can see he also can't tune (which is the
reason he don't receive anything in mplayer).
--=20
Gr=E9goire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg=
.org
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR4000 Support
In message [EMAIL PROTECTED], Bob wrote:
lo
On Saturday 17 March 2007 22:55, Darron Broad wrote:
In message [EMAIL PROTECTED], Bob wrote:
I would have thought though, that if it was DVB-S, then I would be
able to view it. I also thought that HD only happened over DVB-S2?
you can tune in if you use the DVB-S delivery system (-t 0) else
use the regular szap
So much to learn...
yes, and what you may find is even though you can tune in, you
may not have the required decoder to view it, else you do, but
it's only something like 1 FPS...
Good luck
--
// /
{:)==={ Darron Broad [EMAIL PROTECTED]
\\ \
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
