<html><body><p><tt><font size="2">"openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org> wrote on 06/08/2017 02:10:26 AM:<br><br>> From: Joel Stanley <joel@jms.id.au></font></tt><br><tt><font size="2">> To: Patrick Venture <venture@google.com></font></tt><br><tt><font size="2">> Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org></font></tt><br><tt><font size="2">> Date: 06/08/2017 02:11 AM</font></tt><br><tt><font size="2">> Subject: Re: New Platform Guide</font></tt><br><tt><font size="2">> Sent by: "openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org></font></tt><br><tt><font size="2">> <br>> Hi Patrick,<br>> <br>> On Thu, Jun 8, 2017 at 3:48 AM, Patrick Venture <venture@google.com> wrote:<br>> > Where is the new platform guide?<br>> ><br>> > In trying to get the quanta board running with everything; I've often run<br>> > into stumbling blocks when trying to define what packages are required and<br>> > what need to be replaced with custom versions -- for things like sensors.<br>> ><br>> > Often I've been more or less reduced to checking the journal logs to see if<br>> > something is saying why it's not running (settings.py was crashing which<br>> > meant ipmid wouldn't start as an example). It took some source searching to<br>> > figure out that x really depended on some object existing. Often those were<br>> > in the service file, but not every time. And especially as OpenBMC is a<br>> > moving target, this has been somewhat discouraging. Especially when the<br>> > "supported" platforms all stem from the skeleton which still has its fingers<br>> > in many places.<br>> <br>> As an end-user of the userspace who does not grok the systemd part of<br>> OpenBMC, I also find it hard to navigate. I look forward to<br>> improvements in this area.<br>> <br>> ><br>> > That said, there are a lot of dependencies between packages, and things that<br>> > you receive that maybe you don't want or need or aren't configuredproperly.<br>> > For example, I don't know why or what the led-manager is doing but it's on<br>> > my system running. I don't believe I configured it.<br>> ><br>> > If there is a guide, then I didn't see it and I apologize.<br>> ><br>> > If there isn't a guide -- I can start one; however, I won't really have to<br>> > do it properly until some time in July. My approach would be, create a new<br>> > platform that mimics Zaius but under a different name and see what it takes<br>> > to output a similar image and what is really required -- although difficult<br>> > for me to test. So maybe a new Quanta image from scratch and see what's<br>> > running, and why and what things need to be configured.<br>> <br>> I would appreciate this too. Let me know if I can help out.<br>> <br>> Cheers,<br>> <br>> Joel<br>> <br></font></tt><br><tt><font size="2">No better time then the present... Add/edit as you see fit. Then we can at least assign some tasks out </font></tt><br><br><tt><font size="2">Goal for document: Allow an experienced engineering team to port existing hardware to OpenBMC</font></tt><br><tt><font size="2">Topics: </font></tt><br><tt><font size="2">- Yocto Layering to support your board</font></tt><br><tt><font size="2">- Does your hardware have supported device drivers</font></tt><br><tt><font size="2">- How to deal with non hwmon supported devices</font></tt><br><tt><font size="2">- How to implement the default set of packages (thermal, inventory, ipmi, led, etc)</font></tt><br><tt><font size="2">- How to swapping a default package with a proprietary one</font></tt><br><tt><font size="2">- Adding packages</font></tt><br><tt><font size="2">- Testing against the OpenBMC verification suite</font></tt><br><br><BR>
</body></html>