From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758655AbZEFSpU (ORCPT ); Wed, 6 May 2009 14:45:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754947AbZEFSpE (ORCPT ); Wed, 6 May 2009 14:45:04 -0400 Received: from main.gmane.org ([80.91.229.2]:56949 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754076AbZEFSpD (ORCPT ); Wed, 6 May 2009 14:45:03 -0400 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Lifesaver Subject: DMI information from a kernel module? Date: Wed, 6 May 2009 18:44:08 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 128.107.241.170 (Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; InfoPath.2)) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I am using kernel version 2.6.16.46. I saw some code regarding dmi decoding in the kernel source tree - arch/i386/kernel/dmi_scan.c. I believe dmi_scan_machine is done early in the boot process using bt_ioremap, dmi_alloc etc. Is it the case, and if yes, is there a way to get a hold of the stored information (via functions like dmi_get_system_info) from a dynamically loaded kernel module?