From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Daiane Angolini <daiane.angolini@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [RFC] default u-boot
Date: Thu, 10 Oct 2013 09:31:33 -0700 [thread overview]
Message-ID: <5256D665.1020702@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKo7TPRJaQEeps5Uwart-ABai6UHfY4AZb5A15jk9vsxwA@mail.gmail.com>
Hi all,
On 10/10/2013 09:28 AM, Otavio Salvador wrote:
> On Thu, Oct 10, 2013 at 1:12 PM, Daiane Angolini
> <daiane.angolini@freescale.com> wrote:
>> On 10/10/2013 11:26 AM, Eric Nelson wrote:
>>>> u-boot-fslc is our recipe that points to "trye main-line U-Boot". It's
>>>> hosted on github only to keep some needed backport patches.
>>>>
>>>
>>> IOW, the same thing we use ours for. If it makes things easier, we could
>>> push a 'boundary' branch there when we update things.
>>
>>
>> <3
>>
>> I think it would be perfect =D
>> (if not for Dora, absolutely for 1.6)
>>
>> Otavio, what do you think?
>
> I am not sure; I think the u-boot-boundary gives the clear notion it
> is something done by Bondary. If we'd use u-boot-fslc we'd need to
> have the changes in same branch as used by other boards or it loses
> its meaning.
>
> My goal with u-boot-fslc is to have a /single/ u-boot for most boards;
> so it is essentially U-Boot mainline plus bugfixes; supporting
> multiple branches for different boards I think it will confuse people.
>
> It seems the best would be if, instead of pushing to our u-boot GIT,
> it had regular updates in the u-boot-boundary recipes and point to
> newer revisions.
>
We'll make sure to update with each switch in our production branch.
Regards,
Eric
next prev parent reply other threads:[~2013-10-10 16:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 0:28 [RFC] default u-boot Daiane Angolini
2013-10-10 1:59 ` Eric Nelson
2013-10-10 12:47 ` Daiane Angolini
2013-10-10 14:26 ` Eric Nelson
2013-10-10 16:12 ` Daiane Angolini
2013-10-10 16:28 ` Otavio Salvador
2013-10-10 16:31 ` Eric Nelson [this message]
2013-10-10 17:44 ` Otavio Salvador
2013-10-10 19:10 ` Eric Nelson
2013-10-10 19:10 ` Daiane Angolini
2013-10-10 19:35 ` Eric Nelson
2013-10-11 11:27 ` Daiane Angolini
2013-10-10 19:16 ` Otavio Salvador
2013-10-10 19:18 ` Daiane Angolini
2013-10-10 19:38 ` Eric Nelson
2013-10-10 16:32 ` Dmitriy B.
2013-10-10 17:56 ` Daiane Angolini
2013-10-10 19:02 ` Haakon Stende
2013-10-10 19:08 ` Otavio Salvador
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=5256D665.1020702@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.