From: John Daiker <daikerjohn@gmail.com>
To: Matteo Croce <technoboy85@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Compat wireless with kernel 2.6.33
Date: Mon, 05 Apr 2010 15:17:42 -0700 [thread overview]
Message-ID: <4BBA6186.2030108@gmail.com> (raw)
In-Reply-To: <40101cc31003200759u447b625ct6f48aa6003593dac@mail.gmail.com>
Luis,
It would be nice to see this pushed into the latest compat-wireless.
It's helpful for people using a 2.6.33 kernel and needing the latest b43
updates for our Atom-based netbooks! :)
John Daiker
On 03/20/2010 07:59 AM, Matteo Croce wrote:
> This patch allows compat wireless to compile with a kernel>= 2.6.33
>
> Index: compat-wireless-2010-03-19/scripts/gen-compat-autoconf.sh
> ===================================================================
> --- compat-wireless-2010-03-19.orig/scripts/gen-compat-autoconf.sh 2010-03-20
> 15:26:22.604720545 +0100
> +++ compat-wireless-2010-03-19/scripts/gen-compat-autoconf.sh 2010-03-20
> 15:27:49.212236531 +0100
> @@ -145,7 +145,11 @@
> kernel_version_req $OLDEST_KERNEL_SUPPORTED
>
> # Handle core kernel wireless depenencies here
> +echo '#if LINUX_VERSION_CODE>= KERNEL_VERSION(2,6,33)'
> +define_config_req CONFIG_CFG80211_WEXT
> +echo '#else'
> define_config_req CONFIG_WIRELESS_EXT
> +echo '#endif'
>
> # For each CONFIG_FOO=x option
> for i in $(grep '^CONFIG_' $COMPAT_CONFIG); do
>
>
next prev parent reply other threads:[~2010-04-05 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 14:59 Compat wireless with kernel 2.6.33 Matteo Croce
2010-04-05 22:17 ` John Daiker [this message]
2010-04-05 23:34 ` Luis R. Rodriguez
2010-04-05 23:54 ` Matteo Croce
2010-04-06 0:08 ` Luis R. Rodriguez
2010-04-06 6:58 ` Johannes Berg
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=4BBA6186.2030108@gmail.com \
--to=daikerjohn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=technoboy85@gmail.com \
/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).