From: "David Härdeman" <david@hardeman.nu>
To: Sean Young <sean@mess.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Jarod Wilson <jarod@wilsonet.com>,
Alan Cox <alan@linux.intel.com>,
linux-media@vger.kernel.org, linux-serial@vger.kernel.org,
lirc-list@lists.sourceforge.net, greg@kroah.com
Subject: Re: [PATCH] [media] winbond-cir: Fix initialization
Date: Sun, 19 Aug 2012 00:46:21 +0200 [thread overview]
Message-ID: <20120818224621.GD11774@hardeman.nu> (raw)
In-Reply-To: <1343731023-9822-1-git-send-email-sean@mess.org>
On Tue, Jul 31, 2012 at 11:37:03AM +0100, Sean Young wrote:
>The serial driver will detect the winbond cir device as a serial port,
>since it looks exactly like a serial port unless you know what it is
>from the PNP ID.
>
>Winbond CIR 00:04: Region 0x2f8-0x2ff already in use!
>Winbond CIR 00:04: disabled
>Winbond CIR: probe of 00:04 failed with error -16
The proposed solution means that a serial port will show up and then
automagically disappear (potentially) during boot, which isn't very
elegant.
When I discussed this a long time ago with Alan Cox (while he was still
the serial maintainer) I got the feeling that he was advocating
implementing a PNP ID based blacklist in the serial driver (apologies to
Alan if I misrepresented him now).
That seems to be a better solution (one that I never got around to
implementing myself).
>
>Signed-off-by: Sean Young <sean@mess.org>
>---
> drivers/media/rc/winbond-cir.c | 21 ++++++++++++++++++++-
> drivers/tty/serial/8250/8250.c | 1 +
> 2 files changed, 21 insertions(+), 1 deletion(-)
(BTW, I'm on vacation with sporadic Internet access for two more weeks,
and when I return I'll be spending most of my spare time moving in to a
new apartment, expect slow turnaround times for replying to emails).
prev parent reply other threads:[~2012-08-18 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 10:37 [PATCH] [media] winbond-cir: Fix initialization Sean Young
2012-08-11 20:20 ` Mauro Carvalho Chehab
2012-08-19 16:00 ` Alan Cox
2012-08-16 16:19 ` Greg KH
2012-08-16 21:16 ` Sean Young
2012-08-18 22:46 ` David Härdeman [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=20120818224621.GD11774@hardeman.nu \
--to=david@hardeman.nu \
--cc=alan@linux.intel.com \
--cc=greg@kroah.com \
--cc=jarod@wilsonet.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
--cc=mchehab@redhat.com \
--cc=sean@mess.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).