From: Bob Feretich <bob.feretich@rafresearch.com>
To: yocto@yoctoproject.org
Subject: A simpler way of creating an using a local kernel repository - BeagleBone example
Date: Tue, 06 May 2014 15:31:52 -0700 [thread overview]
Message-ID: <536962D8.1040007@rafresearch.com> (raw)
I have had problems getting good download performance when accessing the
kernels at kernel.org. Since I expect to build the kernel several times,
I decided to create a copy of the kernel repository locally and use that
for my builds.
There are instructions on how to create a local repository in the Yocto
manuals, but those are more complex than I needed. (I don't plan on
checking anything into the repository.)
The below is a simpler way of creating and using the repository.
I'm publishing this because my search though the Yocto/OE/Angstrom
yielded only the more complicated or incomplete methods.
// First set up local kernel repository
mkdir ~/ksrc3-8
cd ~/ksrc3-8
git clone --bare
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
stable-work-bare.git
// Then modify the kernel recipe to use the local repository instead of
the the one at kernel.org.
// The beaglebone recipe for the 3.8 kernel is at...
setup-scripts/sources/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
// Replace the file's SRC_URI with one that points to your local repository.
#SRC_URI =
"git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.8.y"
SRC_URI = "git:///home/Bob/ksrc3-8/stable-work-bare.git;branch=linux-3.8.y"
Regards,
Bob
next reply other threads:[~2014-05-06 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:31 Bob Feretich [this message]
2014-05-06 22:39 ` A simpler way of creating an using a local kernel repository - BeagleBone example Bruce Ashfield
2014-05-06 22:45 ` Gary Thomas
2014-05-07 2:48 ` Bob Feretich
2014-05-07 10:46 ` Gary Thomas
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=536962D8.1040007@rafresearch.com \
--to=bob.feretich@rafresearch.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.