[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <488AEA54.2030703@uw.no>
Date: Sat, 26 Jul 2008 09:11:48 +0000
From: "Daniel K." <dk@...no>
To: Peter Oruba <peter.oruba@....com>
CC: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 8/9] [PATCH 8/9] x86: Major refactoring.
Peter Oruba wrote:
> Refactored code by introducing a two-module solution. There is one
> general module in which vendor specific modules can hook into.
>
> config MICROCODE
> - tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
> + tristate "/dev/cpu/microcode - microcode support"
> select FW_LOADER
> ---help---
> If you say Y here, you will be able to update the microcode on
> @@ -791,14 +791,28 @@ config MICROCODE
> actual microcode binary data itself which is not shipped with the
> Linux kernel.
>
> - For latest news and information on obtaining all the required
> - ingredients for this driver, check:
> - <http://www.urbanmyth.org/microcode/>.
> + This option selects the general module only, you need to select
> + at least one vendor specific module as well.
>
> To compile this driver as a module, choose M here: the
> module will be called microcode.
>
> -config MICROCODE_OLD_INTERFACE
> +config MICROCODE_INTEL
> + tristate "Intel microcode patch loading support"
> + depends on MICROCODE
default MICROCODE
so that users doing make oldconfig don't get a surprise?
> + select FW_LOADER
> + --help---
> + This options enables microcode patch loading support for Intel
> + processors.
> +
> + For latest news and information on obtaining all the required
> + Intel ingredients for this driver, check:
> + <http://www.urbanmyth.org/microcode/>.
> +
> + This driver is only available as a module: the module
> + will be called microcode_intel.
> +
> + config MICROCODE_OLD_INTERFACE
Kill the extra spaces.
Daniel K.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists