public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Adam Belay <ambx1@neo.rr.com>, Jaroslav Kysela <perex@perex.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"greg@kroah.com" <greg@kroah.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: PnP model
Date: Tue, 4 Feb 2003 09:46:34 +0000	[thread overview]
Message-ID: <20030204094634.A11346@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030203204325.GA7425@neo.rr.com>; from ambx1@neo.rr.com on Mon, Feb 03, 2003 at 08:43:25PM +0000

On Mon, Feb 03, 2003 at 08:43:25PM +0000, Adam Belay wrote:
> In many cases, Auto configuration can be better then manual configuration.
> 1.) The auto configuration engine in my patch is able to resolve almost any
> resource conflict and provides the greatest chance for all devices to have
> resources allocated.

There is a nice problem with ISA PNP serial ports generated by this
type of thing in 2.5.59.

On boot, we probe for the usual serial ports, and discover two at
0x3f8 and 0x2f8, and we request these resources.  Please note that
one port could be in use as a serial console from earlier in the
bootup.

Then, we move on to the PNP probes.  The PNP layer gives us two
serial ports, and we initialise them.  The PNP layer notices that
the resources for 0x3f8 and 0x2f8, and re-assigns the ports to
0x3e8 and 0x2e8.  The serial layer finds two extra ports at
0x3e8 and 0x2e8.

However, the ports at 0x3f8 and 0x2f8 are now gone, along with the
serial console, and the boot messages claim that we have four serial
ports at ttyS0, ttyS1, ttyS2, and ttyS3, when the machine in fact
only has two serial ports.  The serial layer likewise believes we
have four serial ports.

I look forward to your thoughts on getting around this problem.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-02-04  9:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 20:36 [PATCH][RFC] Resource Management Improvements (1/4) Adam Belay
2003-02-03  9:33 ` Jaroslav Kysela
2003-02-03  9:44 ` Jaroslav Kysela
2003-02-03 13:55 ` PnP model Jaroslav Kysela
2003-02-03 15:45   ` Alan Cox
2003-02-03 20:43   ` Adam Belay
2003-02-04  9:46     ` Russell King [this message]
2003-02-04 10:18       ` Jaroslav Kysela
2003-02-04 10:49         ` Russell King
2003-02-05 21:34           ` Adam Belay
2003-02-07  8:56             ` Jaroslav Kysela
2003-02-04 10:40     ` Jaroslav Kysela
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 15:31 PnP Model James Bottomley
2003-02-03 16:41 ` Alan Cox
2003-02-04 16:45   ` James Bottomley
2003-02-04 19:25 PnP model Grover, Andrew
2003-02-04 19:40 ` John Bradford
2003-02-04 19:53 Grover, Andrew
2003-02-04 22:56 ` Alan Cox
2003-02-06 18:49 ` Adam Belay

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=20030204094634.A11346@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ambx1@neo.rr.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    /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