From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH] powerpc/bootwrapper: Allow user to specify additional default targets
Date: Mon, 7 Jul 2008 08:29:47 -0600 [thread overview]
Message-ID: <fa686aa40807070729w524aa50xb1c762f13ba31da1@mail.gmail.com> (raw)
In-Reply-To: <20080707100704.26f1630c@zod.rchland.ibm.com>
On Mon, Jul 7, 2008 at 8:07 AM, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> On Mon, 7 Jul 2008 07:34:23 -0600 Grant Likely wrote:
>> Specifically the case I'm thinking of is when a user of a Xilinx FPGA
>> drops a new .dts file into arch/powerpc/boot/dts (say
>> 'super-sexy-platform.dts'). However, instead of modifying the
>> Makefile or always typing 'make simpleImage.super-sexy-platform', then
>> can add 'simpleImage.super-sexy-platform' to their defconfig which I
>> can see being easier for someone to get their head around.
>
> Yeah, I thought about the Virtex case with the differing bitstreams
> after I sent out my original question. For purposes like that, this
> seems like a great fit. For truly discrete boards, I prefer discrete
> defconfigs.
>
> So overall I see value in the patch. If nobody else has objections,
> then it's fine with me.
so.... can I have an ack? :-)
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-07-07 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 17:59 [RFC/PATCH] powerpc/bootwrapper: Allow user to specify additional default targets Grant Likely
2008-07-04 6:51 ` Grant Likely
2008-07-07 13:18 ` Josh Boyer
2008-07-07 13:34 ` Grant Likely
2008-07-07 14:07 ` Josh Boyer
2008-07-07 14:29 ` Grant Likely [this message]
2008-07-09 14:00 ` Josh Boyer
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=fa686aa40807070729w524aa50xb1c762f13ba31da1@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=jwboyer@linux.vnet.ibm.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).