netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Bonilla Beeche <abonilla@linuxwireless.org>
To: Horms <horms@verge.net.au>
Cc: Mikhail Gusarov <dottedmag@dottedmag.net>,
	debian-kernel@lists.debian.org, NetDev <netdev@vger.kernel.org>,
	James Ketrenos <jketreno@linux.intel.com>
Subject: Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
Date: Tue, 01 Nov 2005 20:44:06 -0700	[thread overview]
Message-ID: <43683606.4060703@linuxwireless.org> (raw)
In-Reply-To: <20051102020903.GG29803@verge.net.au>

Horms wrote:

>On Tue, Nov 01, 2005 at 11:30:09PM +0600, Mikhail Gusarov wrote:
>  
>
>>Hello,
>>
>>I've encountered the problem with 2.6.14 kernels: they are shipped
>>with ancient version of ipw2200 drivers (1.0.0 while current version
>>is 1.0.7) and ancient version of ieee80211 subsystem (copyrighted as
>>2004, so also outdated).
>>
>>This breaks compilation of module from ipw2200-source package (because
>>it links against in-kernel ieee80211).
>>    
>>
The .deb will need to run the remove-old script included in the new 
versions of the driver/stack.

>
>I assume the problem you are seeing is a headers problem.
>
>  
>
>>Is there way to modularize builds to exclude ieee80211 or just disable
>>it (along with ipw2200) because it is outdated and current vesion is
>>shipped in ieee80211-source package?
>>    
>>
>
>Probably the best place to start is to ping netdev to find out if
>there are any plans to update IPW2200 in Linus's tree. I've CCed
>that list, hopefully someone can shed some light on this.
>
>  
>
Not really. Basically, only stable versions of the driver make it into 
Mainline, and currently 1.0.8 is being tested to move into mainline 
(first -mm, then when people decide move to Linus)

Basically, when installing 1.0.8 and ieee80211-1.1.5, the .deb packages 
or whatever will need to run the remove-old script that is included in 
the source in order to make the new versions compile.

.Alejandro

  reply	other threads:[~2005-11-02  3:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <873bmg9sym.fsf@vertex.dottedmag.net>
2005-11-02  2:09 ` ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14) Horms
2005-11-02  3:44   ` Alejandro Bonilla Beeche [this message]
2005-11-02  6:54   ` Mikhail Gusarov
2005-11-02 16:26     ` Christoph Hellwig
2005-11-04  3:29       ` Horms
2005-11-05  0:21         ` Christoph Hellwig
2005-11-05  8:25           ` Harald Welte

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=43683606.4060703@linuxwireless.org \
    --to=abonilla@linuxwireless.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=dottedmag@dottedmag.net \
    --cc=horms@verge.net.au \
    --cc=jketreno@linux.intel.com \
    --cc=netdev@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).