From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755873Ab0I2VEA (ORCPT ); Wed, 29 Sep 2010 17:04:00 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:40632 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751880Ab0I2VD7 (ORCPT ); Wed, 29 Sep 2010 17:03:59 -0400 Date: Wed, 29 Sep 2010 22:28:04 +0100 From: Alan Cox To: Jean Delvare Cc: Olof Johansson , Andrew Morton , linux-kernel@vger.kernel.org, Tejun Heo Subject: Re: [PATCH] dmi: export dmi data through debugfs Message-ID: <20100929222804.7f506ba5@lxorguk.ukuu.org.uk> In-Reply-To: <20100929171118.1dbf3fbb@endymion.delvare> References: <20100928211246.GA20941@lixom.net> <20100929093403.7db92388@endymion.delvare> <20100929145330.GA9351@lixom.net> <20100929171118.1dbf3fbb@endymion.delvare> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Now if you really insist on exposing the whole DMI table through sysfs, > I can't prevent you from doing that. After all, ACPI already exposes > its tables under /sys/firmware/acpi/tables (mode 0400). But then you'd > rather expose the DMI entry point and tables > under /sys/firmware/dmi/tables for consistency, rather than using > debugfs. But again, I don't think it is adding any value over what we > already have. If you really the DMI data generally available run dmidecode in the boot scripts directed to a file. It even has a dump mode for this. Alan