Re: [PATCH V2] platform-driver-x86: ACPI EC Extra driver for Oaktrail

[Thomas Renninger]

...

> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/