From: don.brown@codethink.com (Don Brown)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Creating a Linux kernel from the stock linux-cip repo
Date: Fri, 05 May 2017 16:57:54 -0400 [thread overview]
Message-ID: <e9a6f6eff0f21155d7b6b77282912377@codethink.com> (raw)
Hi Ben,
As I was working with the Beaglebone Black trying to get the health
check to pass, it occurred to me that I don't know how to create a
kernel specifically for the BBB using just the stock CIP Kernel from
https://gitlab.com/cip-project/linux-cip
The linux-cip kernel doesn't have a defconfig for the Beaglebone Black,
or for the AM335x CPU as far as I can tell.
The Linaro BBB Health Check pulls the am335x-boneblack.dtb from their
repository, but it isn't clear what we need to add to the linux-cip to
have KernelCI build the kernel from scratch. Can you please take a look
and let us know?
The official repo is at:
https://github.com/beagleboard/linux
It has a bb.org_defconfig here:
https://github.com/beagleboard/linux/blob/4.4/arch/arm/configs/bb.org_defconfig
Is that all we need?
Thank you!
--
Don Brown
Codethink, Ltd.
Software Engineering Consultant
Indianapolis, IN USA
Email: don.brown at codethink.co.uk
Mobile: +1 317-560-0513
reply other threads:[~2017-05-05 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e9a6f6eff0f21155d7b6b77282912377@codethink.com \
--to=don.brown@codethink.com \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox