From: "Pali Rohár" <pali.rohar@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Dell Latitude E6440 & i8k
Date: Sun, 18 May 2014 08:36:16 +0000 [thread overview]
Message-ID: <201405181036.16704@pali> (raw)
In-Reply-To: <20140518101910.35059ee7@endymion.delvare>
[-- Attachment #1.1: Type: Text/Plain, Size: 1004 bytes --]
On Sunday 18 May 2014 10:19:10 Jean Delvare wrote:
> Please leave the list in Cc.
>
Sorry I forgot, but after that I resent original message to list.
> On Sun, 18 May 2014 00:52:13 +0200, Pali Rohár wrote:
> > Do you know if there is any way to extract BIOS SMM code? Or
> > it is something which is not possible to do from OS/kernel
> > side?
>
> If you download a BIOS update for your laptop from Dell, the
> SMM code is certainly somewhere in the binary blob which gets
> flashed to the EEPROM. But extracting that code from there
> would certainly be challenge.
Yes extracting it from bios flashing image was only idea which I
got and I doubt I can do it... (specially when dell bios is
compressed and image itself contains flashing program...)
What I now found is this table of SMM commands:
https://lkml.org/lkml/2008/12/18/44
So it looks like SMM data are in some NBSVC.MDM binary. Do you
know something more about it?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2014-05-18 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 8:19 [lm-sensors] Dell Latitude E6440 & i8k Jean Delvare
2014-05-18 8:36 ` Pali Rohár [this message]
2014-05-18 9:02 ` Jean Delvare
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=201405181036.16704@pali \
--to=pali.rohar@gmail.com \
--cc=lm-sensors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.