From: Milton Miller <miltonm@bga.com>
To: Milton Miller <miltonm@bga.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: udbg_16550.c and legacy_serial.c
Date: Wed, 27 Jun 2007 06:29:26 -0500 [thread overview]
Message-ID: <64edb4cfb6f38bd6e1d7de64bbbebae6@bga.com> (raw)
In-Reply-To: <d8960a6c86859c19b84dc9fd41446fbd@bga.com>
On Jun 27, 2007, at 6:22 AM, Milton Miller wrote:
> (4) Adding a 5th udbg_putc method that calls a byte read to
> udbg_comport->lsr masked with THRE until 0 and performs a byte write
> to ->thr shows we have the wrong abstraction. Please make the
> inb/outb a method with the comport. It would seem the actual init_xx
> could be in the platforms, passing inb, outb, and comport to a helper
> in udbg_16550.c. I'm fine with declaring all the early inits in
> udbg.h
>
I'll repost that with a different subject in case someone else wants to
work on that.
Also, while researching this, I found that check_legacy_serial_console
has a check for legacy_serial_console < 0 in it. Since that is set to
the legacy_ports array we pass to the serial layer, it would seem all
the other parsing to find the console is redundant; we can get the np
that we already found. However, it also means that the code to notice
the stdout path is ch-a or ch-b will never be executed because of that
check.
The comment about stdout being a wierd phandle should read
"/chosen/stdout is a ihandle. use linux,stdout-path instead".
no patch at this hour.
milton
next prev parent reply other threads:[~2007-06-27 11:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 6:53 [PATCH 0/3] PReP support David Gibson
2007-06-27 6:54 ` [PATCH 1/3] Abolish unused ucBoardRev variables David Gibson
2007-06-27 6:54 ` [PATCH 2/3] Make more OF-related bootwrapper functions available to non-OF platforms David Gibson
2007-06-28 8:44 ` Segher Boessenkool
2007-06-27 7:10 ` [PATCH 3/3] First cut at PReP support for arch/powerpc David Gibson
2007-06-27 11:22 ` Milton Miller
2007-06-27 11:29 ` Milton Miller [this message]
2007-06-28 0:38 ` David Gibson
2007-06-28 8:59 ` Segher Boessenkool
2007-06-28 10:00 ` Gabriel Paubert
2007-07-02 11:51 ` Segher Boessenkool
2007-07-03 9:51 ` Gabriel Paubert
2007-07-03 12:49 ` Segher Boessenkool
2007-07-03 2:26 ` Tom Gall
2007-07-03 6:50 ` Ulrich Teichert
2007-08-03 6:35 ` David Gibson
2007-08-03 15:24 ` Jon Loeliger
2007-08-06 19:43 ` Segher Boessenkool
2007-08-06 19:42 ` Segher Boessenkool
2007-07-18 1:31 ` David Gibson
2007-07-18 15:55 ` Segher Boessenkool
2007-08-03 6:43 ` David Gibson
2007-08-06 19:37 ` Segher Boessenkool
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=64edb4cfb6f38bd6e1d7de64bbbebae6@bga.com \
--to=miltonm@bga.com \
--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 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).