Linux-kernel mailing list archive 2000-07,: Re: [patch-2.3.36-p3] dd if=microcode of=/proc/driver/microcode

# Re: [patch-2.3.36-p3] dd if=microcode of=/proc/driver/microcode

Jeff Garzik (jgarzik@mandrakesoft.com)
Wed, 16 Feb 2000 19:07:55 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jeff Garzik: "PATCH 2.3.46: ll_rw_blk compile fixes"
- Previous message: Richard B. Johnson: "Re: Of removable devices"

Tigran Aivazian wrote:
>
> Hi Linus,
>
> This version implements a write-only file /proc/driver/microcode which
> gets rid of the need of any specialized tools. No ioctls - just write
> method. Why do we need ioctl here? We don't.
>
> Regards,
> Tigran.
>
> diff -urN -X dontdiff linux/arch/i386/config.in linux-mc/arch/i386/config.in
> --- linux/arch/i386/config.in Wed Feb 2 10:09:49 2000
> +++ linux-mc/arch/i386/config.in Wed Feb 16 22:22:31 2000
> @@ -49,6 +49,10 @@
> define_bool CONFIG_X86_USE_3DNOW y
> fi
>
> +if [ "$CONFIG_M686" = "y" -a "$CONFIG_PROC_FS" = "y" ]; then
> + tristate '/proc/driver/microcode - Intel P6 CPU microcode support' CONFIG_MICROCODE
> +fi
> +

Not all 686 machines, particularly ones running vendor-built kernels,
have CONFIG_M686 set. You should test CONFIG_X86 in Config.in, then let
the existing 686 processor tests in your driver take care of the rest.

    --
    Jeff Garzik         | Writing software is
    Building 1024       | more fun than working.
    MandrakeSoft, Inc.  | 	-Anon

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Jeff Garzik: "PATCH 2.3.46: ll_rw_blk compile fixes"
- Previous message: Richard B. Johnson: "Re: Of removable devices"