linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Kenyon <simon@koala.ie>
To: linux-media@vger.kernel.org
Subject: Re: Results of the 'dropping support for kernels <2.6.22' poll
Date: Mon, 02 Mar 2009 23:28:44 +0000	[thread overview]
Message-ID: <49AC6BAC.9040901@koala.ie> (raw)
In-Reply-To: <alpine.LNX.2.00.0903021610280.16643@banach.math.auburn.edu>

kilgota@banach.math.auburn.edu wrote:
> Just one comment. IIRC, I was the one who mentioned the eeePC, having 
> recently bought one. I mentioned it, not because I disagree with 
> anything else you write here, but because, in fact, I agree. Frankly, 
> I think the use of the 2.6.21 kernel in the eeePC is somewhat perverse 
> and just a little bit weird.
>
> Essentially, the eeePC and the other Intel-based netbooks are not some 
> kind of exotic hardware platforms, which might provide an explanation 
> or excuse for using some "specially crafted" but old kernel. No. In 
> fact, the eeePC and almost all the other current netbooks are just a 
> new (and attractive) combination of some fairly standard types of 
> hardware. Practically every hardware component in them is better 
> supported in more recent kernels, with the possible exception of a 
> wireless device which may not yet be supported in any kernel, new or 
> old. Therefore, instead of worrying about whether to support and 
> provide indulgence for apparently inexplicable behavior, let us hope 
> that a decision of this nature will serve as a needed message.
just as another data point
i have an eee 900 and i run gentoo on it
i have 2.6.27 running just fine (wireless and all)

i know gentoo is a little too hardcore for most people
but living with a distro kernel forever is not a real requirement
--
simon

  reply	other threads:[~2009-03-02 23:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 21:18 Results of the 'dropping support for kernels <2.6.22' poll Hans Verkuil
2009-03-02 22:46 ` kilgota
2009-03-02 23:28   ` Simon Kenyon [this message]
2009-03-02 22:47 ` Trent Piepho
2009-03-03  7:19   ` Hans Verkuil
2009-03-03  8:06     ` Trent Piepho
2009-03-04 17:17 ` Mauro Carvalho Chehab
2009-03-05 18:56   ` Guennadi Liakhovetski
2009-03-05 20:19     ` Trent Piepho
2009-03-05 20:36       ` Guennadi Liakhovetski
2009-03-05 20:57         ` Trent Piepho
2009-03-05 21:29           ` Hans Verkuil
2009-03-05 22:20           ` Guennadi Liakhovetski
2009-03-07  0:01             ` Trent Piepho
2009-03-07  0:46               ` Guennadi Liakhovetski
2009-03-07  1:46                 ` hermann pitton
2009-03-15 16:39                 ` Trent Piepho
2009-03-15 16:48                   ` Hans Verkuil
2009-03-19  9:10                     ` Trent Piepho
2009-03-15 19:00                   ` Devin Heitmueller
2009-03-07 21:12               ` Adam Baker
2009-03-20 20:47   ` Hans Werner
2009-03-20 22:20     ` Mauro Carvalho Chehab
2009-03-21  2:03       ` Devin Heitmueller
2009-03-21  3:04         ` Mauro Carvalho Chehab
2009-03-21  5:21           ` Trent Piepho
2009-03-21 12:05           ` Devin Heitmueller
2009-03-21 17:35             ` Mauro Carvalho Chehab
2009-03-24 12:04               ` Trent Piepho
2009-03-21  5:16         ` Trent Piepho
  -- strict thread matches above, loose matches on Subject: below --
2009-03-24 12:25 Hans Verkuil

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=49AC6BAC.9040901@koala.ie \
    --to=simon@koala.ie \
    --cc=linux-media@vger.kernel.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).