<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Thanks for your reply, it clarifies the main idea for me.<br><br>2016-03-17 23:56 GMT+02:00 Martin Roth <span dir="ltr"><<a href="mailto:gaumless@gmail.com" target="_blank">gaumless@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Sorry it's taken a while to get back to you on this.</div><div><br></div>The build needs to happen with the correct toolchain to generate a rom that is similar (or identical) to the original rom that was tested in the board status. That would be done with with 'make crossgcc'. If I try to build a rom that was submitted 8 months ago, I'd want to use the toolchain that was in use 8 months ago, not today's toolchain.<div></div></div></blockquote><div><br></div><div>So I need to came up with some mechanism to store multiple toolchain version. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Boards that are in the board status repo: </div><div><a href="https://review.coreboot.org/gitweb/cgit/board-status.git/tree/amd" target="_blank">https://review.coreboot.org/gitweb/cgit/board-status.git/tree/amd</a><br></div><div>These are boards that have been tested. These submissions are known to at least boot (with the configuration that was used to test the rom).<br></div><div><br></div><div>Any valid board:</div><div><a href="https://review.coreboot.org/gitweb/cgit/coreboot.git/tree/src/mainboard/amd" target="_blank">https://review.coreboot.org/gitweb/cgit/coreboot.git/tree/src/mainboard/amd</a><br></div><div>The source code for these boards is in the codebase, but we have no way of knowing whether it's currently booting or not until we actually test it.</div></div></blockquote><div> </div><div>Did I understand correctly, that there is no possibility to automatically test all these boards, because they require specific hardware, which can't be emulated? So, if user wants to build and flash one, he takes all responsibility?<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>As the project proposal says, first we want to just build roms that are already present in the board status database. We have a config already present for these, so we don't need to ask any configuration options at all, just give them a list of boards that they can build a rom for. We also don't need to give users every option available in Kconfig. Maybe we give them an edit window that they can paste a config into or edit an existing config.</div></div></blockquote><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>The preference would be to do everything on the server or in the browser though. We would really prefer not to have any scripts that need to be run on the user's system.</div></div></blockquote><div><br></div><div>I strongly agree about this. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span class=""><font color="#888888"><div><br></div><div>Martin</div><div><br></div></font></span></div><div class=""><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 17, 2016 at 3:35 PM, ron minnich <span dir="ltr"><<a href="mailto:rminnich@gmail.com" target="_blank">rminnich@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><span><div dir="ltr">On Thu, Mar 17, 2016 at 2:33 PM Yurii Shevtsov <<a href="mailto:ungetch@gmail.com" target="_blank">ungetch@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I can't see any other way, it's all about running the commands. Browsers can't do this. Certain actions are still required from user. Some shell script, which will run commands and then send stdout to the server, can be developed though.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><span><font color="#888888"><div><br></div></font></span></div></div></blockquote></div></div></div></blockquote><div><br></div><div><br></div></span><div>the board-status script can send the ref and the configuraiton. </div><div><br></div><div>That's not part of rom-o-matic. </div><div><br></div><div>Further, tools at <a href="http://coreboot.org" target="_blank">coreboot.org</a> and create the tables whih rom-o-matic uses to present choices to the user. </div><div><br></div><div>That's what I was wondering, anyway.</div><span><font color="#888888"><div><br></div><div>ron </div></font></span></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>