From: "Mark A. Greer" <mgreer@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 5/6] bootwrapper: Add support for the DINK firmware
Date: Wed, 2 Aug 2006 11:31:42 -0700 [thread overview]
Message-ID: <20060802183142.GK17652@mag.az.mvista.com> (raw)
In-Reply-To: <20060802181514.GO3075@smtp.west.cox.net>
On Wed, Aug 02, 2006 at 11:15:14AM -0700, Tom Rini wrote:
> On Wed, Aug 02, 2006 at 11:14:22AM -0700, Mark A. Greer wrote:
> > On Wed, Aug 02, 2006 at 09:19:34AM -0700, Tom Rini wrote:
> > > On Wed, Jul 19, 2006 at 04:14:21PM -0700, Mark A. Greer wrote:
> > >
> > > > This patch adds the firmware operations that support the DINK firmware
> > > > from Freescale.
> > >
> > > This isn't really DINK support (which would mean actually talking
> > > back/with DINK,
> >
> > You seem to be thinking that this is the final, end-all solution to
> > everything. It isn't. Its a step in the direction that we are trying
> > go (IIUC). dink.c is about the easiest one there will be. of.c has a
> > slightly more complicated fw_ops. We still need to figure out what uboot
> > needs and what PIBS needs and what...
>
> Right. I'm just saying that unless you're planning on making this talk
> with / use DINK (I swear, the DINK manual talks about this a bit, but
> I'm too lazy to look just this second), this isn't the DINK one, this is
> the (will be needed and used) bare metal one.
Ah, okay. Sure.
next prev parent reply other threads:[~2006-08-02 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 23:14 [PATCH 5/6] bootwrapper: Add support for the DINK firmware Mark A. Greer
2006-07-19 23:33 ` Mark A. Greer
2006-08-02 16:19 ` Tom Rini
2006-08-02 18:14 ` Mark A. Greer
2006-08-02 18:15 ` Tom Rini
2006-08-02 18:31 ` Mark A. Greer [this message]
2006-09-08 3:40 ` [PATCH 5/6] bootwrapper: Add simple memory allocator 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=20060802183142.GK17652@mag.az.mvista.com \
--to=mgreer@mvista.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).