|| ||Dave Jones <davej-AT-redhat.com>|
|| ||Alistair John Strachan <s0348365-AT-sms.ed.ac.uk>|
|| ||Re: [2.6 patch] i386: always use 4k stacks|
|| ||Mon, 14 Nov 2005 13:18:54 -0500|
|| ||Alan Cox <alan-AT-lxorguk.ukuu.org.uk>,
Alex Davis <alex14641-AT-yahoo.com>, linux-kernel-AT-vger.kernel.org|
On Mon, Nov 14, 2005 at 06:02:45PM +0000, Alistair John Strachan wrote:
> On Monday 14 November 2005 14:49, Alan Cox wrote:
> > On Llu, 2005-11-14 at 05:38 -0800, Alex Davis wrote:
> > > This will break ndiswrapper. Why can't we just leave this in and let
> > > people choose?
> > If we spent our entire lives waiting for people to fix code nothing
> > would ever happen. Removing 8K stacks is a good thing to do for many
> > reasons. The ndis wrapper people have known it is coming for a long
> > time, and if it has a lot of users I'm sure someone in that community
> > will take the time to make patches.
> I honestly don't know if this is the case, but is it conceivable that no patch
> could be written to resolve this, because the Windows drivers themselves only
> respect Windows stack limits (which are presumably still 8K?).
Windows drivers can actually use more than 8KB. So in some situations,
you're already screwed. There are already cases where vendors customer
service are now telling people "Use ndiswrapper" when people ask about
If we continue down this path, we'll have no native wireless drivers for Linux.
The answer is not to complain to linux-kernel for breaking ndiswrapper,
but complain to the vendors for not releasing specifications for
native drivers to be written.
to post comments)