All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: remove old kernels
Date: Mon, 18 Oct 2010 22:14:29 +0200	[thread overview]
Message-ID: <20101018201429.GA818@boggieman> (raw)
In-Reply-To: <201010151039.08619.marcin@juszkiewicz.com.pl>

On Fri, Oct 15, 2010 at 10:39:05AM +0200, Marcin Juszkiewicz wrote:
> 
> Hi
> 
> recipes/linux/ contains 235 recipes. I would like to propose cleaning:
> 
> 1. drop 2.4 kernels - if someone still needs them then .oz354x and .stable
>    branches have them.

Agreed

> 
> This may affect:
> 
> - zauruses (which have 2.6 kernel)
> - ipaq h36/38/39/54/55 - some have 2.6 kernel
> - ipod - but does someone really uses 2.4.24 on own ipod?
> - ramses - but this is maintained out of tree
> - wrt54 - OpenWRT distro works better there and lets keep that way
> - xxs1500, mtx, sun4cdm - if someone maintain it at all then please raise your
>   hand
> - colinux - no one will cry
> - geodegx - 2.6 mainline works on it
> 
> 
> 2. Drop kernels older then 2.6.20 - it was over 3 years ago so if someone uses 
>    older one then probably also uses 3 years old OE. 
> 

Not sure that this is a good idea really. As an example, the best kernel
for the hp6xx is the 2.6.17 (yes its old I know, but everything works).
For the hp7xx its currently 2.6.19 (although its changing shortly to 2.6.34).

So how about putting the limit somewhat lower :) ? Like 2.6.15?

> This may affect (checked recipes):
> 
> - ep93xx - machines with this cpu are mainline supported, patches from ts72xx
>   and sim.one works
> - chumby
> - compulab-pxa270
> - devkitidp-pxa255
> - fsg3
> - gumstix
> - amsdelta
> - bd-neon
> - colinux
> - epia
> - geodelx
> - h1940
> - h6300
> - ks8695
> - magicbox
> - mtx-3
> - neuros
> - sun4cdm
> - tornado-omap2
> - wrap-geode
> - x86
> - acern30
> - logicpd-pxa270
> - mainstone
> - mx21ads
> - netbook-pro
> - triton
> - blueangel
> - universal
> 
> Some of those machines are not maintained anymore, many of them should work 
> with current mainline kernels. If someone cares about anything on a list - 
> raise your hand.
> 
> Why 2.6.20? Because NHK-15 uses it and does not work with mainline kernel.
> 
> Regards, 
> -- 
> JID:      hrw@jabber.org
> Website:  http://marcin.juszkiewicz.com.pl/
> LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  parent reply	other threads:[~2010-10-18 20:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15  8:39 RFC: remove old kernels Marcin Juszkiewicz
2010-10-15  9:05 ` Marco Cavallini
2010-10-15  9:13   ` Frans Meulenbroeks
2010-10-15  9:20   ` Marcin Juszkiewicz
2010-10-15  9:08 ` Frans Meulenbroeks
2010-10-15  9:19 ` Graeme Gregory
2010-10-15  9:34   ` Frans Meulenbroeks
2010-10-18 20:14 ` Kristoffer Ericson [this message]
2010-10-18 21:10   ` Ash Charles
2010-10-19  7:27   ` Marcin Juszkiewicz
2010-10-21 10:56     ` Kristoffer Ericson
2010-10-18 21:25 ` Khem Raj
2010-10-21  5:03 ` Vitus Jensen

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=20101018201429.GA818@boggieman \
    --to=kristoffer.ericson@gmail.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 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.