From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Daiane Angolini <daiane.angolini@freescale.com>,
Daiane Angolini <daiane.list@gmail.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: [RFC] default u-boot
Date: Thu, 10 Oct 2013 07:26:09 -0700 [thread overview]
Message-ID: <5256B901.9010706@boundarydevices.com> (raw)
In-Reply-To: <5256A1E3.5070002@freescale.com>
Hi Daiane,
On 10/10/2013 05:47 AM, Daiane Angolini wrote:
> On 10/09/2013 10:59 PM, Eric Nelson wrote:
>> On 10/09/2013 05:28 PM, Daiane Angolini wrote:
>>
>> <snip>
>>
>>> Is the default version for nitrogen and sabrelite (u-boot-boundary)
>>> 2013.01?
>>>
>> No. The current release of u-boot-boundary is 2013.07:
>> http://boundarydevices.com/u-boot-2013-07-release/
>
> Thanks, I changed the docs already.
>
>>
>> The sources are in our Github repository (production branch is
>> what we're currently shipping with boards);
>> https://github.com/boundarydevices/u-boot-imx6/tree/production
>>
>> We try to keep this in-line with true main-line U-Boot, but use
>> it as a staging area so we can be a bit more responsive to customer
>> needs. The primary deltas at this point are additional boards
>> (nit6xlite is not yet in main-line), support for additional
>> displays, and support for custom boards.
>
> I used your last sentence to make a description. Please, take a look on
> https://github.com/Freescale/Documentation/blob/master/release-notes/source/u-boot.rst
>
> And let me know if you want to change anything.
>
This looks good. Thanks.
>>
>>> I would like to know what's the plan to add both support on u-boot-fslc
>>>
>> I have to admit that I've never looked at u-boot-fslc. I thought it was
>> only used for PPC boards.
>
> 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.
Regards,
Eric
next prev parent reply other threads:[~2013-10-10 14:26 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 [this message]
2013-10-10 16:12 ` Daiane Angolini
2013-10-10 16:28 ` Otavio Salvador
2013-10-10 16:31 ` Eric Nelson
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=5256B901.9010706@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=daiane.angolini@freescale.com \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.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 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.