From: Jean Delvare <khali@linux-fr.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Mike Isely <isely@pobox.com>,
isely@isely.net, LMML <linux-media@vger.kernel.org>,
Andy Walls <awalls@radix.net>, Hans Verkuil <hverkuil@xs4all.nl>,
Janne Grunau <j@jannau.net>, Jarod Wilson <jarod@redhat.com>
Subject: Re: [RFC] Anticipating lirc breakage
Date: Tue, 7 Apr 2009 14:36:17 +0200 [thread overview]
Message-ID: <20090407143617.2c2adbf7@hyperion.delvare> (raw)
In-Reply-To: <20090407075029.21d14f4a@pedra.chehab.org>
Hi Mauro,
On Tue, 7 Apr 2009 07:50:29 -0300, Mauro Carvalho Chehab wrote:
> On Tue, 7 Apr 2009 12:02:09 +0200
> Jean Delvare <khali@linux-fr.org> wrote:
>
> > Hi Mike,
> >
> > Glad to see we all mostly agree on what to do now. I'll still answer
> > some of your questions below, to clarify things even more.
>
> I don't understand why you are preferring to do some workaround, spending
> energy to add hooks at the kernel drivers to support out-of-tree drivers,
> instead of working to provide the proper solution.
What I am proposing isn't a workaround, it is a fundamental part of
the solution, and it is even the approach which requires the minimum
amount of changes. This is as straightforward a solution as you can
hope for.
> I'm against adding any hook on kernel to support an out-of-tree driver.
I do not plan to add any hook. The plan is to instantiate all IR
devices we know are present, and let ir-kbd-i2c bind to the ones it
supports. The fact that another out-of-tree driver may optionally bind
to these devices is a side effect.
I would love to say "let's just ignore lirc altogether", however 1* I
don't think it makes any sense to break user systems when it is trivial
for us to not break them and 2* I don't think it is smart to be rude
with lirc developers are the exact moment they decide to attempt to
merge their drivers in the kernel tree.
> From what I understood, lirc developers are interested on merging lirc drivers.
> We all agree that ir-kbd-i2c doesn't address all i2c IR's, and that lirc
> drivers provide support for the remaining ones.
Yes, this is my understanding as well.
> So, let's just forget the workarounds and go straight to the point: focus on
> merging lirc-i2c drivers.
Will this happen next week? I fear not. Which is why I can't wait for
it. And anyway, in order to merge the lirc_i2c driver, it must be
turned into a new-style I2C driver first, so bridge drivers must be
prepared for this, which is _exactly_ what my patches are doing.
--
Jean Delvare
next prev parent reply other threads:[~2009-04-07 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 15:44 [RFC] Anticipating lirc breakage Jean Delvare
2009-04-07 1:20 ` Andy Walls
2009-04-07 3:15 ` hermann pitton
2009-04-07 9:08 ` Jean Delvare
2009-04-07 2:30 ` Mauro Carvalho Chehab
2009-04-07 6:19 ` Mike Isely
2009-04-07 10:02 ` Jean Delvare
2009-04-07 10:50 ` Mauro Carvalho Chehab
2009-04-07 12:36 ` Jean Delvare [this message]
2009-07-09 15:44 ` Jarod Wilson
2009-07-09 15:52 ` Devin Heitmueller
2009-07-09 16:08 ` Jean Delvare
2009-04-08 17:22 ` Mike Isely
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=20090407143617.2c2adbf7@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=isely@isely.net \
--cc=isely@pobox.com \
--cc=j@jannau.net \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--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