public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lev Makhlis <mlev@despammed.com>
To: Michael Brown <mebrown@michaels-house.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4] add SMBIOS information to /proc/smbios -- UPDATE 2
Date: Fri, 30 Apr 2004 23:07:43 -0500	[thread overview]
Message-ID: <200405010007.43171.mlev@despammed.com> (raw)
In-Reply-To: <1083382335.1203.2975.camel@debian>

On Friday 30 April 2004 23:32, Michael Brown wrote:
> On Fri, 2004-04-30 at 19:09, Lev Makhlis wrote:
> > > +	for (fp = 0xF0000; fp < 0xFFFFF; fp += 16) {
> > > +		isa_memcpy_fromio(table_eps, fp, sizeof(*table_eps));
> > > +		if (memcmp(table_eps->anchor, "_SM_", 4)!=0)
> > > +			continue;
> >
> > This is fine for x86 and x86_64, but for ia64 -- don't you need
> > to get the SMBIOS entry point from the EFI table?
>
> Sorry, but I am not familiar with how SMBIOS tables work on IA64
> architecture, and in fact, the DMI spec says nothing about how it
> differs on IA64, that I can see.
>
> Can you please send me a URL with this information? I have access to
> some IA64 machines. I will add this code if I have a spec.
> --
> Michael

The EFI spec is here: http://developer.intel.com/technology/efi/EFI_110.htm
(SMBIOS pointer is mentioned in section 4.3), but arch/ia64/kernel/efi*.c
already reads EFI.  You may want to look at dmidecode
(http://freshmeat.net/projects/dmidecode/), which has code to read
/proc/efi/systab (which, last I checked, itself required a patch).
In kernel space, I think you could just use efi.smbios, but I'm not an expert
on that myself.

Lev


  reply	other threads:[~2004-05-01  4:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01  0:09 [PATCH 2.4] add SMBIOS information to /proc/smbios -- UPDATE 2 Lev Makhlis
2004-05-01  3:32 ` Michael Brown
2004-05-01  4:07   ` Lev Makhlis [this message]
2004-05-01  4:15     ` Michael Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-04-30  5:08 Michael Brown

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=200405010007.43171.mlev@despammed.com \
    --to=mlev@despammed.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mebrown@michaels-house.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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