2008/3/12 Ben Backx [EMAIL PROTECTED]:
Hello,
I was wondering if there's some info to find on how to implement (and test)
multi-channel receiving?
It's possible, because dvb uses streams and the driver is currently capable
to filter one channel, but how can I implement the support of
-Original Message-
From: Jarryd Beck [mailto:[EMAIL PROTECTED]
Sent: 12 March 2008 11:32
To: Ben Backx
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Implementing support for multi-channel
2008/3/12 Ben Backx [EMAIL PROTECTED]:
Hello,
I was wondering if there's
Hello,
I was wondering if there's some info to find on how to implement (and test)
multi-channel receiving?
It's possible, because dvb uses streams and the driver is currently capable
to filter one channel, but how can I implement the support of multi-channel
filtering?
Is there perhaps an
Hello everyone!
I recently installed mythbunut 7.10 and tried to get the WinTV Nova-TD
stick working with the latest v4l-sources (mercurial)
Output of lsusb: ID 2040:9580 Hauppauge
Hauppauge Remote: A415-HPG-WE-A
When I start mythbuntu, I get the following error, after switching the
channels
Hello,
I was wondering if there's some info to find on how to implement (and
test)
multi-channel receiving?
It's possible, because dvb uses streams and the driver is currently
capable
to filter one channel, but how can I implement the support of
multi-channel
filtering?
Is there perhaps
On Wed, Mar 12, 2008 at 12:19 PM, Stephen Rowles [EMAIL PROTECTED] wrote:
Hello,
I was wondering if there's some info to find on how to implement (and
test)
multi-channel receiving?
It's possible, because dvb uses streams and the driver is currently
capable
to filter one
On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Also when I plugged it in, it sat there for about 10 seconds before
finishing loading (dmesg printed another 5 lines about the device
after about 10 seconds), but still no tuning.
Can I see those five
On 03/12/2008 06:36:04 AM, Ben Backx wrote:
-Original Message-
From: Jarryd Beck [mailto:[EMAIL PROTECTED]
Sent: 12 March 2008 11:32
To: Ben Backx
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Implementing support for multi-channel
2008/3/12 Ben Backx [EMAIL
hello
I looked sniffs and find correct demodulator initialization values for
this NXP tuner. Copy paste correct table from attached file and try.
Hopefully it works. I compared your sniff to mt2060 and qt1010 based
devices and there was still some minor differences to check.
regards,
Antti
Michael Krufky wrote:
On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Also when I plugged it in, it sat there for about 10 seconds
before
finishing loading (dmesg printed another 5 lines about the device
after about 10 seconds), but still no tuning.
Hi there,
I ran into problems using the MSI Digi VOX mini II (original Version, not
V2.0 or V3.0) on Kubuntu 7.10.
Here is a tail -f /var/run/kern.log while inserting the stick and opening
Kaffeine:
Mar 12 13:54:10 PBserver kernel: [ 561.467245] usb 6-5: new high speed
USB device using
When I was having the problem, I was running 2.6.22 (vanilla ubuntu),
so it doesn't appear to be related to kernel version.
The fix posted a few weeks ago does seem to have stopped it for me. I
said I lost a tuner recently, but I think that may have just been a
loss in reception.
Ben
On
-Original Message-
From: Stephen Rowles [mailto:[EMAIL PROTECTED]
Sent: 12 March 2008 13:20
To: Ben Backx
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Implementing support for multi-channel
Hello,
I was wondering if there's some info to find on how to implement (and
On 3/12/08, Ben Firshman [EMAIL PROTECTED] wrote:
When I was having the problem, I was running 2.6.22 (vanilla ubuntu),
so it doesn't appear to be related to kernel version.
The fix posted a few weeks ago does seem to have stopped it for me. I
said I lost a tuner recently, but I think that
2.6.22-14 with patches, stable for me.
/Henrik
On Tue, Mar 11, 2008 at 12:07 PM, [EMAIL PROTECTED] wrote:
Not sure if this helps or adds that much to the discussion... (I think
this was concluded before)
But I finally switched back to kernel 2.6.22.19 on March 5th (with current
v4l-dvb
2008/3/12 Henrik Beckman [EMAIL PROTECTED]:
2.6.22-14 with patches, stable for me.
/Henrik
On Tue, Mar 11, 2008 at 12:07 PM, [EMAIL PROTECTED] wrote:
Not sure if this helps or adds that much to the discussion... (I think
this was concluded before)
But I finally switched back to
On Wed, Mar 5, 2008 at 12:03 AM, Ben Firshman [EMAIL PROTECTED] wrote:
I am quite disappointed to report that one of my tuners has just died
this evening. No error messages to speak of.
Ben
On 26 Feb 2008, at 19:18, Philip Pemberton wrote:
Patrik Hansson wrote:
Just wanted to say
Jarryd,
I've analyzed the snoop that you've taken of the windows driver, and I
conclude that the driver is basically doing exactly the same that the
linux driver would do. The only thing that I cannot verify is whether
or not the tda18211 uses the same table values as the
On Wed, Mar 12, 2008 at 9:34 PM, Patrik Hansson [EMAIL PROTECTED] wrote:
On Wed, Mar 5, 2008 at 12:03 AM, Ben Firshman [EMAIL PROTECTED] wrote:
I am quite disappointed to report that one of my tuners has just died
this evening. No error messages to speak of.
Ben
On 26
It's (partly) for a research project, so I have to look at all possible
solutions, software being one, so dvbstreamer is part of the solution :-)
The others are at driver and hardware level (the hardware supports this).
I can try to explain you what I have understood.
Please anybody
Hi,
I'd like to understand the behavior and meaning of the LOCK returned by the
fronted.
If I open the fronted in readonly, and ask for the INFO, it is possible that
I get a LOCK but no
data is actually received.
This because the fronted receives data ONLY while it is opened
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Jarryd,
I've analyzed the snoop that you've taken of the windows driver, and I
conclude that the driver is basically doing exactly the same that the
linux driver would do. The only thing that I
On Sun, 09 Mar 2008 23:21:17 +0100
Jan Hoogenraad [EMAIL PROTECTED] wrote:
Mauro:
Thanks a lot for the comments.
One clear problem with this particular driver is that the code that came
from RealTek does not conform to the Linux C coding style.
Would that be an objection for the steps
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Jarryd,
I've analyzed the snoop that you've taken of the windows driver,
and I
conclude that the driver is
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Jarryd,
I've analyzed the snoop that you've taken of the windows
driver, and I
conclude that
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Jarryd,
I've analyzed
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED]
wrote:
Jarryd,
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED]
wrote:
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Then, please turn ON debug, repeat your tests, and post again with
dmesg. I am not familiar with the af9015 driver, but for tda18271, set
debug=1. (you must unload all modules first -- do 'make unload' in
Bernhard Albers wrote:
[ 628.492000] hub 4-0:1.0: port 9 disabled by hub (EMI?), re-enabling...
[ 628.492000] usb 4-9: USB disconnect, address 2
[ 628.50] MT2266 I2C write failed
[ 628.50] MT2266 I2C write failed
[ 650.208000] dvb-usb: error while stopping stream.
Maybe it is a
status 00 | signal | snr | ber | unc |
status 01 | signal | snr | ber | unc |
I'm not familiar enough with the hardware and I don't know if this will help
but this is the same thing I was seeing when I was getting the dvico dual
digital 4
Hi, i'm trying to get a AOPEN mc770a up and running.
From what i can find it should be the same as a DIBCOM 7700-PH. This should
contain dib7700 + ConexantCX25842 + Xceive XC3028 according to their own
docs.
After following this thread with some minor alterations to match my card's
usbid
Hi all,
A while back I reported I was having problems with compiling drivers
for a HVR-1250.
I got the drivers compiled recently using the latest source from
v4l-dvb. I saw that cx23885 loaded and detected the card ok, so I
tried watching video in mythtv, to no avail. I then tried dumping
On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote:
Jarryd Beck wrote:
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote:
Then, please turn ON debug, repeat your tests, and post again with
dmesg. I am not familiar with the af9015 driver, but for
On Wed, Mar 12, 2008 at 8:51 PM, raphy [EMAIL PROTECTED] wrote:
Hi all,
A while back I reported I was having problems with compiling drivers
for a HVR-1250.
I got the drivers compiled recently using the latest source from
v4l-dvb. I saw that cx23885 loaded and detected the card ok, so I
Alright, here is the new dmesg output http://pastebin.com/m35d1137d.
Brandon
On Tue, Mar 11, 2008 at 8:11 AM, Chaogui Zhang [EMAIL PROTECTED] wrote:
On Tue, Mar 11, 2008 at 3:36 AM, Brandon Rader [EMAIL PROTECTED]
wrote:
I tried the different repo that you suggested, and get the same error.
I just put my new HVR-1800 in and restarted and found lspci dosen't see it.
I have not redone drivers yet. They are still built only for the Nexus. I
have searched all the logs for ref to the chip used, but nothing. Google
came back with a lot of people having problems with lspci and PCIe cards.
37 matches
Mail list logo
