On Tue, October 3, 2006 22:43, C.Y.M said:
David Härdeman wrote:
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,
On Wed, October 4, 2006 1:20, Oliver Endriss said:
Torgeir Veimo wrote:
Those double keypress issues are also present when using the linux
input system, it's not LIRC dependent at all.
...
Solution:
The application must grab the input device for exclusive access.
In other words: Get LIRC
On Wed, October 4, 2006 10:44, Torgeir Veimo said:
On 4 Oct 2006, at 08:35, David Härdeman wrote:
The solution is simple, get rid of LIRC
Well I run an application without X while taking input only using the
linux input system, and I'm still having problems with multiple input
when pressing
Tomislav Bodor wrote:
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:
David Härdeman wrote:
On Wed, October 4, 2006 10:44, Torgeir Veimo said:
On 4 Oct 2006, at 08:35, David Härdeman wrote:
The solution is simple, get rid of LIRC
Well I run an application without X while taking input only using the
linux input system, and I'm still having problems with
On Wed, October 4, 2006 12:53, Oliver Endriss said:
David Härdeman wrote:
On Wed, October 4, 2006 10:44, Torgeir Veimo said:
Well I run an application without X while taking input only using the
linux input system, and I'm still having problems with multiple input
when pressing a single key.
David Härdeman wrote:
On Wed, October 4, 2006 1:20, Oliver Endriss said:
Torgeir Veimo wrote:
Those double keypress issues are also present when using the linux
input system, it's not LIRC dependent at all.
...
Solution:
The application must grab the input device for exclusive access.
On 4 Oct 2006, at 11:53, Oliver Endriss wrote:
Afaik the av7110 ir driver works correctly.
I think it's in fact the cx88-input driver that is at fault.
--
Torgeir Veimo
[EMAIL PROTECTED]
___
linux-dvb mailing list
linux-dvb@linuxtv.org
Hi,
Aapo wrote a driver for anoter m920x based device, it just contains
another tuner afaik.
Could you provide some usbsnoop logfiles
http://linuxtv.org/v4lwiki/index.php/USBVideo and upload them
somewhere (raw usbsnoop logfiles would also be nice), maybe also start
a wikisite with all the
Robin Hill wrote:
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
KevinLuX wrote:
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
Some more mixed news.
I patched Chris' tree with the new device IDs (following your instructions) and
tried again to just run a scan - no dice. But it certainly looks like you might
be on to something - I saw some new messages from the driver shortly before
the lockup:
tune to:
On 10/4/06, Emilio Castellano [EMAIL PROTECTED] wrote:
KevinLuX wrote:
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
Hi,
The WinTV-HVR3000 has a single transport bus on the cx2388x shared
between a cx22702 DVB-T and a cx24123 DVB-S. The windows driver manages
the hardware to ensure an application can stream from one or the other
demod.
In terms of Linux and the current tree, it's a trivial thing to add
Le Mercredi 04 Octobre 2006 18:08, Steven Toth a écrit :
Hi,
The WinTV-HVR3000 has a single transport bus on the cx2388x shared
between a cx22702 DVB-T and a cx24123 DVB-S. The windows driver manages
the hardware to ensure an application can stream from one or the other
demod.
In terms of
Hi,
I have got this error-message. I'm using a TT-connect S-1200.
I have found following chips on the Board:
STV0299B
TDA8060
TSA5059
Can please somebody help me for running this card?
Thanks a lot
Stefan
___
linux-dvb mailing list
On Sat Sep 30, 2006 at 06:49:45PM +0100, Robin Hill wrote:
I've just installed a couple of Nova-T-500s in my media system and,
after a bit of digging, have got them working fine with the current
checked out drivers. However, the remote control doesn't seem to be
working at all - has anyone
All,
I'm not sure whether anyone has the IR working for the Nova-T-USB2 with
the Hauppauge firmware, but just in case it isn't:
Send 2 byte buffer to pipe0 containing 0x04 0x35
Read 4 byte buffer fr pipe1 containing:
// Bytes: 76543210 76543210 76543210 76543210
//
Michael Krufky wrote:
Patrick,
Could you look over the changesets in this tree and let me know whether
or not you approve of this?
Aapo,
After you sent your patch in to the linux-dvb mailing list, Patrick had
some comments and requests for certain things to be cleaned up. I have
not seen any
On Sun, 2006-10-01 at 21:58 +0200, [EMAIL PROTECTED] wrote:
Hi Guys,
I have been looking into the 'tv_grab_dvb' project, and tried using it
with my Danish Canal Digital subscribtion.
I can find data with the application, but it only contains now/next
listings, which is sort of useless to
Hi,
Tomislav Bodor wrote:
Tomislav Bodor wrote:
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
Hi,
On 10/4/06, Gunther Mayer [EMAIL PROTECTED] wrote:
Michael Krufky wrote:
Patrick,
Could you look over the changesets in this tree and let me know whether
or not you approve of this?
Aapo,
After you sent your patch in to the linux-dvb mailing list, Patrick had
some comments and
Gunther Mayer wrote:
I believe you are wrong, the USB IDs differ:
0db0:5580 = MSI Megasky 580 (with m920x)
0db0:5581 = MSI Megasky 580 (with gl861)
Yes, thank you. We realized that a few days ago, and I've already made
the appropriate change in the megasky tree:
Hi!
Christoph Höger [EMAIL PROTECTED] wrote
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.
It seems that this is a
Hi, Folks
This patch should make make the Pinnacle 310i DVB-T working.
It is based on the patch by Pierluigi_Rolando and should apply
to the v4l-dvb repository at http://www.linuxtv.org of today.
I don't have this card, so i need you to test it.
The card should be fully working except remote
Steven Toth writes:
The simple thing about a solution like this is that:
a. a/t/szap -a fenum worked with zero changes.
b. The recent cx88 bus arbitration patches ensured that only one of
adapter0/fe0 or adapter1/fe could be opened at any one time. (As expected).
I don't see solution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael
Some more help needed with the version 1 card you helped me with last
time.
Just got the auto update to my kernel to suse version: 2.6.16.21-0.25,
so I tried to recompile my running version of the v4l tree from last
time to find it does
Am Mittwoch, den 04.10.2006, 16:36 -0400 schrieb Michael Krufky:
Gunther Mayer wrote:
[...]
On another note, Gunther, I have to second Markus' comment:
Gunther, could you do us a favour and split up your site a bit..
The index file already takes around 2.6 MB (without images) .. it's a
28 matches
Mail list logo
