Linux wireless drivers development
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Delphi Real Estate <Info@delphi-real-estate.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Kernel Compile Fail with 2.6.26 Drivers
Date: Fri, 23 Jan 2009 08:53:49 -0800	[thread overview]
Message-ID: <1232729629.4501.37.camel@rc-desk> (raw)
In-Reply-To: <200901230550.25986.Info@delphi-real-estate.com>

On Fri, 2009-01-23 at 05:50 -0800, Delphi Real Estate wrote:
> It seems that either no one has 'n' working at 5GHz, or are not willing to advise.  All I need is a combination that works;  I've tried 2.6's iwlwifi in 2.6.27 and it won't compile, and it seems that 2.6.28's iwlwifi doesn't work in 'n'.  I've run Debian for eleven years and have always compiled my own custom kernels, but would very much like to get 'n' working.  Scripting is no problem, although I am not an actual coder.  I wish someone could pitch in briefly.

As a summary of our discussion so far:

80211n currently works, except that you will get slower speeds because
TX aggregation is not working.

If you want TX aggregation support then you can use the iwl5000 branch
of the iwlwifi-2.6 repo on git.kernel.org, which is based on kernel
2.6.26.

We are working on getting TX aggregation working again.

Reinette




  reply	other threads:[~2009-01-23 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 17:42 Kernel Compile Fail with 2.6.26 Drivers Delphi Real Estate
2009-01-21 16:27 ` Delphi Real Estate
2009-01-22 13:58 ` Delphi Real Estate
2009-01-22 15:17   ` Luis R. Rodriguez
2009-01-23 13:50 ` Delphi Real Estate
2009-01-23 16:53   ` reinette chatre [this message]
2009-01-24  2:10     ` Delphi Real Estate
  -- strict thread matches above, loose matches on Subject: below --
2009-01-19 17:30 Delphi Real Estate
2009-01-19 18:46 ` reinette chatre
2009-01-19 21:48 ` Stefanik Gábor

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=1232729629.4501.37.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=Info@delphi-real-estate.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