From: Darren Hart <dvhart@linux.intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/3] n450: add 2.6.37 kernel recipe and SMP support
Date: Wed, 27 Apr 2011 12:51:58 -0700 [thread overview]
Message-ID: <1303933921-10310-1-git-send-email-dvhart@linux.intel.com> (raw)
The atom-pc BSP which the n450 is based on was originally intended for single
CPU. The n450 is a single-core hyperthreaded CPU, so CONFIG_SMP and
CONFIG_SCHED_SMT are required to access the second hardware thread. These
patches add the newly created cfg/smp.scc config fragment to the recipe.
The current n450 BSP uses linux-yocto-stable (2.6.34), which was an oversight.
These patches add support for the linux-yocto (2.6.37) recipe and separately
enable that as the default. I have tested the linux-yocto kernel and confirmed
it boots, has functional networking, and can suspend and resume.
After some discussion with Tom, it seems that there is adequate testing planned
for the point release to allow for moving to the linux-yocto recipe. Note that
fixing bug 1010 makes significant changes to whichever kernel we choose
to use. Before I commit to meta-intel however, I would like the input of the QA
team.
How much testing was planned for the n450 originally? How much additional
testing would be required if we make the new kernel the default?
Thanks,
Darren Hart
next reply other threads:[~2011-04-27 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 19:51 Darren Hart [this message]
2011-04-27 19:51 ` [PATCH 1/3] n450: enable SMP and SCHED_SMT Darren Hart
2011-04-27 19:52 ` [PATCH 2/3] n450: add linux_yocto (2.6.37) bbappend Darren Hart
2011-04-27 19:52 ` [PATCH 3/3] n450: use linux-yocto (2.6.37) by default Darren Hart
2011-04-27 19:59 ` [PATCH 0/3] n450: add 2.6.37 kernel recipe and SMP support Bruce Ashfield
2011-04-27 22:19 ` Darren Hart
2011-04-28 0: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=1303933921-10310-1-git-send-email-dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@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.