From: Horms <horms@debian.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mikhail Gusarov <dottedmag@dottedmag.net>,
debian-kernel@lists.debian.org, NetDev <netdev@vger.kernel.org>
Subject: Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
Date: Fri, 4 Nov 2005 12:29:20 +0900 [thread overview]
Message-ID: <20051104032918.GE4708@verge.net.au> (raw)
In-Reply-To: <20051102162620.GA32696@infradead.org>
On Wed, Nov 02, 2005 at 04:26:21PM +0000, Christoph Hellwig wrote:
> On Wed, Nov 02, 2005 at 12:54:09PM +0600, Mikhail Gusarov wrote:
> > So, having in mind the two levels of 'stablenesss': kernel
> > 'stableness' and modules 'stableness' :) we should find the way to
> > exclude discussed modules from the build, because in-kernel versions
> > will always be, erm..., slightly (1.0.0 is mentioned only as 'stone
> > age' in the mailing list of ipw2200 developers) outdated due to fact
> > integration and testing gets some time in upstream kernels. I propose
> > just to disable compilation of this drivers: everyone will be able to
> > compile the recent version using ipw2200-source we provide.
>
> The kernel drivers aren't stable but obsolete. Because of that ever
> distribution that supports it's users must patch in a more recent one,
> which is what we should do for debian aswell.
>
> It's a pity the braindead Intel policies don't allow us to have an uptodate
> driver in mainline.
Christoph,
do I take that comment to mean that upstream can't update the
drivers but Debian can? And if so, do you recommend updating
Debian's kernel packages, or putting the updates elsewhere?
--
Horms
next prev parent reply other threads:[~2005-11-04 3:29 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
2005-11-02 6:54 ` Mikhail Gusarov
2005-11-02 16:26 ` Christoph Hellwig
2005-11-04 3:29 ` Horms [this message]
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=20051104032918.GE4708@verge.net.au \
--to=horms@debian.org \
--cc=debian-kernel@lists.debian.org \
--cc=dottedmag@dottedmag.net \
--cc=hch@infradead.org \
--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).