From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.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>,
"saul.wold" <saul.wold@intel.com>
Subject: Re: meta-yocto-bsp changes and 3.14
Date: Fri, 28 Mar 2014 14:38:39 -0400 [thread overview]
Message-ID: <5335C1AF.5080904@windriver.com> (raw)
In-Reply-To: <1396031644.14790.26.camel@ted>
On 14-03-28 02:34 PM, Richard Purdie wrote:
> On Fri, 2014-03-28 at 14:28 -0400, Bruce Ashfield wrote:
>> On 14-03-28 02:27 PM, Bruce Ashfield wrote:
>>> On 14-03-28 02:24 PM, Richard Purdie wrote:
>>>> I've merged Bruce's 3.14 patches into master-next. With the yocto-bsp
>>>> parts that I could pull together, there seemed to be some pieces
>>>> missing, specifically:
>>>>
>>>> * the yocto-linux-dev.bbappend was underpopulated
>>>> * the yocto-linux-3.14.bbappend was missing
>>>
>>> I have one of these, I was hoping the BSP developers would submit
>>> it, but I can commit and send mine.
>>>
>>>> * no removal of beagleboard
>>>
>>> I was keeping this around, for the 3.10 and older trees.
>>>
>>>> * no addition to the README for beaglebone
>>>
>>> Denys and I talked about this, one should be pending.
>>>
>>>> * local.conf.sample needs updates
>>>> * missing edgerouter configuration in linux-yocto*
>>>
>>> Hmm. no, it's definitely there, so I'm not sure
>>
>> I forgot to finish this. This is all here for me, what exactly are you
>> seeing that is missing ?
>
> Specifically, I had to add:
>
> http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?h=master-next&id=21f04021a62248bdb827e7d7acc103deb9136b5d
>
> http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?h=master-next&id=c94b1e4dc6af0848a30b4275f3cc2bc894f5e267
>
> http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?h=master-next&id=03bdb1421e51fa2a4da4bae42ff0b42a92c5acce
>
> So I can't help feeling I'm missing some patches from somewhere or
> something.
Aha. I thought you meant the in-kernel configuration and branch information.
Yes, those are missing, I was going to get them from the BSP creators,
but instead, I'll send mine along.
It'll be a little while though, I had to clean my builder when changing
PVs, so I need to wait full a full kernel refetch.
>
> 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.
Bruce
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2014-03-28 18:38 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 [this message]
[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
[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=5335C1AF.5080904@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=denys@ti.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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.