Linus,
Please pull from:
ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git
for_linus
For a series of345 patches that contain:
- new tuner driver for max2165;
- new dvb-usb driver for ec168;
- new frontend drivers for atbm8830, ds3000, ec100, s
On Tue, 2009-12-08 at 23:30 +0100, Christoph Bartelmus wrote:
> Hi Andy,
>
> on 07 Dec 09 at 23:10, Andy Walls wrote:
> [...]
> > (Christoph can correct me if I get anything wrong.)
>
> Just a few additions.
Christoph,
Thanks for the corrections and additions. :)
> [...]
> > I know that the h
Jon Smirl wrote:
>> I don't like the idea of automatically loading 3 different keycodes at the
>> same time. You may have overlaps between different keycode tables. The
>> better is to have some userspace GUI that will allow the user to select
>> what keycode table(s) he want to be available, if h
Dmitry Torokhov wrote:
> I am a resonable guy ;) In cases when we can certainly say that there
> are 2 separate remotes (and we know characteristics somehow) we need to
> create 2 input devices. Otherwise we can't ;)
Only on very few specific cases (a few protocols), you can be (almost) sure.
Ev
Krzysztof Halasa wrote:
> Jon Smirl writes:
>
>> Why do you want to pull the 1KB default mapping table out of the
>> device driver __init section and more it to a udev script? Now we will
>> have to maintain a parallel udev script for ever receiver's device
>> driver.
>
> Of course no. We will n
Manu Abraham wrote:
>> Not true. As pointed at the previous answer, the difference between a new
>> ioctl
>> and S2API is basically the code at dtv_property_prepare_get_stats() and
>> dtv_property_process_get(). This is a pure code that uses a continuous struct
>> that will likely be at L3 cache,
Jon Smirl writes:
> Why do you want to pull the 1KB default mapping table out of the
> device driver __init section and more it to a udev script? Now we will
> have to maintain a parallel udev script for ever receiver's device
> driver.
Of course no. We will need a single program (script etc.) f
Hi Andy,
on 07 Dec 09 at 23:10, Andy Walls wrote:
[...]
> (Christoph can correct me if I get anything wrong.)
Just a few additions.
[...]
>> What is the time standard for the data, where does it come from?
> I think it is usec, IIRC.
Yes, it is.
> I know that the hardware I work with has sub
Hi Jon,
on 08 Dec 09 at 08:34, Jon Smirl wrote:
[...]
> The point of those design review questions was to illustrate that the
> existing LIRC system is only partially designed. Subsystems need to be
> fully designed before they get merged.
I'd say that a system that has proven itself in real worl
Hi Dmitry,
on 06 Dec 09 at 23:51, Dmitry Torokhov wrote:
[...]
>>> I suppose we could add MSC_SCAN_END event so that we can transmit
>>> "scancodes" of arbitrary length. You'd get several MSC_SCAN followed by
>>> MSC_SCAN_END marker. If you don't get MSC_SCAN_END assume the code is 32
>>> bit.
>>
On Tue, Dec 8, 2009 at 5:22 PM, Mauro Carvalho Chehab
wrote:
> Hi Julian,
>
> Let me add some corrections to your technical analysis.
>
> Julian Scheel wrote:
>> Hello together,
>>
>> after the last thread which asked about signal statistics details
>> degenerated into a discussion about the techn
From: Muralidharan Karicheri
If a USERPTR address that is not aligned to page boundary is passed to the
videobuf_dma_contig_user_get() function, it saves a page aligned address to
the dma_handle. This is not correct. This issue is observed when using USERPTR
IO machism for buffer exchange.
Updat
> 2009/9/14 Michael Krufky :
>> On Wed, Sep 9, 2009 at 11:08 AM, Michael Krufky
>> wrote:
>>> On Wed, Sep 9, 2009 at 10:01 AM, wrote:
On Tue, Sep 08, 2009 at 05:57:12PM -0400, Michael Krufky wrote:
>
> Henk,
>
> Why do you expect a 8295? If your board uses the SAA7131, the
Vaibhav,
I have posted a re-worked patch with clocks configuration moved
to ccdc. From your response below, I understand the clocks
are being called differently on different SoCs even though they
use the same IP. So IMO, it is better to customize it on a SoC
by defining the clock names in the res
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Tue Dec 8 19:00:02 CET 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 13588:065f9e34e07b
gcc version: gcc (
On Tue, Dec 8, 2009 at 11:27 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 9:34 AM, Mauro Carvalho Chehab
>> wrote:
>>> Jon Smirl wrote:
On Tue, Dec 8, 2009 at 8:59 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 8:3
On 7 декабря 2009 05:35:46 Andy Walls wrote:
> On Mon, 2009-12-07 at 03:23 +0200, Igor M. Liplianin wrote:
> > On 6 декабря 2009 23:40:54 Andy Walls wrote:
> > > On Sun, 2009-11-22 at 03:03 +0200, Igor M. Liplianin wrote:
> > > > On 21 ноября 2009 22:41:42 Andy Walls wrote:
> > > > > > Matthias Fec
On Tue, Dec 8, 2009 at 12:35 PM, Rob Beard wrote:
> Hi folks,
>
> I've borrowed a WinTV HVR-900 USB stick from a friend of mine to see if I
> can get any reception in my area before forking out for one however I've run
> in to a couple of problems and wondered if anyone had used one of these
> sti
> -Original Message-
> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Karicheri, Muralidharan
> Sent: Thursday, December 03, 2009 9:25 PM
> To: Hiremath, Vaibhav; linux-media@vger.kernel.org;
> hverk...@xs4all.nl; khil...@deeprootsystems.
On Tue, Dec 08, 2009 at 02:57:15PM +0100, Krzysztof Halasa wrote:
> Dmitry Torokhov writes:
>
> > Why woudl we want to do this? Quite often there is a need for "observer"
> > that maybe does not act on data but allows capturing it. Single-user
> > inetrfaces are PITA.
>
> Lircd can work as a mul
On Tue, Dec 08, 2009 at 07:46:52AM -0500, Andy Walls wrote:
> On Tue, 2009-12-08 at 09:32 -0200, Mauro Carvalho Chehab wrote:
> > Andy Walls wrote:
> > > On Mon, 2009-12-07 at 13:19 -0500, Jarod Wilson wrote:
>
> > > So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
> > > end
On Tue, Dec 08, 2009 at 09:17:42AM -0200, Mauro Carvalho Chehab wrote:
> Jon Smirl wrote:
> > On Mon, Dec 7, 2009 at 6:44 PM, Mauro Carvalho Chehab
> > wrote:
>
> >>> Where is the documentation for the protocol?
> >> I'm not sure what you're meaning here. I've started a doc about IR at the
> >>
On Tue, Dec 08, 2009 at 07:52:02AM -0500, Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
> > On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
> >> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
> >
> >> > So I'll whip up an RC-6 Mode 6A decoder for cx238
On Tue, Dec 08, 2009 at 09:58:53AM -0200, Mauro Carvalho Chehab wrote:
> Dmitry Torokhov wrote:
> > On Mon, Dec 07, 2009 at 09:44:14PM -0200, Mauro Carvalho Chehab wrote:
>
> >>> What about capabilities of the receiver, what frequencies?
> >>> If a receiver has multiple frequencies, how do you rep
On Tue, Dec 08, 2009 at 09:44:29AM -0200, Mauro Carvalho Chehab wrote:
> Dmitry Torokhov wrote:
> > On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
> >> On Mon, 2009-12-07 at 13:19 -0500, Jarod Wilson wrote:
> >>> On Nov 26, 2009, at 2:43 PM, Andy Walls wrote:
> >>>
> On Thu, 2009-
Hi Guennadi,
On 12/7/09, Guennadi Liakhovetski wrote:
> Hi Alan
>
> On Mon, 7 Dec 2009, Alan Carvalho de Assis wrote:
>
> It's always better to cc a suitable list, in this case it is
>
> Linux Media Mailing List
>
Sure, here we go.
>
>> I am trying to use an OV2640 camera with soc_camera.
>>
>
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 9:34 AM, Mauro Carvalho Chehab
> wrote:
>> Jon Smirl wrote:
>>> On Tue, Dec 8, 2009 at 8:59 AM, Mauro Carvalho Chehab
>>> wrote:
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 8:30 AM, Mauro Carvalho Chehab
> wrote:
>> Andy Walls wrote:
>
On Tue, Dec 8, 2009 at 10:49 AM, Mauro Carvalho Chehab
wrote:
> Krzysztof Halasa wrote:
>> Mauro Carvalho Chehab writes:
>>
>>> If you use a kfifo to store the event (space_or_mark, timestamp),
>>> the IRQ handler can return immediately, and a separate kernel thread
>>> can do the decode without
Mauro Carvalho Chehab writes:
> Jon Smirl wrote:
>
>> This model is complicated by the fact that some remotes that look
>> like multi-function remotes aren't really multifunction. The remote
>> bundled with the MS MCE receiver is one. That remote is a single
>> function device even though it has
On Tue, Dec 8, 2009 at 9:40 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 9:16 AM, Mauro Carvalho Chehab
>> wrote:
>>> Jon Smirl wrote:
On Tue, Dec 8, 2009 at 8:40 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 7:35
I accidently sent this mail to Michael's private address, I'm sorry for that.
Hi,
I bought the same card a couple of months ago and back then, it just
wouldn't work. I set up a wiki page, which henk has updated with links
to patches, to document the card as well as possible. I set up a
thread on
On Tue, Dec 8, 2009 at 9:34 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 8:59 AM, Mauro Carvalho Chehab
>> wrote:
>>> Jon Smirl wrote:
On Tue, Dec 8, 2009 at 8:30 AM, Mauro Carvalho Chehab
wrote:
> Andy Walls wrote:
>> On Mon, 2009-12-07 at 20:2
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab writes:
>
>> If you use a kfifo to store the event (space_or_mark, timestamp),
>> the IRQ handler can return immediately, and a separate kernel thread
>> can do the decode without needing to touch at the IRQ.
>
> But the decoding itself is a real
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab writes:
>
>> The enable/disable protocol decoder enable/disable interface is needed
>> anyway,
>> due to the needs for the hardware IR decoders
>
> Why do they need it exactly?
> The key tables say all they need I hope?
You can't upload a key for
Mauro Carvalho Chehab writes:
> If you use a kfifo to store the event (space_or_mark, timestamp),
> the IRQ handler can return immediately, and a separate kernel thread
> can do the decode without needing to touch at the IRQ.
But the decoding itself is a really simple thing, why complicate it?
Mauro Carvalho Chehab writes:
> The enable/disable protocol decoder enable/disable interface is needed anyway,
> due to the needs for the hardware IR decoders
Why do they need it exactly?
The key tables say all they need I hope?
--
Krzysztof Halasa
--
To unsubscribe from this list: send the lin
Dmitry Torokhov writes:
> No, the IR core responsible for registering receivers and decoders.
Well. This makes me think now that LIRC can be just "another decoder".
>> Those are simple things. The only part which needs to be stable is the
>> (in this case LIRC) kernel-user interface.
>
> For wh
On 2009-12-08 13:31, Thomas Kernen wrote:
Matthias Wächter wrote:
Hallo Thomas!
Am 02.12.2009 15:31, schrieb Thomas Kernen:
Is someone already working on supporting the TBS 6980 Dual DVB-S2 PCIe
card? http://www.tbsdtv.com/english/product/6980.html
I got one last Thursday, also direct from T
On 04.12.2009 05:59, Justin P. Mattock wrote:
> On 12/03/09 18:05, Daniel Ritz wrote:
>> Hi Laurent
>>
>> On Thu, 2009-12-03 at 21:15 +0100, Laurent Pinchart wrote:
>>> Hi Daniel,
>>>
>>> On Wednesday 02 December 2009 00:48:44 Daniel Ritz wrote:
For some unknown reason, on a MacBookPro5,3 the
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 6:17 AM, Mauro Carvalho Chehab
> wrote:
>> Jon Smirl wrote:
>>> On Mon, Dec 7, 2009 at 6:44 PM, Mauro Carvalho Chehab
>>> wrote:
> Where is the documentation for the protocol?
I'm not sure what you're meaning here. I've started a doc about IR at
On Tue, Dec 8, 2009 at 9:07 AM, Mauro Carvalho Chehab
wrote:
> Krzysztof Halasa wrote:
>> Mauro Carvalho Chehab writes:
>>
What is the interface for attaching an in-kernel decoder?
>>> IMO, it should use the kfifo for it. However, if we allow both raw data and
>>> in-kernel decoders to read
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 9:16 AM, Mauro Carvalho Chehab
> wrote:
>> Jon Smirl wrote:
>>> On Tue, Dec 8, 2009 at 8:40 AM, Mauro Carvalho Chehab
>>> wrote:
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
>> On Mon, 2009-12-07 at 20:22 -0800, Dmitr
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 8:59 AM, Mauro Carvalho Chehab
> wrote:
>> Jon Smirl wrote:
>>> On Tue, Dec 8, 2009 at 8:30 AM, Mauro Carvalho Chehab
>>> wrote:
Andy Walls wrote:
> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
>> On Mon, Dec 07, 2009 at 09:42:22
On Tue, Dec 8, 2009 at 9:16 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 8:40 AM, Mauro Carvalho Chehab
>> wrote:
>>> Jon Smirl wrote:
On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
>> On
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab writes:
>> IMO, the better is to have an API to allow creation of multiple interfaces
>> per IR receiver, based on some scancode matching table and/or on some
>> matching mask.
>
> I think setting the keytables for each logical device would do.
Yes
On Tue, Dec 8, 2009 at 8:59 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 8:30 AM, Mauro Carvalho Chehab
>> wrote:
>>> Andy Walls wrote:
On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 8:40 AM, Mauro Carvalho Chehab
> wrote:
>> Jon Smirl wrote:
>>> On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
>> So I'
Mauro Carvalho Chehab writes:
> With RC-5, you have no fields describing the remote. So, all the driver could
> do is an educated guess.
It can't even do that, e.g. single remotes (even the dumb ones) can send
different code groups (addresses) for different keys.
> IMO, the better is to have an
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab writes:
>
>> I don't think we need an userspace interface for the in-kernel
>> decoders.
>
> Of course we need it, to set (and probably retrieve) scancode-keycode
> mappings. This could probably be, ATM, the existing input layer channel.
This is t
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab writes:
>
>>> What is the interface for attaching an in-kernel decoder?
>> IMO, it should use the kfifo for it. However, if we allow both raw data and
>> in-kernel decoders to read data there, we'll need a spinlock to protect the
>> kfifo.
>
> This
Mauro Carvalho Chehab writes:
> Yes, an opaque type for scancode at the userspace API can be better, but
> passing a pointer to kernel will require some compat32 logic (as pointer
> size is different on 32 and 64 bits).
Yes. I think we can't avoid that, but it's a single compat handler,
I wouldn
On Tue, Dec 8, 2009 at 8:40 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
>>> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
> So I'll whip up an RC-6 Mode 6A
Mauro Carvalho Chehab writes:
> I don't think we need an userspace interface for the in-kernel
> decoders.
Of course we need it, to set (and probably retrieve) scancode-keycode
mappings. This could probably be, ATM, the existing input layer channel.
> All
> it needs is to enable/disable the pro
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 8:30 AM, Mauro Carvalho Chehab
> wrote:
>> Andy Walls wrote:
>>> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
> So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c be
Dmitry Torokhov writes:
> Why woudl we want to do this? Quite often there is a need for "observer"
> that maybe does not act on data but allows capturing it. Single-user
> inetrfaces are PITA.
Lircd can work as a multiplexer. IMHO single-open lirc interface is ok,
though we obviously need simult
Jon Smirl writes:
> Data could be sent to the in-kernel decoders first and then if they
> don't handle it, send it to user space.
Nope. It should be sent to all of them, they aren't dependent.
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the b
Mauro Carvalho Chehab writes:
>> What is the interface for attaching an in-kernel decoder?
>
> IMO, it should use the kfifo for it. However, if we allow both raw data and
> in-kernel decoders to read data there, we'll need a spinlock to protect the
> kfifo.
This may be an option, but I think we
On Tue, Dec 8, 2009 at 8:30 AM, Mauro Carvalho Chehab
wrote:
> Andy Walls wrote:
>> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
>>> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
>>
So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
end of t
Jon Smirl wrote:
> On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
>> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
>>> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
end of the month.
On Tue, Dec 8, 2009 at 6:17 AM, Mauro Carvalho Chehab
wrote:
> Jon Smirl wrote:
>> On Mon, Dec 7, 2009 at 6:44 PM, Mauro Carvalho Chehab
>> wrote:
>
Where is the documentation for the protocol?
>>> I'm not sure what you're meaning here. I've started a doc about IR at the
>>> media
>>
>> Wha
Matthias Wächter wrote:
Hallo Thomas!
Am 02.12.2009 15:31, schrieb Thomas Kernen:
Is someone already working on supporting the TBS 6980 Dual DVB-S2 PCIe
card? http://www.tbsdtv.com/english/product/6980.html
Have you seen/tried their all-in-one linux source package which was
released 2009-12-0
Andy Walls wrote:
> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
>> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
>
>>> So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
>>> end of the month.
>>>
>>> I can setup the CX2388[58] hardware to look for bo
Hi Julian,
Let me add some corrections to your technical analysis.
Julian Scheel wrote:
> Hello together,
>
> after the last thread which asked about signal statistics details
> degenerated into a discussion about the technical possibilites for
> implementing an entirely new API, which lead to n
On Tue, Dec 8, 2009 at 7:35 AM, Andy Walls wrote:
> On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
>> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
>
>> > So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
>> > end of the month.
>> >
>> > I can setup th
On Tue, 2009-12-08 at 09:32 -0200, Mauro Carvalho Chehab wrote:
> Andy Walls wrote:
> > On Mon, 2009-12-07 at 13:19 -0500, Jarod Wilson wrote:
> > So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
> > end of the month.
>
> Good! Please, try to design the decoder as an indepen
On Mon, 2009-12-07 at 20:22 -0800, Dmitry Torokhov wrote:
> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
> > So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the
> > end of the month.
> >
> > I can setup the CX2388[58] hardware to look for both RC-5 and RC-6 with
World's No 1 doctor recommended solution to many of the common intimacy
problems. http://dhwtd.ecwyqutt.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-in
Am 08.12.09 10:16, schrieb Julian Scheel:
Hello together,
after the last thread which asked about signal statistics details
degenerated into a discussion about the technical possibilites for
implementing an entirely new API, which lead to nothing so far, I
wanted to open a new thread to bring
Dmitry Torokhov wrote:
> On Mon, Dec 07, 2009 at 09:44:14PM -0200, Mauro Carvalho Chehab wrote:
>>> What about capabilities of the receiver, what frequencies?
>>> If a receiver has multiple frequencies, how do you report what
>>> frequency the data came in on?
>> IMO, via sysfs.
>
> We probably n
Dmitry Torokhov wrote:
> On Mon, Dec 07, 2009 at 09:42:22PM -0500, Andy Walls wrote:
>> On Mon, 2009-12-07 at 13:19 -0500, Jarod Wilson wrote:
>>> On Nov 26, 2009, at 2:43 PM, Andy Walls wrote:
>>>
On Thu, 2009-11-26 at 12:05 -0200, Mauro Carvalho Chehab wrote:
> Krzysztof Halasa wrote:
>>
Andy Walls wrote:
> On Mon, 2009-12-07 at 13:19 -0500, Jarod Wilson wrote:
>> On Nov 26, 2009, at 2:43 PM, Andy Walls wrote:
>>
>>> On Thu, 2009-11-26 at 12:05 -0200, Mauro Carvalho Chehab wrote:
Krzysztof Halasa wrote:
> Andy Walls writes:
>
>> I would also note that RC-6 Mode 6A
Jon Smirl wrote:
> On Mon, Dec 7, 2009 at 1:41 PM, Dmitry Torokhov
> wrote:
>> That is why I think we should go the other way around - introduce the
>> core which receivers could plug into and decoder framework and once it
>> is ready register lirc-dev as one of the available decoders.
>
> The co
Jon Smirl wrote:
> On Mon, Dec 7, 2009 at 6:44 PM, Mauro Carvalho Chehab
> wrote:
>>> Where is the documentation for the protocol?
>> I'm not sure what you're meaning here. I've started a doc about IR at the
>> media
>
> What is the format of the pulse stream data coming out of the lirc device?
Hallo Thomas!
Am 02.12.2009 15:31, schrieb Thomas Kernen:
> Is someone already working on supporting the TBS 6980 Dual DVB-S2 PCIe
> card? http://www.tbsdtv.com/english/product/6980.html
Have you seen/tried their all-in-one linux source package which was
released 2009-12-03?
http://www.tbsdtv.co
Dmitry Torokhov a écrit :
On Mon, Dec 07, 2009 at 06:54:39PM +0100, Emmanuel Fusté wrote:
Mauro Carvalho Chehab wrote:
In summary,
While the current EVIO[G|S]KEYCODE works sub-optimally for scancodes up
to 16 bytes
(since a read loop for 2^16 is not that expensive), the current appr
Hello together,
after the last thread which asked about signal statistics details
degenerated into a discussion about the technical possibilites for
implementing an entirely new API, which lead to nothing so far, I wanted
to open a new thread to bring this forward. Maybe some more people can
> Mauro,
>
> Resend of my proposed patch attached that reverts tuning regressions with
> my DViCO card, whilst still fixing the original 6Mhz tuning issue. Please
> merge or let me know how else I should proceed to get this merged.
>
> Thanks
>
> -Rob
perhaps the attached notes will help Rob's ca
77 matches
Mail list logo
