Linux wireless drivers development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: "Marco Höfle" <Marco.Hoefle@web.de>, linux-wireless@vger.kernel.org
Subject: Re: Bug or am I too stupid for installing the Intel Wirelss drivers for Linux?
Date: Wed, 2 Jan 2008 13:07:11 -0500	[thread overview]
Message-ID: <20080102180711.GB3120@tuxdriver.com> (raw)
In-Reply-To: <1198855928.23441.8.camel@localhost.localdomain>

On Fri, Dec 28, 2007 at 10:32:07AM -0500, Dan Williams wrote:

> In any case, since RHEL5 runs 2.6.18, you'll need to work a bit to
> backport mac80211 and iwl3945.  There were some heavy crypto changes
> around 2.6.18/2.6.19, and there may be quite a lot of lower level
> network stack churn that you'll have to deal with.

You might try the test kernels here:

	http://people.redhat.com/linville/kernels/rhel5/

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

      reply	other threads:[~2008-01-02 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 13:35 Bug or am I too stupid for installing the Intel Wirelss drivers for Linux? Marco Höfle
2007-12-28 15:32 ` Dan Williams
2008-01-02 18:07   ` John W. Linville [this message]

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=20080102180711.GB3120@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Marco.Hoefle@web.de \
    --cc=dcbw@redhat.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