From: arigead@gmail.com (John Whitmore)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Building which kernel?
Date: Sun, 14 Jun 2015 16:54:31 +0100 [thread overview]
Message-ID: <20150614155430.GB28612@bamboo.electronicsoup> (raw)
In-Reply-To: <20150614152703.GA17619@kroah.com>
On Sun, Jun 14, 2015 at 08:27:03AM -0700, Greg KH wrote:
> On Sun, Jun 14, 2015 at 02:11:33PM +0100, John Whitmore wrote:
> > I've a question regarding the building of the linux kernel, more specifically
> > which kernel to build.
>
> Always the latest version, why would you want to build an old one?
>
> > I've previously built the kernel for an 86 arch but this time I want to build
> > for the RaspberryPi. I can easily get the current version of the installed
> > kernel with the "uname -a" command but that doesn't tell me the git repo
> > where the kernel originated. I'd imagine that it's from the RPi git repo, but
> > that adds another level of confusion as that git repo doesn't have any tags at
> > all. So even given the version number from uname how to check out a suitable
> > version of the kernel.
>
> If you are using hardware that is not completly supported in the main
> kernel.org repo, like many embedded devices like the RPi, I suggest
> using the source repo that the project provides instead.
>
> > I could take the latest from the RPi repo and use "make oldconfig" but I
> > wonder how far, in kernel versions, I can jump and not affect the installed
> > libs and utilities which have been built against another version of the
> > kernel?
>
> You should always be able to use a new kernel on old userspace with no
> problems. Going backwards is not supported (old kernel on new
> userspace.)
>
> hope this helps,
>
> greg k-h
Yes that clears up versions, thanks a milion.
John
prev parent reply other threads:[~2015-06-14 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 13:11 Building which kernel? John Whitmore
2015-06-14 15:24 ` Lucas Tanure
2015-06-14 15:27 ` Greg KH
2015-06-14 15:54 ` John Whitmore [this message]
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=20150614155430.GB28612@bamboo.electronicsoup \
--to=arigead@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).