public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Yin Kangkai <kangkai.yin@linux.intel.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	"platform-driver-x86" <platform-driver-x86@vger.kernel.org>,
	linux-kernel@vger.kernel.org, "Wang,
	Yong Y" <yong.y.wang@intel.com>,
	"Liu, Bing Wei" <bing.wei.liu@intel.com>,
	Corentin Chary <corentin.chary@gmail.com>
Subject: Re: [PATCH V2] platform-driver-x86: ACPI EC Extra driver for Oaktrail
Date: Mon, 10 Jan 2011 10:16:50 +0100	[thread overview]
Message-ID: <201101101016.50662.trenn@suse.de> (raw)
In-Reply-To: <20110110071013.GJ30215@kai-debian>

...

> > Is any hardware actually going to ship with this identifier, or will 
> > vendors change the string?
> 
> 
> I think vendors and OEMs will change this string. But we can add the
> DMI_BOARD_NAME, DMI_BOARD_VERSION, etc. back later, can we?

I could imagine vendors will also build a higher level WMI, ACPI or
whatever interface on it (EC bits should not be accessed directly).
Compare with acer-wmi, hp-wmi, platformXY-*, ...
They have their userspace tools/drivers in place for Windows and I
doubt they will add these EC bits there. Instead I expect they will
use the same API which works for their other platforms and add some
ACPI code to glue the EC bits with their (depending on vendor mostly
ACPI based) their Windows laptop driver.
We also have these drivers (re-engineered or implemented by the vendors)
which would result in double HW access.

If this driver can only be loaded on the Intel systems..., but what
would happen if you try to load this one together with the platformXY-
driver on a sold system which provides another mechanism to access this
functionality?

Hm, googling for the oaktrail platform, it seem to be a bit special..,
but as Windows7 runs on it, I do not see why above cannot/will not
happen.

   Thomas

  reply	other threads:[~2011-01-10  9:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06  2:59 [PATCH] platform-driver-x86: ACPI EC Extra driver for Oaktrail Yin Kangkai
2011-01-06  7:29 ` Corentin Chary
2011-01-06 10:11   ` Yin Kangkai
2011-01-06 10:21     ` Corentin Chary
2011-01-06 10:50   ` Yin Kangkai
2011-01-06 10:54     ` Corentin Chary
2011-01-06 11:32       ` Joey Lee
2011-01-06 11:35         ` Joey Lee
2011-01-07  0:01         ` Yin Kangkai
2011-01-07  7:41 ` [PATCH V2] " Yin Kangkai
2011-01-07  8:56   ` Corentin Chary
2011-01-07 11:24     ` Yin Kangkai
2011-01-10  6:57       ` Yin Kangkai
2011-01-07 22:09   ` Matthew Garrett
2011-01-10  7:10     ` Yin Kangkai
2011-01-10  9:16       ` Thomas Renninger [this message]
2011-01-10  7:15 ` [PATCH V3] platform-driver-x86: " Yin Kangkai

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=201101101016.50662.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=bing.wei.liu@intel.com \
    --cc=corentin.chary@gmail.com \
    --cc=kangkai.yin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=yong.y.wang@intel.com \
    /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