linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 4/6] bootwrapper: Add non-OF serial console support
Date: Wed, 2 Aug 2006 09:17:12 -0700	[thread overview]
Message-ID: <20060802161712.GH3075@smtp.west.cox.net> (raw)
In-Reply-To: <20060719231244.GE3887@mag.az.mvista.com>

On Wed, Jul 19, 2006 at 04:12:44PM -0700, Mark A. Greer wrote:

> This patch adds support for serial I/O to the bootwrapper.
> 
> It is broken into 2 layers.  The first layer is generic serial
> operations that calls uart-specific routines to do the actual I/O.
> The second layer contains support for a 16550 compatible uart.
> 
> The division allows support for other serial devices to be easily
> added in the future (e.g., the Marvell MPSC and the Freescale CPM).

Why do we do this with indirection rather than weak defaults and then
real implementations?  The only places I see that are data are:

> +	ns16550_scd.base = NULL;
> +	ns16550_scd.reg_shift = 0;

And I imagine that on platforms where these are real, we dig them out of
the tree and set them, in your scheme, so it'd just be an empty (return
0/NULL) weak function, or the dig in the tree function.  Heck, it could
just always be a 'dig in the tree' function.

-- 
Tom Rini

  reply	other threads:[~2006-08-02 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 23:12 [PATCH 4/6] bootwrapper: Add non-OF serial console support Mark A. Greer
2006-08-02 16:17 ` Tom Rini [this message]
2006-08-02 17:54   ` Mark A. Greer
2006-09-08  3:39 ` Mark A. Greer

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=20060802161712.GH3075@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.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;
as well as URLs for NNTP newsgroup(s).