From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "V. ANANDA KRISHNAN" <mansarov@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: Serial core: 8250_pci could not register serial port for UART chip EXAR XR17D152
Date: Sat, 16 Jul 2005 09:38:58 +0100 [thread overview]
Message-ID: <20050716093858.A19067@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1121359649.15007.18.camel@siliver.austin.ibm.com>; from mansarov@us.ibm.com on Thu, Jul 14, 2005 at 11:47:29AM -0500
On Thu, Jul 14, 2005 at 11:47:29AM -0500, V. ANANDA KRISHNAN wrote:
> I have been coming across a problem with my serial port EXAR chip XR
> 17D152, when I try to use the 8250_pci driver. I am using
> kernel-2.6.12.1 on RHEL4.0-U1 on pSeries box with 4-cpu. 8250_pci
> during the boot time, after detecting the exar chip (I checked with the
> pci_dev structure and the pci_device_id structure for the info), is
> unable to get thru the port registration (static int
> __devinit_pciserial_init_one(struct pci_dev *dev, const struct
> pci_device_id *ent) procedure in 8250_pci.c). I debugged the problem
> and traced upto the routine "static int uart_match_port(struct uart_port
> *port1, struct uart_port *port2" in 8250.c where UPIO_MEM is not
> satisfying the condition port1->membase==port2->membase and hence
> returns 0.
That's the intended result. uart_match_port() only returns true when
the types of the two ports match, and the base address of the two ports
also match.
Please try mainline 2.6 kernels. Also, please include the kernel entire
messages when reporting bugs.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2005-07-16 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 16:47 Serial core: 8250_pci could not register serial port for UART chip EXAR XR17D152 V. ANANDA KRISHNAN
2005-07-16 8:38 ` 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=20050716093858.A19067@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mansarov@us.ibm.com \
/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