From: Tom Rini <trini@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/6] bootwrapper: arch/powerpc/boot code reorg
Date: Wed, 2 Aug 2006 09:03:18 -0700 [thread overview]
Message-ID: <20060802160318.GF3075@smtp.west.cox.net> (raw)
In-Reply-To: <17616.17129.964122.125259@cargo.ozlabs.ibm.com>
On Wed, Aug 02, 2006 at 04:15:05PM +1000, Paul Mackerras wrote:
> I wrote:
>
> > The ops structure seems like a reasonable concept, but I question
> > whether we need to have platform_ops separate from fw_ops, since the
> > firmware is essentially part of the implementation of the platform.
> > Also I don't see why we need to do a double indirection to get to each
> > ops function.
>
> Thinking about this a bit more, why do we need the indirect function
> calls at all? Do we ever want to be able to choose (e.g.) one of
> several possible console implementations at runtime? Don't we know at
> compile time which one we will be using, and thus can't we use the
> linker to make the necessary linkages?
Right. I was thinking perhaps Mark did it this way so certain things
could be omitted (if ops->foo then ops->foo(bar, baz)) but that'd
better taken care of with weak functions and getting the right one at
compile time.
The only potential case, but I'm not even sure then that it is an issue,
is on platforms where it's either U-Boot or PIBS/DINK/whatever. But
even then, the only thing that should matter is 'Do we have a tree
passed in?'.
--
Tom Rini
next prev parent reply other threads:[~2006-08-02 16:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 23:00 [PATCH 1/6] bootwrapper: arch/powerpc/boot code reorg Mark A. Greer
2006-08-02 4:53 ` Paul Mackerras
2006-08-02 6:15 ` Paul Mackerras
2006-08-02 16:03 ` Tom Rini [this message]
2006-08-02 16:58 ` Mark A. Greer
2006-08-03 19:26 ` Mark A. Greer
2006-08-07 6:48 ` Paul Mackerras
2006-08-08 0:15 ` Mark A. Greer
2006-08-02 12:41 ` Arnd Bergmann
2006-08-02 17:00 ` Mark A. Greer
2006-08-02 16:40 ` Mark A. Greer
2006-08-07 0:21 ` Hollis Blanchard
2006-08-08 0:16 ` Mark A. Greer
2006-09-08 3:35 ` Mark A. Greer
2006-09-15 10:19 ` Paul Mackerras
2006-09-15 18:01 ` Mark A. Greer
2006-09-16 4:01 ` Paul Mackerras
2006-09-19 0:45 ` Mark A. Greer
2006-09-19 0:48 ` Mark A. Greer
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 5:57 Milton Miller
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=20060802160318.GF3075@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).