All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Barszus <steffenbpunkt@googlemail.com>
To: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>,
	Jarod Wilson <jarod@wilsonet.com>
Cc: "Antti Palosaari" <crope@iki.fi>,
	stybla@turnovfree.net, "Sascha Wüstemann" <sascha@killerhippy.de>,
	linux-media@vger.kernel.org,
	"Thomas Holzeisen" <thomas@holzeisen.de>,
	"Maxim Levitsky" <maximlevitsky@gmail.com>
Subject: Re: RTL2831U driver updates
Date: Wed, 22 Jun 2011 08:13:59 +0200	[thread overview]
Message-ID: <20110622081359.6d55979a@grobi> (raw)
In-Reply-To: <4E017EE7.9040902@hoogenraad.net>

On Wed, 22 Jun 2011 07:34:31 +0200
Jan Hoogenraad <jan-conceptronic@hoogenraad.net> wrote:

> Thanks. Do you know more about this subject ?
> 
> We do have specs about the chipset, but
> 
> http://linuxtv.org/downloads/v4l-dvb-apis/remote_controllers.html#Remote_controllers_Intro
> 
> only mentions lirc, not rc-core.
> This is about where my knowledge stops, however.
> 
> rc-core is only mentioned shortly in:
> http://linuxtv.org/wiki/index.php/Remote_Controllers

I think/hope Jarod can comment on this - i just know that new remotes
should use rc-core, as this is the "new thing" for this. I'm no
developer whatsoever :)

> 
> Steffen Barszus wrote:
> > 2011/6/21 Jan Hoogenraad<jan-conceptronic@hoogenraad.net>:
> >> and add the IR remote interface, based
> >> on the LIRC framework.
> >> It actually should yield little code, and mainly requires a)
> >> understanding of LIRC and b) comparing code tables to that the
> >> in-kernel code tables can be re-used.
> >
> >
> > sorry for the noise , but i guess you mean rc-core not Lirc
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-media" in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> 


  reply	other threads:[~2011-06-22  6:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  8:19 RTL2831U wont compile against 2.6.38 Thomas Holzeisen
2011-06-16 11:34 ` Sascha Wüstemann
2011-06-16 21:36   ` RTL2831U driver updates Jan Hoogenraad
2011-06-17  8:30     ` Sascha Wüstemann
2011-06-17 14:17       ` Thomas Holzeisen
2011-06-20 16:10     ` poma
2011-06-20 22:22     ` Antti Palosaari
2011-06-21  5:40       ` Jan Hoogenraad
2011-06-21  8:03         ` Steffen Barszus
2011-06-22  5:34           ` Jan Hoogenraad
2011-06-22  6:13             ` Steffen Barszus [this message]
2011-06-22 11:11               ` Antti Palosaari
2011-06-21  9:41       ` Maxim Levitsky
2011-06-21 10:00         ` Jan Hoogenraad
2011-07-09  3:27           ` Antti Palosaari
2011-08-04 23:43             ` Antti Palosaari
2011-08-06  3:56               ` Alistair Buxton
2011-08-06  5:13                 ` Alistair Buxton
2011-08-08 19:50                   ` Antti Palosaari
2011-08-09 13:22                     ` Alistair Buxton
2011-10-21 20:41                       ` Alistair Buxton
2011-06-17 10:39   ` RTL2831U wont compile against 2.6.38 Thomas Holzeisen
2011-06-17 19:28     ` Sascha Wüstemann
2011-06-18 12:44       ` Thomas Holzeisen
2011-06-18 12:56         ` Antti Palosaari

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=20110622081359.6d55979a@grobi \
    --to=steffenbpunkt@googlemail.com \
    --cc=crope@iki.fi \
    --cc=jan-conceptronic@hoogenraad.net \
    --cc=jarod@wilsonet.com \
    --cc=linux-media@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=sascha@killerhippy.de \
    --cc=stybla@turnovfree.net \
    --cc=thomas@holzeisen.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.