Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267370AbUIJQLq (ORCPT ); Fri, 10 Sep 2004 12:11:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267464AbUIJQIl (ORCPT ); Fri, 10 Sep 2004 12:08:41 -0400 Received: from pengo.systems.pipex.net ([62.241.160.193]:55491 "EHLO pengo.systems.pipex.net") by vger.kernel.org with ESMTP id S267538AbUIJQEF (ORCPT ); Fri, 10 Sep 2004 12:04:05 -0400 Date: Fri, 10 Sep 2004 17:04:35 +0100 (BST) From: Tigran Aivazian X-X-Sender: tigran@einstein.homenet To: Alan Cox Cc: Bill Davidsen , Linux Kernel Mailing List Subject: Re: Latest microcode data from Intel. In-Reply-To: <1094828066.17442.4.camel@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 929 Lines: 21 On Fri, 10 Sep 2004, Alan Cox wrote: > > The microcode_ctl utility had a hardcoded default "/dev/cpu/microcode" and > > there is no real reason to change it because different distributions > > prefer a different value, so how to decide who is "right"? > > Documentation/devices.txt aka LANANA Ok, in that case microcode_ctl is right about "/dev/cpu/microcode" and distributions need to change to match it. Indeed, it always seemed silly to me to "pretend" that the microcode device node is "per cpu" in some sense (as it is impossible under Linux to bind userspace app to a given cpu then there is no "good" sense in which "per cpu" node can be defined). Kind regards Tigran - 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/