From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mario.Limonciello@dell.com
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Dell docking station & Dell Embedded Controller & PS/2 devices
Date: Mon, 7 May 2018 22:48:51 +0200 [thread overview]
Message-ID: <20180507204851.6y4rplcka4inzhsl@pali> (raw)
In-Reply-To: <05cd71987d8f4a8e99cb1994218a8485@ausx13mpc124.AMER.DELL.COM>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On Monday 07 May 2018 20:32:16 Mario.Limonciello@dell.com wrote:
> > The items that show up in this structure are supposed to be dynamic
> > values but static addresses. I was asking to check before bootup in
> > case this was a problem of Linux caching SMBIOS table information once.
> > The values I was referring to might be for older generation dock though,
> > I'll see if I can find anything else you can check.
>
> Can you check if structure type 08 or structure type 09 change based on
> dock being plugged in? Again you might have to do it across a boot
> with/without dock in case of Linux kernel caches values.
The only difference is:
--- dmidecode_laptop_docked 2018-05-07 22:34:02.650325758 +0200
+++ dmidecode_laptop_undocked 2018-05-07 22:39:27.580306838 +0200
@@ -913,7 +913,7 @@ System Power Supply
Asset Tag: To Be Filled By O.E.M.
Model Part Number: To Be Filled By O.E.M.
Revision: To Be Filled By O.E.M.
- Max Power Capacity: 90 W
+ Max Power Capacity: Unknown
Status: Present, OK
Type: Switching
Input Voltage Range Switching: Auto-switch
And this is in block Handle 0x003E, DMI type 39, 22 bytes - System Power
Supply. So looks like that DMI data are same.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2018-05-07 20:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 10:41 Dell docking station & Dell Embedded Controller & PS/2 devices Pali Rohár
2018-02-01 19:29 ` Dmitry Torokhov
2018-02-01 19:35 ` Mario.Limonciello
2018-02-01 21:14 ` Dmitry Torokhov
2018-02-01 21:23 ` Mario.Limonciello
2018-02-04 20:07 ` Pali Rohár
2018-05-06 13:47 ` Pali Rohár
2018-05-07 8:44 ` Pali Rohár
2018-05-07 19:33 ` Dmitry Torokhov
2018-05-07 19:58 ` Pali Rohár
2018-05-07 19:59 ` Mario.Limonciello
2018-05-07 20:07 ` Pali Rohár
2018-05-07 20:18 ` Mario.Limonciello
2018-05-07 20:28 ` Pali Rohár
2018-05-07 20:30 ` Mario.Limonciello
2018-05-07 20:32 ` Mario.Limonciello
2018-05-07 20:48 ` Pali Rohár [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:
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=20180507204851.6y4rplcka4inzhsl@pali \
--to=pali.rohar@gmail.com \
--cc=Mario.Limonciello@dell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 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).