Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe mantis' my prompt never returns. The machine still
is working.
[snip]
Michel Verbraak wrote:
Aug 26 11:08:32 recorder kernel: ivtv0 i2c: i2c client attach
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 00 ]
Aug 26 11:08:32 recorder kernel:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe mantis' my prompt never returns.
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe
Michel Verbraak wrote:
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
Michael Krufky wrote:
is
Hans and Manu,
The mantis and ivtv module loaded ok with the following options for
saa7115 in /etc/modprobe.conf:
options saa7115 ignore=-1,0x25,-1,0x24,-1,0x21,-1,0x20
^^
Just change the -1 to the i2c bus ID
The Linux-DVB API is currently not able to handle ISDB-T . I.e. there is
no userspace application which could talk (correctly) to a device.
Furthermore there is no device-driver yet there which could lock on a
ISDB-T signal.
But starting the discussion on that, would be a great idea:
Hi,
I'm trying to get a Twinham Skybox working under 2.6.21-2 (Debian Lenny). Using
szap I'm not getting any signal i.e.:
# szap -c /home/myth/channels-dvb-hotbird.conf Mediatel -a 1
zapping to 1 'Mediatel':
sat 0, frequency = 10949 MHz V, symbolrate 2750, vpid = 0x1389, apid =
0x1393
Manu Abraham wrote:
Michael Krufky wrote:
is
Hans and Manu,
The mantis and ivtv module loaded ok with the following options for
saa7115 in /etc/modprobe.conf:
options saa7115 ignore=-1,0x25,-1,0x24,-1,0x21,-1,0x20
^^
Just change the -1
Michael Krufky wrote:
Manu,
You can go on and on about how probing is wrong -- I already agree with you
in that respect. Regardless, the saa7115 driver does this probe, and this
will not change until after the new i2c methods are implemented in the video
decoder i2c_client modules.
On Sunday 26 August 2007 18:45:44 Michael Krufky wrote:
Manu Abraham wrote:
Michael Krufky wrote:
is
Hans and Manu,
The mantis and ivtv module loaded ok with the following options
for saa7115 in /etc/modprobe.conf:
options saa7115 ignore=-1,0x25,-1,0x24,-1,0x21,-1,0x20
Manu Abraham wrote:
Michael Krufky wrote:
Manu,
You can go on and on about how probing is wrong -- I already agree with you
in that respect. Regardless, the saa7115 driver does this probe, and this
will not change until after the new i2c methods are implemented in the video
decoder
Nava Whiteford wrote:
Hi,
I'm trying to get a Twinham Skybox working under 2.6.21-2 (Debian Lenny).
Using szap I'm not getting any signal i.e.:
# szap -c /home/myth/channels-dvb-hotbird.conf Mediatel -a 1
zapping to 1 'Mediatel':
sat 0, frequency = 10949 MHz V, symbolrate 2750, vpid
Hans Verkuil wrote:
And I would appreciate comments on my approach to implement the
new-style i2c API to existing i2c drivers. See the topic [RFC]
Converting wm8775.c to new-style I2C API in the video4linux
mailinglist.
Attempts to make things better are appreciated. :) Don't have those
Michael Krufky wrote:
What can be simpler than that?
Sometimes it is better to keep quiet, rather than to explain to people.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Patrick Boettcher wrote:
The Linux-DVB API is currently not able to handle ISDB-T . I.e. there is
no userspace application which could talk (correctly) to a device.
Furthermore there is no device-driver yet there which could lock on a
ISDB-T signal.
But starting the discussion on that,
Michael Krufky wrote:
I'm not saying that anything is wrong with Mantis -- I am merely stating
that since Mantis doesn't use probed i2c clients, that Mantis should
simply disallow such probing.
What can be simpler than that?
Hey jumpy ! Everytime one faces the same problem, You have
On Sunday 26 August 2007 19:23:42 Manu Abraham wrote:
Hans Verkuil wrote:
And I would appreciate comments on my approach to implement the
new-style i2c API to existing i2c drivers. See the topic [RFC]
Converting wm8775.c to new-style I2C API in the video4linux
mailinglist.
Attempts to
Michael Krufky schreef:
Michel Verbraak wrote:
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
Hi all!
Im currently trying to set up my new Hauppauge Nova-T 500. I have
followed the instructions in this manual exactly:
http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_500_PCI
Unfortunately, loading the firmeware fails. Here is my dmesg-output:
[350864.383841] dib0700: loaded
Le dimanche 26 août 2007 23:02, Tobias Hovorka a écrit :
Hi all!
Im currently trying to set up my new Hauppauge Nova-T 500. I have
followed the instructions in this manual exactly:
http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_500_PCI
Unfortunately, loading the firmeware
Am Sonntag, den 26.08.2007, 21:56 +0400 schrieb Manu Abraham:
Michael Krufky wrote:
I'm not saying that anything is wrong with Mantis -- I am merely stating
that since Mantis doesn't use probed i2c clients, that Mantis should
simply disallow such probing.
What can be simpler than
Well, it looks like either the kernel (stock FC6 2.6.20) or the driver itself
is broken. Reverting to 2.6.18 (with minor patches to the r8169 Ethernet
driver source) and installing Steve Toth's hvr3000 driver has enabled most of
the card's features. The analogue TV tuner isn't working properly
24 matches
Mail list logo
