<html><body><p>Unfortunately, there is quite a bit more to having OpenBMC support a given system (x86 or otherwise). Unless you got really lucky, the GPIO's on your x86 system likely do various other things than we do. A simple example, is we have a gpio to control the power sequencer to power on system. The x86 system might also use a gpio, but could be a different gpio or it might control power from southbridge. you would need a schematic of your system or reverse engineer the board to know.<br><br><br>Regards,<br>Norman James<br>IBM - POWER Systems Architect<br>Phone: 1-512-286-6807 (T/L: 363-6807)<br>Internet: njames@us.ibm.com<br><br><br><img width="16" height="16" src="cid:1__=09BBF58CDFEB6C458f9e8a93df938690918c09B@" border="0" alt="Inactive hide details for Nathan House ---12/18/2015 03:57:19 PM---Forwarding this here. Looking for a little guidance on io m"><font color="#424282">Nathan House ---12/18/2015 03:57:19 PM---Forwarding this here. Looking for a little guidance on io map definitions extracted from an x86 pla</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Nathan House <nathan.house@RACKSPACE.COM></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">12/18/2015 03:57 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Fwd: OpenBMC workshop agenda (was: "Fwd: Foxconn/Rackspace workshop agenda")</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">"openbmc" <openbmc-bounces+njames=us.ibm.com@lists.ozlabs.org></font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="4">Forwarding this here. Looking for a little guidance on io map definitions extracted from an x86 platform. </font><br><br><font size="4">Thanks!</font><br><br><font size="4"> Nate House</font><br><br>
<ul><ul><font size="4">Begin forwarded message:</font><br><br><b><font size="4">Subject: Re: OpenBMC workshop agenda (was: "Fwd: Foxconn/Rackspace workshop agenda")</font></b><br><b><font size="4">From: </font></b><font size="4">Nathan House <</font><a href="mailto:nathan.house@rackspace.com"><u><font size="4" color="#0000FF">nathan.house@rackspace.com</font></u></a><font size="4">></font><br><b><font size="4">Date: </font></b><font size="4">December 16, 2015 at 4:00:51 PM CST</font><br><b><font size="4">Cc: </font></b><font size="4">Adi Gangidi <</font><a href="mailto:adi.gangidi@rackspace.com"><u><font size="4" color="#0000FF">adi.gangidi@rackspace.com</font></u></a><font size="4">>, Kenneth Wilke <</font><a href="mailto:kenneth.wilke@RACKSPACE.COM"><u><font size="4" color="#0000FF">kenneth.wilke@RACKSPACE.COM</font></u></a><font size="4">>, Major Hayden <</font><a href="mailto:major.hayden@rackspace.com"><u><font size="4" color="#0000FF">major.hayden@rackspace.com</font></u></a><font size="4">>, Antony Messerli <</font><a href="mailto:amesserl@rackspace.com"><u><font size="4" color="#0000FF">amesserl@rackspace.com</font></u></a><font size="4">>, Norman James/Austin/IBM <</font><a href="mailto:njames@us.ibm.com"><u><font size="4" color="#0000FF">njames@us.ibm.com</font></u></a><font size="4">>, <</font><a href="mailto:jk@ozlabs.org"><u><font size="4" color="#0000FF">jk@ozlabs.org</font></u></a><font size="4">>, <</font><a href="mailto:causten@us.ibm.com"><u><font size="4" color="#0000FF">causten@us.ibm.com</font></u></a><font size="4">>, <</font><a href="mailto:pwilliams@us.ibm.com"><u><font size="4" color="#0000FF">pwilliams@us.ibm.com</font></u></a><font size="4">></font><br><b><font size="4">To: </font></b><font size="4">Aaron Sullivan <</font><a href="mailto:aaron.sullivan@rackspace.com"><u><font size="4" color="#0000FF">aaron.sullivan@rackspace.com</font></u></a><font size="4">></font><br><br><font size="4">Hey Guys, </font><br><br><font size="4">In my attempts to keep some momentum going following the workshop I was digging on one of our x86 platforms ast2400 vendor provided images. Looking for what needs to change to make a working image for them etc. I think with the dev address defs it would get half way if not more. Loaded their bmc fw bin into binwalk and discovered some interesting binary data that might have what is needed. Below is a gist of the contents which appear might be refs to addresses for different io and sensors. </font><br><br><a href="https://gist.github.com/naterh/c00caf9c940578eec138"><u><font size="4" color="#0000FF">https://gist.github.com/naterh/c00caf9c940578eec138</font></u></a><br><br><font size="4">What needs to be added to the skeleton to make this happen. I’m thinking it would need a new module in bin/ and maybe a bit of work in objects/ and its sub dirs. Outside of that project and looking at the existing working platforms, I was going to try to base off of palmetto and see where that gets me. Anything else I’m missing?</font><br><br><font size="4">Feel free to include or drop off anyone from this thread as some of the addresses might be incorrect. Was something I’d forgot to get before taking off. </font><br><br><font size="4">Thanks!</font><br><br><font size="4">Nate House</font><br><font size="4"> </font><ul><ul><font size="4">On Dec 10, 2015, at 2:52 PM, Aaron Sullivan <</font><a href="mailto:aaron.sullivan@rackspace.com"><u><font size="4" color="#0000FF">aaron.sullivan@rackspace.com</font></u></a><font size="4">> wrote:</font><br><br><font size="4">See below. Still might change, but just a bit.<br><br>Sent from my mobile</font><ul><ul><b><u><font size="4">Monday Dec 14th</font></u></b><font size="4"><br></font><b><font size="4"><br>Time Topic Details Presenter</font></b><font size="4"><br><br>9:00am 15 min Kickoff Intros, present objective, agenda Norm<br><br>9:15 45 min Dbus Dbus tutorial. </font><b><font size="4" color="#0000FF">Summarize bindings (python, sdbus, gdbus) </font></b><b><font size="4" color="#008000">Patrick or Norm?</font></b><font size="4" color="#0000FF"><br>Even though we aren't using gdbus, they will come across it<br>when searching and don't want any confusion</font><font size="4"><br><br>10:00 15 min Dbus and IPMI Highlight differences from IPMI, such as inventory vs sensors </font><b><font size="4" color="#0000FF">Norm</font></b><font size="4"><br><br>10:15 15 min BREAK<br><br>10:30 1 hr Dbus example Walk through a current dbus implementation </font><b><font size="4" color="#008000">Chris</font></b><font size="4"> <br><br>11:30 1.5 hr LUNCH<br><br>1:00pm 30 min Githup overview Review of the gihub repositories and what each contains </font><b><font size="4" color="#0000FF">Brad</font></b><font size="4"><br><br>1:30 1 hr Tree code struct Review of the openbmc tree code structure in yocto env </font><b><font size="4" color="#0000FF">Brad</font></b><font size="4"><br><br>2:30 15 min BREAK<br><br>2:45 1 hr Dbus objects Overview of all created dbus objects </font><b><font size="4" color="#008000">Whoever created the dbus object can talk for it</font></b><font size="4"><br><br>3:45 1hr Roundtable Questions to Foxconn/Rackspace, such as mfg tools,<br>how they provision their systems,<br>how their admins support the systems, access to root level<br>things on dbus such as flashing, should that be something clients have access to?<br>Any features they want us to work / focus on</font><b><font size="4" color="#008000"><br>NTP clock, MAC addresses, Rackspace's Ironic</font></b><font size="4"><br><br>4:45 15 min WRAP-UP Questions<br><br>5:00 END<br><br><br></font><b><u><font size="4"><br>Tuesday Dec 15th</font></u></b><font size="4"><br></font><b><font size="4"><br>Time Topic Details Presenter</font></b><font size="4"><br><br>9:00am 15 min Intro Agenda for the day <br><br>9:15 1 hr Hwmon Hwmon tutorial and overview of OCC driver </font><b><font size="4" color="#0000FF">Li Yi</font></b><font size="4"><br><br>10:15 15 min BREAK<br><br>10:30 45 min Kernel </font><b><font size="4" color="#0000FF">- Cover new kernel advantages, limitations, device tree overview - Jeremy</font></b><font size="4"><br><br>11:15 45 min Event logs Event logs and fru isolation strategy </font><b><font size="4" color="#0000FF">Chris</font></b><font size="4"><br><br>12:00 1 hr LUNCH<br><br>1:00pm 1 hr Rest How to access methods through REST </font><b><font size="4" color="#0000FF">Brad</font></b><font size="4"><br><br>2:00 15 min Rest advantages Show how seamlessly the REST implementation is </font><b><font size="4" color="#0000FF">Brad</font></b><font size="4"><br><br>2:15 15 min BREAK<br><br>2:30 1.5 hr Hands-on Write a dbus implementation (TBD) </font><b><font size="4" color="#008000">- System info (free text area)</font></b><font size="4"> </font><b><font size="4" color="#0000FF">Chris</font></b><font size="4"><br><br>4:00 30 min Future Where we're going next and where we're heading </font><b><font size="4" color="#008000">???</font></b><b><font size="4" color="#0000FF"><br>- Discuss x86 and maybe refactoring Facebook Openbmc<br>for Yosemite to dbus architecture and new kernel</font></b><font size="4"><br><br>4:30 30 min WRAP-UP Questions, workshop recap, conclusion<br><br>5:00 END<br><br></font><b><font size="4" color="#0000FF"><br>2 topics to add:<br>- Cover new kernel advantages, limitations, device tree overview - Jeremy<br>- Discuss x86 and maybe refactoring Facebook Openbmc for Yosemite to dbus architecture and new kernel</font></b><font size="4"><br><br><br><br></font></ul></ul><font size="4"><graycol.gif></font></ul></ul></ul></ul><tt>_______________________________________________<br>openbmc mailing list<br>openbmc@lists.ozlabs.org<br></tt><tt><a href="https://lists.ozlabs.org/listinfo/openbmc">https://lists.ozlabs.org/listinfo/openbmc</a></tt><tt><br></tt><br><BR>
</body></html>