From: Grant Likely <grant.likely@secretlab.ca>
To: Eddie Dawydiuk <eddie@embeddedarm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH, RFC]
Date: Fri, 6 Mar 2009 22:41:15 -0700 [thread overview]
Message-ID: <fa686aa40903062141n210f81d7g9f11154f3c78cadc@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40903062022i2211ccdfu1bffab54749615d8@mail.gmail.com>
On Fri, Mar 6, 2009 at 9:22 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Mar 6, 2009 at 3:32 PM, Eddie Dawydiuk <eddie@embeddedarm.com> wrote:
>> Hello,
>>
>> Let's try this one more time. The last patch was using the clocks for a
>> custom board based on the Yosemite board and was referencing a non-existent
>> ethNadr( I forgot to pull out this code out).
>
> But the question remains: Why do you need simpleboot support for
> Yosemite when you can use a uImage or cuImage with u-boot?
On a more general note; this patch also diverges from the original
model for simple image. The idea behind simpleimage was that it would
contain a fully formed device tree, with no fixups necessary. I want
to think carefully before diverging from that.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-03-07 5:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 17:41 [PATCH, RFC] Eddie Dawydiuk
2009-03-06 18:40 ` Josh Boyer
2009-03-06 19:45 ` Grant Likely
2009-03-06 21:51 ` Eddie Dawydiuk
2009-03-06 22:32 ` Eddie Dawydiuk
2009-03-07 4:22 ` Grant Likely
2009-03-07 5:41 ` Grant Likely [this message]
2009-03-07 15:21 ` Eddie Dawydiuk
2009-03-07 16:04 ` Grant Likely
2009-03-07 15:14 ` Eddie Dawydiuk
2009-03-07 16:06 ` Grant Likely
2009-03-08 19:20 ` Sean MacLennan
-- strict thread matches above, loose matches on Subject: below --
2009-03-07 16:37 Eddie Dawydiuk
2009-03-08 7:35 ` Grant Likely
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=fa686aa40903062141n210f81d7g9f11154f3c78cadc@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=eddie@embeddedarm.com \
--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).