[PATCH linux] added i2c busses and devices for palmetto and barreleye
Norman James
njames at us.ibm.com
Sat Oct 31 09:07:44 AEDT 2015
Fine with me.
Regards,
Norman James
IBM - POWER Systems Architect
Phone: 1-512-286-6807 (T/L: 363-6807)
Internet: njames at us.ibm.com
From: Patrick Williams <patrick at stwcx.xyz>
To: OpenBMC Patches <patches at stwcx.xyz>
Cc: openbmc at lists.ozlabs.org
Date: 10/30/2015 02:34 PM
Subject: Re: [PATCH linux] added i2c busses and devices for palmetto and
barreleye
Sent by: "openbmc" <openbmc-bounces+njames=us.ibm.com at lists.ozlabs.org>
On Fri, Oct 30, 2015 at 01:52:24PM -0500, OpenBMC Patches wrote:
> i'm not sure compatibility string is correct for barreleye
>
> https://github.com/openbmc/linux/pull/10
>
> Norman James (1):
> added i2c busses and devices
>
> arch/arm/boot/dts/aspeed-bmc-opp-barreleye.dts | 333 +++++++++++++++++++
++++++
> arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 28 ++-
> 2 files changed, 354 insertions(+), 7 deletions(-)
> create mode 100644 arch/arm/boot/dts/aspeed-bmc-opp-barreleye.dts
>
> --
> 2.6.0
>
>
> _______________________________________________
> openbmc mailing list
> openbmc at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
In general where should we put the devtree files? Seems like these
belong in meta-phosphor-machines instead of directly in the linux tree.
If there is no disagreement I can open an issue to track moving these.
--
Patrick Williams
[attachment "signature.asc" deleted by Norman James/Austin/IBM]
_______________________________________________
openbmc mailing list
openbmc at lists.ozlabs.org
https://lists.ozlabs.org/listinfo/openbmc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20151030/f06709fd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20151030/f06709fd/attachment.gif>
More information about the openbmc
mailing list