linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Farina <sidhayn@gmail.com>
To: lina <lina.lastname@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: something about compact-wireless
Date: Wed, 08 Feb 2012 21:11:53 -0500	[thread overview]
Message-ID: <4F332B69.6090009@gmail.com> (raw)
In-Reply-To: <CAG9cJmmffGJBpefd5uz6DP=kjdxPPU7K6hrt0SF81hTL04hLCw@mail.gmail.com>

On 02/08/12 21:09, lina wrote:
> On Thu, Feb 9, 2012 at 2:14 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>> On 02/08/2012 11:05 AM, lina wrote:
>>> Hi,
>>>
>>> The question i am going to ask might sounds silly, please forgive,
>>>
>>> do I need the compact-wireless in future? something about it's history?
>>
>> Obviously, you do not understand the reason for compat-wireless. It is used
>> to backport the wireless drivers in the development kernels so that they can
>> be used on older kernels. Whether you need it depends on what kernel you are
>> using, and what device(s) you have. The short answer is "probably not".
> Thanks for explaination.
>
> last night I installed the $ uname -a
> Linux debian 3.2.5
>
> Do I still need install the compact-wireless?
if you don't know if you need compat-wireless then you don't need
compat-wireless.

Enjoy.

-Rick
>
> Thanks again,
>
>> Larry
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2012-02-09  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 17:05 something about compact-wireless lina
2012-02-08 18:14 ` Larry Finger
2012-02-09  2:09   ` lina
2012-02-09  2:11     ` Richard Farina [this message]
2012-02-09  3:06       ` lina
2012-02-09 15:43         ` Pavel Roskin

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=4F332B69.6090009@gmail.com \
    --to=sidhayn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=lina.lastname@gmail.com \
    --cc=linux-wireless@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).