mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Kronos <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.49] Serial registered twice
Date: Sun, 24 Nov 2002 18:07:20 +0000	[thread overview]
Message-ID: <20021124180720.A30521@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20021124153842.GA586@dreamland.darkstar.lan>; from kronos@kronoz.cjb.net on Sun, Nov 24, 2002 at 04:38:42PM +0100

On Sun, Nov 24, 2002 at 04:38:42PM +0100, Kronos wrote:
> In my bootlog I see this:
> 
> Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing enabled
> tts/0 at I/O 0x3f8 (irq = 4) is a 16550A
> tts/1 at I/O 0x2f8 (irq = 3) is a 16550A
> pnp: the driver 'serial' has been registered
> pnp: pnp: match found with the PnP device '00:0c' and the driver 'serial'
> devfs_register(tts/0): could not append to parent, err: -17
> tts/0 at I/O 0x3f8 (irq = 4) is a 16550A
> pnp: pnp: match found with the PnP device '00:10' and the driver 'serial'
> devfs_register(tts/1): could not append to parent, err: -17
> tts/1 at I/O 0x2f8 (irq = 3) is a 16550A

Indeed.  Although it is harmless, it isn't what the average user
expects.  I could tweak the serial layer to refuse to re-initialise
an already initalised port.

However, the devfs_regsiter problem is one that needs solving.

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


      reply	other threads:[~2002-11-24 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24 15:38 Kronos
2002-11-24 18:07 ` Russell King [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=20021124180720.A30521@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®