linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linuxppc-embedded@lists.linuxppc.org
Subject: Serial core problems on embedded PPC
Date: Mon, 29 Jul 2002 14:08:24 +1000	[thread overview]
Message-ID: <20020729040824.GA2351@zax> (raw)


I've been trying to get the new serial core stuff working on a PPC 4xx
machine (an EP405 board, specifically).  This is proving more
difficult than I expected.

In 8250.c, it appears that in order for a port to be used for the
serial console it must be defined "old style" with SERIAL_PORT_DFNS,
rather than being registered with register_serial() (because
serial8250_console_setup() indexs into the serial8250_ports array)).
This presents a small problem for 4xx, since it's serial ports are
memory mapped and the new old_serial_port structure can't represent
these.  I added support for these into 8250.c, but ran into further
troubles.

The kernel now gets into an infinite loop when trying to open
/dev/console in init().  The loop is occuring in tty_open() - the open
fails and it loops back to the retry_open: label.  This seems to be
happening because the uart_port structure is ending up with the type
field set to PORT_UNKNOWN.  However, I'm getting confused attempting
to work out where this field ought to be set, and why it isn't.

The current plethora of similar-but-not-the-same structures describing
serial ports (serial_state, serial_struct, uart_port, old_serial_port)
is also rather confusing.  I'm guessing some of these are deprecated
and remain only as an aid to transition, but I'm not sure which.

--
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-07-29  4:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29  4:08 David Gibson [this message]
2002-07-29  9:00 ` Serial core problems on embedded PPC Russell King
2002-07-29 14:44   ` Tom Rini
2002-07-29 17:17     ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Russell King
2002-07-29 17:43       ` Tom Rini
2002-07-29 18:13         ` Benjamin Herrenschmidt
2002-07-29 19:07           ` Tom Rini
2002-07-29 19:09           ` 3 Serial issues up for discussion (was: " Dan Malek
2002-07-29 19:46             ` Remco Treffkorn
2002-07-29 20:18               ` Russell King
2002-07-30  2:54               ` 3 Serial issues up for discussion David S. Miller
2002-07-29 18:15         ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Matt Porter
2002-07-29 17:47       ` [parisc-linux] " Christoph Plattner
2002-07-29 22:19       ` Matthew Wilcox
2002-07-30  2:51       ` 3 Serial issues up for discussion David S. Miller
2002-08-02  6:01     ` symbol card with orinoco_cs on mpc823 shaowei dai
2002-08-02  6:23       ` David Gibson
2002-08-02  6:36         ` Matthew Locke
2002-08-02  7:01           ` shaowei dai
     [not found]       ` <3D4AC468.83BCD667@opensource.se>
2002-08-03  1:30         ` shaowei dai
2002-07-30  1:12   ` Serial core problems on embedded PPC David Gibson

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=20020729040824.GA2351@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).