linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Schwarzott <zzam@gentoo.org>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH] [media] mceusb: select default keytable based on vendor
Date: Tue, 29 Jul 2014 20:29:20 +0200	[thread overview]
Message-ID: <53D7E800.4000608@gentoo.org> (raw)
In-Reply-To: <20140729110631.2443620c.m.chehab@samsung.com>

On 29.07.2014 16:06, Mauro Carvalho Chehab wrote:
> Em Tue, 29 Jul 2014 07:45:29 +0200
> Matthias Schwarzott <zzam@gentoo.org> escreveu:
> 
>> On 27.07.2014 22:47, Mauro Carvalho Chehab wrote:
>>> Some vendors have their on keymap table that are used on
>>> all (or almost all) models for that vendor.
>>>
>>> So, instead of specifying the keymap table per USB ID,
>>> let's use the Vendor ID's table by default.
>>>
>>> At the end, this will mean less code to be added when newer
>>> devices for those vendors are added.
>>>
>>
>> I also did prepare something to add mceusb support, but with this only
>> vendor dependant rc_map selection, it definitly is less code.
>>
>> Your mceusb patches work correctly for my 930C-HD (b130) and PCTV 522e
>> devices.
> 
> Thanks for testing!
> 
Testing IR is fast to do :)

> Btw, do you have plans to add DVB-C support to the frontend too?
> I think that this is the only big feature missing.
> 
Yes, adding DVB-C Support is my next large goal.

Regards
Matthias


      reply	other threads:[~2014-07-29 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 20:47 [PATCH] [media] mceusb: select default keytable based on vendor Mauro Carvalho Chehab
2014-07-29  5:45 ` Matthias Schwarzott
2014-07-29 14:06   ` Mauro Carvalho Chehab
2014-07-29 18:29     ` Matthias Schwarzott [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53D7E800.4000608@gentoo.org \
    --to=zzam@gentoo.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mchehab@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).