Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 Oct 2006 12:25:05 +0100
Ar Sad, 2006-10-21 am 10:17 +0200, ysgrifennodd Borislav Petkov:
This one should be probably made dependent on some #define saying that the cpu
is an AMD and has the LX Geode crypto hardware built in. Turn it off for now.
That makes no real sense. Most kernel selections are "run on lots of
processor types", we thus want as much as possible modular, built and
available.
The existing defaults seem quite sane.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- From: Michael Buesch
- Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- From: Borislav Petkov
- Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- From: Borislav Petkov
- Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- References:
- [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- From: Borislav Petkov
- [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- Prev by Date: Re: [PATCH 2.6.19-rc2] [REVISED] net/ipv4/multipath_wrandom.c: check kmalloc() return value.
- Next by Date: New software uploaded by Denise on Oct 23 07:10:00 -4 2006
- Previous by thread: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- Next by thread: Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
- Index(es):
Relevant Pages
|
