How to power on Intel x86 based CPUs

[Patrick Venture]

On Fri, Apr 13, 2018 at 10:53 AM, Nancy Yuen <yuenn at google.com> wrote:
> Patrick Venture uses the q71l and may be able to answer #2.  I suspect it
> was removed simply b/c the system we were using it on didn't use it.
>
> ----------
> Nancy
>
> On Fri, Apr 13, 2018 at 2:43 AM, Brad Chou <chou.brad at gmail.com> wrote:
>>
>> Hi,
>> Actually I am using the meta-s2600wf as my TEMPLATECONF.
>> Now switch to Q71L but found some problems :
>>
>> 1. I can not send the same REST command to power up the host. It seems the
>> xyz/openbmc_project/state/host0/attr/RequestedHostTransition
>> is gone. I even can’t see any attributes related to
>> xyz/openbmc_project/state.
>>
>> 2. I found in quanta-q71l.conf, it remove the obmc-host-state-mgmt, this
>> may be needed when using REST to power on host. Why q71L remove it ?  Is it
>> because of not compatible with x86 system ?

We didn't require it.  There was nothing wired up to it for us.  One
could conceivably wire up the power-on script stuff.

>>
>> 3. Suppose the REST is not used by Q71L, how can I power it up from LAN ?
>>
>> Thanks.
>>
>>
>> On Apr 10, 2018, at 21:36, Andrew Jeffery <andrew at aj.id.au> wrote:
>>
>> Hi Brad,
>>
>> On Tue, 10 Apr 2018, at 19:35, Brad Chou wrote:
>>
>> Hi,
>> I am going to power on my OEM server board with two Intel x86 CPUs. The
>> BMC chip is ASPEED 2500.
>>
>> By the Intel data sheets, I just need to control a power on GPIO to
>> emulate power button behavior.
>> The problems are, when I send Host State Control commands as mentioned
>> in docs/host-management.md, the journal log shows a lot of systemctl
>> errors.
>>
>> Looks like it is going to start the OpenPower related host control
>> services, which only applies to PowerPC system.
>> I try to modify GPIO_CONFIGS appears in skeleton recipe to match my
>> board, but I still got some other errors says pflash stuffs.
>>
>>
>> It sounds like you're building an OpenPOWER-based BMC image - this is
>> controlled by how you set the TEMPLATECONF environment variable when
>> sourcing the `openbmc-env` file to build (at a guess I'd say you're building
>> for Palmetto, as it's used throughout the examples in the docs repo).
>>
>> We do have support for a couple of x86 machines in the tree - your best
>> bet is probably the Quanta 71L machine maintained by Patrick Venture:
>>
>>
>> https://github.com/openbmc/openbmc/tree/master/meta-openbmc-machines/meta-x86/meta-quanta/meta-q71l
>>
>> As an aside, if you're experimenting and switching between target
>> machines, it's probably a good idea to blow away your build/conf directory
>> to make sure things get set up correctly when you next set TEMPLATECONF and
>> source openbmc-env.
>>
>>
>> Because there is no documents to tell me how to customize the openbmc to
>> fit on x86 CPUs, so I am not sure the GPIO_CONFIGS in skeleton is the
>> right way or not.
>>
>>
>> Yeah, there's not a wealth of documentation on bringing up a new machine.
>> It would be great if you could document your experience once you get there
>> :)
>>
>> Hope that helps in some way,
>>
>> Andrew
>>
>>
>