From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>, david@gibson.dropbear.id.au
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PowerPC: Fix find_legacy_serial_ports on OPB.
Date: Thu, 11 Oct 2007 10:53:48 -0500 [thread overview]
Message-ID: <1192118028.5534.123.camel@localhost.localdomain> (raw)
In-Reply-To: <200710111750.41852.arnd@arndb.de>
On Thu, 2007-10-11 at 17:50 +0200, Arnd Bergmann wrote:
> On Thursday 11 October 2007, Valentine Barshak wrote:
> > Currently find_legacy_serial_ports() can find no serial ports on the OPB.
> > Thus no legacy boot console can be initialized. Just the early udbg console
> > works, which is initialized with udbg_init_44x_as1() on the UART's physical
> > address specified in kernel config. This happens because we look for ns16750
> > and higher serial devices only and expect opb node to have a device type
> > property. This patch makes it look for ns16550 compatible devices and use
> > of_device_is_compatible() for opb instead of checking device type.
> > Lack of legacy serial ports found causes problems for KGDB over serial.
> >
> > Signed-off-by: Valentine Barshak <vbarshak@ru.mvista.com>
>
> The patch would make sense if we were only dealing with flattened device
> tree systems at this point. Unfortunately, IBM is shipping hardware that
> encodes the serial port in exactly the way that find_legacy_serial_ports
> is looking for (parent->type == "opb", compatible = "ns16750" "ns16550"
> "ns16450" i8250").
>
> Changing the search for ns16750 to ns16550 should be fine, but unnecessary
> because AFAIK, all OPB serial imlpementations are actually ns16750 and
> should have that in the device tree as well.
>
> For the device type of the bus, please check for both compatible and
> type, so that it still works on machines that are missing the compatible
> property.
Wait, no. We already had this discussion months ago when David was
working on the original Ebony port. It was declared that legacy_serial
is not how serial should be done on 4xx and the serial_of driver was
supposed to be used instead.
Have we changed our stance on that? If not, then perhaps KGDB should be
fixed to work with serial_of.
josh
next prev parent reply other threads:[~2007-10-11 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 15:26 [PATCH] PowerPC: Fix find_legacy_serial_ports on OPB Valentine Barshak
2007-10-11 15:50 ` Arnd Bergmann
2007-10-11 15:53 ` Josh Boyer [this message]
2007-10-11 17:09 ` Arnd Bergmann
2007-10-11 19:09 ` [PATCH] PowerPC: Add legacy serial support for OPB with flattened device tree Valentine Barshak
2007-10-11 21:10 ` Arnd Bergmann
2007-10-11 17:26 ` [PATCH] PowerPC: Fix find_legacy_serial_ports on OPB Valentine Barshak
2007-10-11 18:31 ` Josh Boyer
2007-10-12 2:31 ` David Gibson
2007-10-12 11:49 ` Josh Boyer
2007-10-11 18:49 ` Valentine Barshak
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=1192118028.5534.123.camel@localhost.localdomain \
--to=jwboyer@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.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 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.