From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: rpurdie@linux.intel.com
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Mon, 17 Jan 2011 16:57:29 -0500 [thread overview]
Message-ID: <cover.1295300980.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
This pull request contains three changes on top of the previously
sent changes that are still pending:
linux-yocto: enable arch ARM config settings for KARCH based boards
linux-yocto-stable: add atom-pc preempt_rt support
linux-yocto: add systemtap config to -stable and -dev kernels
But I wanted to send these anyway, since them sitting on my disk
here isn't helping anyone.
The first commit:
linux-yocto: update validate_branches to detected invalid commit IDs
Addresses a problem that Richard ran into when invalid commit IDs
are used for SRCREVs. I tested this while fixing the ARM boot
issues.
The second commit:
linux-yocto: streamline new BSP creation
Is self explanitory, as is the commit message. With this change you
can throw a previously unknown machine at the yocto kernel and have
a resonable first effort at booting the board and creating an
environment for development.
And finally:
linux-yocto: beagleboard enablement
Enables the beagleboard for 2.6.37. The patch itself has the details.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---
Bruce Ashfield (3):
linux-yocto: beagleboard enablement
linux-yocto: streamline new BSP creation
linux-yocto: update validate_branches to detected invalid commit IDs
meta/classes/kernel-yocto.bbclass | 37 ++++++++++++++++++++---------------
meta/conf/machine/beagleboard.conf | 6 ++--
2 files changed, 24 insertions(+), 19 deletions(-)
next reply other threads:[~2011-01-17 21:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:57 Bruce Ashfield [this message]
2011-01-17 21:57 ` [PATCH 1/3] linux-yocto: beagleboard enablement Bruce Ashfield
2011-01-17 21:57 ` [PATCH 2/3] linux-yocto: streamline new BSP creation Bruce Ashfield
2011-01-17 21:57 ` [PATCH 3/3] linux-yocto: update validate_branches to detected invalid commit IDs Bruce Ashfield
2011-05-05 4:53 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2011-05-09 18:34 Bruce Ashfield
2011-05-10 17:53 ` Saul Wold
2011-08-15 20:24 Bruce Ashfield
2011-08-22 22:37 ` Saul Wold
2011-08-19 5:20 Bruce Ashfield
2011-08-20 5:08 ` Bruce Ashfield
2011-09-03 3:03 Bruce Ashfield
2011-09-05 19:26 ` Richard Purdie
2011-09-14 18:11 Bruce Ashfield
2011-09-15 17:37 ` Saul Wold
2011-12-08 17:11 Bruce Ashfield
2012-01-04 20:12 Bruce Ashfield
2012-02-27 19:34 Bruce Ashfield
2012-02-28 18:41 ` Saul Wold
2012-03-05 4:01 Bruce Ashfield
2012-03-13 15:54 ` Saul Wold
2012-08-27 4:49 Bruce Ashfield
2012-08-28 14:22 ` Saul Wold
2012-08-29 7:58 ` Bruce Ashfield
2012-12-03 20:49 Bruce Ashfield
2013-09-18 18:24 Bruce Ashfield
2013-11-26 17:33 Bruce Ashfield
2016-05-24 15:53 Bruce Ashfield
2016-06-06 8:15 Bruce Ashfield
2016-09-20 15:16 Bruce Ashfield
2018-04-09 15:16 Bruce Ashfield
2019-01-12 18:12 Bruce Ashfield
2019-01-21 17:26 Bruce Ashfield
2019-02-06 19:50 bruce.ashfield
2019-02-09 18:37 bruce.ashfield
2020-03-22 1:18 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=cover.1295300980.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=rpurdie@linux.intel.com \
--cc=saul.wold@intel.com \
--cc=yocto@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.