archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <>
Subject: Re: [PATCH 2.4] dmi_ident made public
Date: Sat, 26 Apr 2003 14:20:02 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> > What's more, I plan to write another module that exports the DMI
> > data, as scanned at boot time, to userland (via sysfs), and such a
> > module definitely requires that the DMI data is made public in
> > dmi_scan.
> I suspect the DMI module should itself do the sysfs interface, and I 
> certainly think the idea of it being in sysfs has merit.

I was not really sure about this. There are two issues that would need
to be discussed:
1* Including it into dmi_scan makes it impossible to be a module, at
least with my knowledge of the modules mechanics. Correct me if I'm
2* There is a need for dmi scanning on IA-64 systems, where locating the
DMI table follows a different scheme from what we do for i386 systems.
Having a platform-independant module for the sysfs stuff would save us
from code duplication (which is precisely what I am trying to avoid
I don't know how much of a concern these two points are, and any light
will be appreciated.

Anyway, I think this is almost a completely different problem from the
one I first posted about. There still are two modules around (i8k and
omke) that would take great benefit of the simple patch I submitted some
days ago. So, unless there is any motivated objection against it (such
as an alternative solution I wouldn't have thought about), I'd still
like to see the above mentioned patch applied, since it would give us
the possibility to remove all the duplicated code (more than 100 lines
per module).


Jean Delvare

      reply	other threads:[~2003-04-26 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 16:47 [PATCH 2.4] dmi_ident made public Jean Delvare
2003-04-24 18:31 ` Alan Cox
2003-04-24 22:43   ` Jean Delvare
2003-04-24 23:10 ` Greg KH
2003-04-25 10:15   ` Jean Delvare
2003-04-25 10:11     ` Alan Cox
2003-04-26 12:20       ` Jean Delvare [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).