All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@as2917.net>
To: "'Russell King'" <rmk@arm.linux.org.uk>
Cc: "'Ruud Linders'" <rkmp@xs4all.nl>, <linux-kernel@vger.kernel.org>
Subject: Re: Serial port numbering (ttyS..) wrong for 2.5.61+
Date: Mon, 2 Jun 2003 20:43:24 +0200	[thread overview]
Message-ID: <011501c32936$d8fc44d0$3f00a8c0@witbe> (raw)
In-Reply-To: <20030602185118.B776@flint.arm.linux.org.uk>

Hello,


> When we add a port to the system, we try to find in order:
> 
> - a port which matches the base address
> - a port which is unallocated
> 
> Probably the easiest way to stop the "ttyS14" occuring would 
> be to clear the port information at boot when we don't find a port.
> 
>From 8250_pci.c, you have :

/*              
 * Probe one serial board.  Unfortunately, there is no rhyme nor reason
 * to the arrangement of serial ports on a PCI card.
 */             

It seems that your board is reporting the parameters in such an order
that when looking for a port based on the IRQ, I/O port, ... the matching
one has id 14...

You could see this more clearly by setting SERIAL_DEBUG_PCI
at line 1549 to activate the code :
#ifdef SERIAL_DEBUG_PCI
                printk("Setup PCI port: port %x, irq %d, type %d\n",
                       serial_req.port, serial_req.irq, serial_req.io_type);
#endif

that would report to you the order in which ports are found on
your system.

Regards,
Paul



  reply	other threads:[~2003-06-02 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-01 11:14 Serial port numbering (ttyS..) wrong for 2.5.61+ Ruud Linders
2003-06-01 12:48 ` Paul Rolland
2003-06-02 17:51   ` Russell King
2003-06-02 18:43     ` Paul Rolland [this message]
2003-06-03 16:58       ` Ruud Linders
  -- strict thread matches above, loose matches on Subject: below --
2003-06-02 16:21 Ruud Linders

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='011501c32936$d8fc44d0$3f00a8c0@witbe' \
    --to=rol@as2917.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkmp@xs4all.nl \
    --cc=rmk@arm.linux.org.uk \
    /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.