Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Orjan Friberg <of@flatfrog.com>
To: <Openembedded-devel@lists.openembedded.org>
Subject: Discouraged kernels 2.6.35+?
Date: Wed, 6 Jul 2011 11:43:11 +0200	[thread overview]
Message-ID: <4E142E2F.6040101@flatfrog.com> (raw)

Hi,

We're looking at upgrading our BeagleBoard-derived board to 2.6.35+. 
Out of the kernels available where COMPATIBLE_MACHINE=beagleboard, is 
there any we should avoid?  (The ones available are .35, .37, .38, and .39.)

I'm thinking if there was an aborted porting attempt at some stage, or 
if a kernel was ported but never saw any actual use.


Also, on the 2011.03-maintenance branch, are all kernels valid or should 
we stick to the default kernel (.32)?

Thanks,
Orjan

-- 
Orjan Friberg
FlatFrog Laboratories AB



             reply	other threads:[~2011-07-06  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06  9:43 Orjan Friberg [this message]
2011-07-06  9:52 ` Discouraged kernels 2.6.35+? Henning Heinold
2011-07-06 10:21   ` Orjan Friberg
2011-07-06 11:13     ` Henning Heinold
2011-07-07  9:40       ` Orjan Friberg
2011-07-06 17:10     ` Enrico
2011-07-07  9:41       ` Orjan Friberg

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=4E142E2F.6040101@flatfrog.com \
    --to=of@flatfrog.com \
    --cc=Openembedded-devel@lists.openembedded.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