Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 29 Sep 2002 12:03:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 29 Sep 2002 12:03:58 -0400 Received: from noodles.codemonkey.org.uk ([213.152.47.19]:386 "EHLO noodles.internal") by vger.kernel.org with ESMTP id ; Sun, 29 Sep 2002 12:03:57 -0400 Date: Sun, 29 Sep 2002 17:11:44 +0100 From: Dave Jones To: Matt Domsch Cc: linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Message-ID: <20020929161144.GA19948@suse.de> Mail-Followup-To: Dave Jones , Matt Domsch , linux-kernel@vger.kernel.org References: <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 24 On Fri, Sep 27, 2002 at 04:30:29PM -0500, Matt Domsch wrote: > arch/i386/kernel/edd.c | 522 +++++++++++++++++++++++++++++++++++++++ > arch/i386/kernel/i386_ksyms.c | 6 > arch/i386/kernel/setup.c | 20 + Something that's been bothering me for a while, has been the proliferation of 'driver' type things appearing in arch/i386/kernel/ My initial thought was to move the various CPU related 'drivers' (msr,cpuid,bluesmoke,microcode) to arch/i386/cpu/ [1] but I'm now wondering if an arch/i386/driver/ would be a better alternative. Opinions? Dave [1] also a more natural home for things like cpufreq if/when it gets integrated. -- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/