mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "V. Ananda Krishnan" <mansarov@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: rmk+lkml@arm.linux.org.uk, gregkh@suse.de
Subject: uart_port structure in serial8250_port[i]  doesn't have the port_type values
Date: Mon, 15 Aug 2005 09:10:56 -0500	[thread overview]
Message-ID: <1124115056.3694.27.camel@siliver.austin.ibm.com> (raw)

Hi,

  The problem described here is related to the 8250_pci driver in
2.6.12.3/2.6.12.4 kernels. When 8250_pci device driver detects a serial
port pci device and sets up the default setup (8250_pci.c), it tries to
find a match or unused port (serial8250_find_match_or_unused proc in in
8250.c). This leads to the uart_match_port with one of the parameters as
serial8250_ports[i].port. During debugging, I noticed that the none of
elements of the serial8250_ports[i].port.type was having any port value.
So the serial8250_register_port fails and the device driver module fails
to load. In this scenario, the last resort to find any entry which
doesn't have a real port associated with it also fails, because of the
null value in the serial8250_ports[i].port.type.  I would like to know
when the port.type values in uart_8250_port strucutre (in
serial8250_ports[i]) is populated? Is there anything missing in the
serial8250_find_match_or_unused codes?  Any help to degug this problem
is appreciated. Thanks.

V.Ananda Krishnan



             reply	other threads:[~2005-08-15 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 14:10 V. Ananda Krishnan [this message]
2005-08-15 14:52 ` Russell King
2005-08-15 15:56   ` V. Ananda Krishnan
2005-08-15 16:11     ` Russell King
2005-08-15 16:33       ` V. Ananda Krishnan
2005-08-15 16:41         ` Russell King
2005-08-15 16:46           ` V. Ananda Krishnan
2005-08-15 17:14           ` V. Ananda Krishnan

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=1124115056.3694.27.camel@siliver.austin.ibm.com \
    --to=mansarov@us.ibm.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@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 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®