From: Peter Stuge <stuge-linux-pcmcia@cdy.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
Samuel Ortiz <samuel@sortiz.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org,
"Linus Walleij \(LD/EAB\)" <linus.walleij@ericsson.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip
Date: Mon, 13 Aug 2007 19:39:06 +0200 [thread overview]
Message-ID: <20070813173906.14407.qmail@cdy.org> (raw)
In-Reply-To: <200708131009.46641.bjorn.helgaas@hp.com>
On Mon, Aug 13, 2007 at 10:09:46AM -0600, Bjorn Helgaas wrote:
> > [ 2207.986873] smsc_ircc_present: can't get sir_base of 0x2e8
>
> As of 2.6.23-rc2, we should have:
> - probes for 8250 legacy devices (as in 2.6.21 and previous)
> - smsc PNP probes turned off by default (2.6.21 and previous had
> no PNP probes for smsc at all)
> - some complicated PNP quirks for SMCf010 devices
>
> In other words, I think we're basically back where we started. The
> 8250 driver should find a ttyS3 device at 0x2e8, and it should
> claim those ports, which will prevent smsc from claiming them.
I use 8250.nr_uarts=1 appended to my kernel parameters on my laptop.
Perfectly reliable workaround, but if it is possible to detect, then
all the better!
//Peter
next prev parent reply other threads:[~2007-08-13 17:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 8:00 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip Andrey Borzenkov
2007-06-03 8:16 ` Andrey Borzenkov
2007-06-03 23:10 ` Samuel Ortiz
2007-06-04 2:33 ` Andrey Borzenkov
2007-06-04 20:44 ` Samuel Ortiz
2007-06-05 3:10 ` Andrey Borzenkov
2007-06-05 7:18 ` Linus Walleij (LD/EAB)
2007-06-05 7:57 ` Samuel Ortiz
2007-06-05 11:57 ` Linus Walleij (LD/EAB)
2007-06-05 13:04 ` Samuel Ortiz
2007-06-05 23:23 ` Bjorn Helgaas
2007-06-06 3:29 ` Andrey Borzenkov
2007-06-06 19:09 ` Bjorn Helgaas
2007-06-06 20:45 ` Andrey Borzenkov
2007-06-07 15:52 ` Bjorn Helgaas
2007-06-07 20:47 ` Samuel Ortiz
2007-06-10 6:47 ` Andrey Borzenkov
2007-06-10 21:03 ` Bjorn Helgaas
2007-06-11 14:04 ` Andrey Borzenkov
2007-06-14 21:30 ` Bjorn Helgaas
2007-06-15 13:44 ` Andrey Borzenkov
2007-06-15 15:19 ` Bjorn Helgaas
2007-06-16 16:38 ` Andrey Borzenkov
2007-06-19 23:31 ` Bjorn Helgaas
2007-06-28 3:56 ` Bjorn Helgaas
2007-06-30 2:41 ` Bjorn Helgaas
2007-06-30 7:16 ` Andrey Borzenkov
2007-06-30 11:45 ` Bjorn Helgaas
2007-06-30 14:47 ` Andrey Borzenkov
2007-06-30 21:13 ` Andrey Borzenkov
2007-07-01 3:30 ` Bjorn Helgaas
2007-07-01 7:08 ` Andrey Borzenkov
2007-07-01 13:57 ` Bjorn Helgaas
2007-08-11 18:39 ` Andrey Borzenkov
2007-08-13 16:09 ` Bjorn Helgaas
2007-08-13 17:39 ` Peter Stuge [this message]
2007-08-18 6:59 ` Andrey Borzenkov
2007-07-01 0:01 ` Michal Piotrowski
2007-07-01 0:04 ` Michal Piotrowski
2007-06-07 18:34 ` Bjorn Helgaas
2007-06-08 5:24 ` Andrey Borzenkov
2007-06-10 8:03 ` Andrey Borzenkov
2007-06-10 20:04 ` Bjorn Helgaas
2007-06-07 12:23 ` Linus Walleij (LD/EAB)
2007-06-07 15:44 ` Bjorn Helgaas
2007-06-05 12:06 ` Linus Walleij (LD/EAB)
2007-06-04 16:34 ` Bjorn Helgaas
2007-06-05 3:08 ` Andrey Borzenkov
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=20070813173906.14407.qmail@cdy.org \
--to=stuge-linux-pcmcia@cdy.org \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=bjorn.helgaas@hp.com \
--cc=linus.walleij@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=samuel@sortiz.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 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.