From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: yocto-builds <yocto-builds@yoctoproject.org>,
Denys Dmytriyenko <denys@ti.com>,
"Hart, Darren" <darren.hart@intel.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>,
"WOLD, SAUL" <saul.wold@intel.com>
Subject: Re: meta-yocto-bsp changes and 3.14
Date: Fri, 28 Mar 2014 15:14:08 -0400 [thread overview]
Message-ID: <5335CA00.8070207@windriver.com> (raw)
In-Reply-To: <20140328191218.GO3370@denix.org>
On 14-03-28 03:12 PM, Denys Dmytriyenko wrote:
> On Fri, Mar 28, 2014 at 03:08:54PM -0400, Bruce Ashfield wrote:
>> On 14-03-28 03:05 PM, Hart, Darren wrote:
>>> On 3/28/14, 11:59, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>>>
>>>> On 14-03-28 02:57 PM, Hart, Darren wrote:
>>>>> On 3/28/14, 11:38, "Bruce Ashfield" <bruce.ashfield@windriver.com>
>>>>> wrote:
>>>>>
>>>>>> On 14-03-28 02:34 PM, Richard Purdie wrote:
>>>>>>>
>>>>>>>
>>>>>>> With regard to beagleboard, whilst the kernel may have support for it,
>>>>>>> I'd like to remove it from meta-yocto-bsp.
>>>>>>
>>>>>> ok. I had planned to just leave the compatible machine as 3.10 and
>>>>>> leave
>>>>>> the support there, since there are a few people who contact me
>>>>>> regularly
>>>>>> and poke with the support.
>>>>>>
>>>>>> Is there a place we can put them as a "retirement" home ? versus asking
>>>>>> people to locally restore the support.
>>>>>
>>>>> The retirement home would be the 1.5 stable releases. Yes?
>>>>
>>>> Nope. That's my point, I have 3.10 changes for the Xm in linux-yocto
>>>> 3.10 that lives in 1.6. We can make it less visible, but I'd like the
>>>> configs to follow the latest versions of the tree.
>>>
>>> Isn't it just the SRCREV that matters here? Those can always just be
>>> applied to 1.5. RP is only asking to remove the beagle board as a
>>> reference BSP from the meta-yocto-bsp layer, he doesn't care if the
>>> linux-yocto/meta data remains in place.
>>
>> We are talking past each other. I'm asking for the meta-yocto-bsp and
>> machine conf file to be around .. somewhere .. I don't want people
>> to have to scrounge them up and revive them from old releases, or
>> revert commits to make them available.
>>
>> So this is outside of linux-yocto, I'd like a single layer than when
>> added, gives access to the BSPs "as they were" in the 3.10 tree, and
>> I'd like that layer to not be on people's local drives only.
>
> 3.10 EOL is projected as Sep, 2015 - do you plan to keep linux-yocto-3.10
> until then?
That's the plan. I tried to kill 3.4 before it official died and was
reminded that we'd keep LTSI support around a bit longer. I'm sure we
can bend a bit on the dates, but the general feel is correct .. the tree
will be around for a while yet.
Bruce
>
next prev parent reply other threads:[~2014-03-28 19:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 18:24 meta-yocto-bsp changes and 3.14 Richard Purdie
2014-03-28 18:27 ` Bruce Ashfield
2014-03-28 18:28 ` Bruce Ashfield
2014-03-28 18:34 ` Richard Purdie
2014-03-28 18:38 ` Bruce Ashfield
[not found] ` <CF5B1473.7DC1D%darren.hart@intel.com>
2014-03-28 18:59 ` Bruce Ashfield
[not found] ` <CF5B160D.7DC33%darren.hart@intel.com>
2014-03-28 19:08 ` Bruce Ashfield
2014-03-28 19:12 ` Denys Dmytriyenko
2014-03-28 19:14 ` Bruce Ashfield [this message]
[not found] ` <CF5B18D7.7DC4F%darren.hart@intel.com>
2014-03-28 19:27 ` Bruce Ashfield
[not found] ` <CF5B2B7A.7DCA2%darren.hart@intel.com>
2014-03-28 20:41 ` Bruce Ashfield
[not found] ` <20140328183036.GG12929@edge>
2014-03-28 18:32 ` Bruce Ashfield
2014-03-28 18:38 ` Denys Dmytriyenko
2014-03-28 19:48 ` Flanagan, Elizabeth
2014-03-28 19:58 ` Bruce Ashfield
2014-03-29 23:12 ` Richard Purdie
2014-03-30 12:37 ` Richard Purdie
2014-03-30 19:22 ` Bruce Ashfield
2014-03-31 14:55 ` Denys Dmytriyenko
2014-03-31 15:07 ` Denys Dmytriyenko
2014-03-30 14:46 ` Bruce Ashfield
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=5335CA00.8070207@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=denis@denix.org \
--cc=denys@ti.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.com \
--cc=yocto-builds@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.