From: Ismail Donmez <ismail@pardus.org.tr>
To: Stephen.Clark@seclark.us
Cc: jketreno@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: IEEE80211 and IPW3945
Date: Sat, 18 Nov 2006 16:41:13 +0200 [thread overview]
Message-ID: <200611181641.14429.ismail@pardus.org.tr> (raw)
In-Reply-To: <455F180A.9080301@seclark.us>
18 Kas 2006 Cts 16:26 tarihinde, Stephen Clark şunları yazmıştı:
> Ismail Donmez wrote:
> >18 Kas 2006 Cts 12:20 tarihinde, Martin Lorenz şunları yazmıştı:
> >>Dear James,
> >>
> >>I just had some issues when trying to compile ieee80211 1.2.15 together
> >>with ipw3945 1.1.2 on the latest kernel tree
> >>
> >>attached are two patches I had to create to work around it
> >>I guess they are self-explanatory :-)
> >
> >I wonder when will ieee80211 tree will be merged to mainline, according to
> >some posts[1] its needed for some devices.
> >
> >[1] http://www.ubuntuforums.org/showthread.php?t=156930
> >
> >/ismail
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
>
> On Mon, 13 Nov 2006 08:42:55 -0500 Stephen Clark wrote:
> >> can someone tell me why I have to replace the 803.11 stack that is
> >> already in
> >> linux 2.6.19 rc5 with the stack at sf.
>
> You don't have to.
> The one in .19-rc5 is new enough (the one in .18 too AFAIK)
>
> I have successfully run ipw3945 with FC6 using the ieee80211 stack from the
> kernel I just had to compile with:
> make IEEE80211_API=2 EXTRA_CFLAGS=-DIEEE80211_API_VERSION=2
Nice tip! Thanks.
/ismail
prev parent reply other threads:[~2006-11-18 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 10:20 Martin Lorenz
2006-11-18 12:31 ` Hesse, Christian
2006-11-18 12:49 ` Ismail Donmez
2006-11-18 14:26 ` Stephen Clark
2006-11-18 14:41 ` Ismail Donmez [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=200611181641.14429.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=Stephen.Clark@seclark.us \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@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
Powered by JetHome