Date: Mon, 17 Nov 2003 21:23:31 +0100 (CET)
From: Maciej Zenczykowski <maze@cela.pl>
To: Andrew Pimlott <andrew@pimlott.net>
cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_CRC32 in 2.4.22 breaks PCMCIA
In-Reply-To: <20031117200451.GA12931@pimlott.net>
Message-ID: <Pine.LNX.4.44.0311172121400.3939-100000@gaia.cela.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1080
Lines: 27

> CONFIG_CRC32 was introduced in 2.4.22.  I found that if I didn't
> explicitly set it, the pcnet_cs driver from stand-alone PCMCIA
> distribution didn't work.  PCMCIA relies on the crc functions, and
> since they were always available before 2.4.22, it doesn't check for
> them.

Something wrong with the in-kernel pcnet_cs?

> This seems to be significant breakage, and it took me a good while
> to figure out what was going on.  Is this change reasonable in the
> stable kernel series?

Well, it's in the help for the CRC32 option that it's available to enable 
external-kernel tree drivers to access these functions.  If you are 
running make oldconfig you'll hit the question and if you don't know what 
it's about you should consult help...
Seems reasonable to me.  Same aplies to deflate, etc. support routines.

Cheers,
MaZe.


-
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/