All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harrison Lee" <harrisonl@tme-inc.com>
To: <backports@vger.kernel.org>
Subject: RE: Bumping required kernels to 3.0 for Linux backports ?
Date: Fri, 11 Apr 2014 10:22:04 -0400	[thread overview]
Message-ID: <006d01cf5591$694ee230$3beca690$@com> (raw)
In-Reply-To: <CAB=NE6VeNTFeGxKXpYunkU-W=JPLMpOnrehttvsqB+yXkdz5fg@mail.gmail.com>

Compat-wireless drivers have been very useful to users like us, who have to work with embedded linux system based on old kernel. For example, we work on a arm based system with 2.6.28 kernel, and could use ath9k drivers thanks to compat-wireless-3.6.8-1. The company who provided the SDK, a big name company, does not have any plan to upgrade the kernel, so we are stuck with it due to all the customized drivers for the chip.

But the situation seems to be changing. Compat-drivers does not support 2.6.28 any more for ath9k. It only supports from 2.6.30 according to "dependencies" list.

I've just joined the mailing list to learn how to backport wwan drivers. And the first message I see is about dumping supports for older kernels...

Would there be any alternatives for old kernel users, then?

Harrison

> 
> That's two stakeholders for 3.0 -- but nothing is voiced for anything
> older than that. Today I will rip the older kernels into oblivion.
> Thanks for all the feedback!
> 
>  Luis
 

__________ Information from ESET NOD32 Antivirus, version of virus signature database 9666 (20140411) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 



  parent reply	other threads:[~2014-04-11 14:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  1:03 Bumping required kernels to 3.0 for Linux backports ? Luis R. Rodriguez
2014-04-09  9:18 ` Felix Fietkau
2014-04-09 18:28   ` Luis R. Rodriguez
2014-04-09 19:12     ` Greg Kroah-Hartman
2014-04-09 20:01       ` Luis R. Rodriguez
2014-04-09 20:22         ` Greg Kroah-Hartman
2014-04-09 20:52           ` Luis R. Rodriguez
2014-04-09 21:06             ` Greg Kroah-Hartman
2014-04-10  7:31               ` Johannes Berg
2014-04-10  7:44               ` Takashi Iwai
2014-04-10 16:59                 ` Luis R. Rodriguez
2014-04-10 17:04                   ` Arend van Spriel
2014-04-10 17:11                     ` Luis R. Rodriguez
2014-04-10 17:24                     ` Loren Kirkby
2014-04-10 17:25                     ` Loren Kirkby
2014-04-10 18:56                     ` Luis R. Rodriguez
2014-04-11  7:51                       ` Arend van Spriel
2014-04-11 18:18                         ` Luis R. Rodriguez
2014-04-11 14:22                   ` Harrison Lee [this message]
2014-04-11 18:23                     ` Luis R. Rodriguez
2014-04-11 18:45                       ` Johannes Berg
2014-04-11 19:18                         ` Luis R. Rodriguez
2014-04-11 19:51                           ` Harrison Lee
2014-04-11 19:56                             ` Luis R. Rodriguez
2014-04-11 20:07                           ` Johannes Berg
2014-04-11 20:47                             ` Luis R. Rodriguez
2014-04-11 19:26                         ` Solomon Peachy
2014-04-10 17:16   ` Johannes Berg
2014-04-10 17:26     ` Felix Fietkau
2014-04-10 17:35       ` Johannes Berg
2014-04-09 10:59 ` Arend van Spriel
2014-04-09 18:25   ` Luis R. Rodriguez

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='006d01cf5591$694ee230$3beca690$@com' \
    --to=harrisonl@tme-inc.com \
    --cc=backports@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 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.