Re: [coreboot] [GSoC 2016] Proposal review

[Yurii Shevtsov]

I'm not complaining. I'm just worrying, only two days left till submission
deadline, and, who knows, maybe people forget. I'll be patient

2016-03-23 20:55 GMT+02:00 ron minnich :

> you need to be patient. All the reviewers have day jobs and there is a lot
> of work in all this.
>
> There's no advantage to you or your proposal in complaining about the
> reviewers, I think.
>
>
Thanks for you reply. I'm not complaining. I'm just worrying, only two days
left till submission deadline, and, who knows, maybe people forget.

> ron
>
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

2016-03-17 22:13 GMT+02:00 ron minnich :

>
>
> On Thu, Mar 17, 2016 at 1:08 PM Denis 'GNUtoo' Carikli 
> wrote:
>
>>
>> Once we get reproducible builds, we could:
>> 1) Store an (SHA) hash of images in board-status.
>> 2) Make the rom-o-matic build (with the board-status configs) and
>>verify(checksums) the image of a known good state.
>>
>>
>>
>
> I really like this idea. I wonder if we could add additional information
> for a board, derived from, say, pci tree, dmidecode, that kind of thing,
> that would be used to characterize a board.
>
> ron
>

I like it too. Maybe we can ask users on rom-o-matic to provide neccesary
info for further project improvement
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] Proposal review

[Yurii Shevtsov]

Hello. Three days passed, but unfortunately I haven't got any feedback on
my draft yet. Although, I can see Martin Roth is watching my proposal. Also
I'm still not assigned to any task. Spare me some time, please :-)
Thanks in advance

2016-03-14 23:11 GMT+02:00 Yurii Shevtsov <unge...@gmail.com>:

> I know we haven't discussed project properly yet, and I understand my
> vision of project may vary from yours. So feel free to point me on a right
> way :-)
> Here is the link:
>
> https://docs.google.com/document/d/1OWOYfKMUSZTi4tTHmGIIY27KAbM5MJVV0DdirjpB2As/edit?usp=sharing
>
> I made my proposal draft private. As for now I shared it with Ron Minnich
> and Martin Roth. If you part of a GSoC commission, I'll add you too (head
> to the doc link).
>
> Unfortunately, I haven't submitted any patch yet. Please, assign me to a
> task.
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

2016-03-17 22:57 GMT+02:00 ron minnich <rminn...@gmail.com>:

>
>
> On Thu, Mar 17, 2016 at 1:30 PM Yurii Shevtsov <unge...@gmail.com> wrote:
>
>>
>>
>>>
>> I like it too. Maybe we can ask users on rom-o-matic to provide neccesary
>> info for further project improvement
>>
>
> no, it has to be automated or it won't work.
>

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.

> ron
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] Proposal review

[Yurii Shevtsov]

2016-03-17 23:00 GMT+02:00 David Hendricks <dhend...@google.com>:

>
> On Thu, Mar 17, 2016 at 1:39 PM, Yurii Shevtsov <unge...@gmail.com> wrote:
>
>> Hello. Three days passed, but unfortunately I haven't got any feedback on
>> my draft yet.
>>
>
> If you make the doc public then you might get more responses.
>

David, you convinced me. Thanks for your advice. Now it's public!
https://docs.google.com/document/d/1rxKXzbaq9w4EthVIP2O5mqXaTJTzK3IKsnbVOWvstVI/edit?usp=sharing

>
> Martin and Ron are both very busy people and might simply have been too
> busy with work this week.
>
> GSOC is all about open source coding and community engagement. Keeping
> your doc private is not a good way to start...
>
>
>> Although, I can see Martin Roth is watching my proposal. Also I'm still
>> not assigned to any task. Spare me some time, please :-)
>> Thanks in advance
>>
>> 2016-03-14 23:11 GMT+02:00 Yurii Shevtsov <unge...@gmail.com>:
>>
>>> I know we haven't discussed project properly yet, and I understand my
>>> vision of project may vary from yours. So feel free to point me on a right
>>> way :-)
>>> Here is the link:
>>>
>>> https://docs.google.com/document/d/1OWOYfKMUSZTi4tTHmGIIY27KAbM5MJVV0DdirjpB2As/edit?usp=sharing
>>>
>>> I made my proposal draft private. As for now I shared it with Ron
>>> Minnich and Martin Roth. If you part of a GSoC commission, I'll add you too
>>> (head to the doc link).
>>>
>>> Unfortunately, I haven't submitted any patch yet. Please, assign me to a
>>> task.
>>>
>>
>>
>> --
>> coreboot mailing list: coreboot@coreboot.org
>> https://www.coreboot.org/mailman/listinfo/coreboot
>>
>
>
>
> --
> David Hendricks (dhendrix)
> Systems Software Engineer, Google Inc.
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

Thanks for your reply, it clarifies the main idea for me.

2016-03-17 23:56 GMT+02:00 Martin Roth <gauml...@gmail.com>:

> Sorry it's taken a while to get back to you on this.
>
> 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.
>

So I need to came up with some mechanism to store multiple toolchain
version.

> Boards that are in the board status repo:
> https://review.coreboot.org/gitweb/cgit/board-status.git/tree/amd
> 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).
>
> Any valid board:
> https://review.coreboot.org/gitweb/cgit/coreboot.git/tree/src/mainboard/amd
> 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.
>

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?

> 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.
>


> 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.
>

I strongly agree about this.

>
> Martin
>
>
> On Thu, Mar 17, 2016 at 3:35 PM, ron minnich <rminn...@gmail.com> wrote:
>
>>
>>
>> On Thu, Mar 17, 2016 at 2:33 PM Yurii Shevtsov <unge...@gmail.com> wrote:
>>
>>>
>>> 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.
>>>
>>>>
>>>>
>>
>> the board-status script can send the ref and the configuraiton.
>>
>> That's not part of rom-o-matic.
>>
>> Further, tools at coreboot.org and create the tables whih rom-o-matic
>> uses to present choices to the user.
>>
>> That's what I was wondering, anyway.
>>
>> ron
>>
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

I admit, I oversimplified. Build server have much more advanced features.
But user still needs to configure ROM, like nconfig/menuconfig prompts, as
a first step, isn't it? Also, why would server need to rebuild toolchain,
isn't crossgcc alone enough? What is the difference between "boards listed
in board-status repository" and "any valid board", what is meant by these
terms?

2016-03-12 7:41 GMT+02:00 ron minnich <rminn...@gmail.com>:

>
>
> On Fri, Mar 11, 2016 at 5:28 PM Yurii Shevtsov <unge...@gmail.com> wrote:
>
>> But personally I think it's fun. Also, now I understand, that rom-o-matic
>> should be web-version of nconfig/menuconfig
>>
>>
>
> I'm not sure that's quite right. But we can talk. You definitely know what
> you are doing at this point :-)
>
> ron
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

Proof of running rom file:
http://pastebin.com/P2WzyTQ8

While I was going through building process, I got quite a view of how
inconvenient it can be - setting the whole building environment, waiting
toolchain compilation. But personally I think it's fun. Also, now I
understand, that rom-o-matic should be web-version of nconfig/menuconfig

BTW, I occasionally found student requirements on GSoC mentors page. And
I'm asking for a simple task)

2016-03-09 22:57 GMT+02:00 ron minnich <rminn...@gmail.com>:

> On Wed, Mar 9, 2016 at 4:16 AM Yurii Shevtsov <unge...@gmail.com> wrote:
>
>> I looked at sites you mentioned. I haven't any configuration feature on
>> johnlewis.ie Instead it provides an instruction for running special
>> shell script. But I much more liked original Rom-o-matic. I want do develop
>> same thing, but with fancier design, if you mind) I have more questions:
>>
>> How important this project for coreboot community is?
>>
>
> well, that's a tough question. Back in 2000 when we first did it, it was
> very important. At this point, coreboot is mostly two user communities:
> people who use it and don't know and don't care (chromebooks); and people
> who are dedicated hackers and know the insides so well they don't need
> rom-o-matic. Those who don't know anything and don't care they're using
> coreboot probably outnumber knowledgable people by about 10,000 to 1 at
> least [based on the 10m+ systems shipped at this point with coreboot, and
> my guess that the coreboot hacker community is unlikely to be as many as
> 1000 people).
>
> The number of people who don't know anything and can use a rom-o-matic is
> probably numbered in single digits, because even to use rom-o-matic you
> have to be knowledgable enough that you might as well build your own
> coreboot. You certainly have to have a path out if something goes wrong,
> and at that point you are cracking open your laptop. A failed coreboot
> install is not like a failed OS install. It's more like destroying your
> mainboard.
>
> I hate to be discouraging but my guess is at present that what john lewis
> is doing is probably as much as is needed.
>
>
> Do I have to fix some bugs or make any other sort of contribution, before
>> submitting my proposal?
>>
>
> You should show that you know how to build and use coreboot from scratch.
> It makes no sense to talk about rom-o-matic otherwise.
>
>
>> Do you have a proposal template or some special requirments for it?
>> What do you think about nodejs, as a backend?
>>
>
>
> I suspect you know far more about writing such a tool than I ever will,
> but far less about coreboot than you need to know. Your first step should
> be to get it, build it, and boot it in qemu; bonus points for doing it on
> real hardware.
>
> I think the choice of node.js is not nearly as important as ensuing you
> give people images that won't brick their machine.
>
> ron
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] Typo in util/crossgcc/buildgcc

[Yurii Shevtsov]

Yeah, I found typo in the shell script. Took me a while to find.

347th line lacks ending quote

I know, I should better submit patch straightaway, but I'm on the building
phase. After building, I'm going to read all patch submitting guidelines
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

I looked at sites you mentioned. I haven't any configuration feature on
johnlewis.ie Instead it provides an instruction for running special shell
script. But I much more liked original Rom-o-matic. I want do develop same
thing, but with fancier design, if you mind) I have more questions:

How important this project for coreboot community is?
Do I have to fix some bugs or make any other sort of contribution, before
submitting my proposal?
Do you have a proposal template or some special requirments for it?
What do you think about nodejs, as a backend?

Thanks in advance!

2016-03-09 6:24 GMT+02:00 ron minnich <rminn...@gmail.com>:

> yeah, we had something like this in the linuxbios days. I think you don't
> want to build it on demand, but rather have a bunch of pre-built images
> that are known good.
>
> Really, look at johnlewis.ie, that's the best thing I've seen. Have you
> also seen the original Rom-o-matic from the etherboot (now gpxe or ipxe)
> project?
>
> ron
>
> On Tue, Mar 8, 2016 at 7:35 PM Yurii Shevtsov <unge...@gmail.com> wrote:
>
>> Hello) I want to be a GSoC 2016 student. I really liked the idea of
>> ROM-O-Matic project. Also it's a nice name. So, as I understood, the end
>> user should get a website with a ROM configurator and a big 'Download'
>> button, right?
>>
>> I'm student of Odessa polytechnic university, computer science. I have a
>> good as for student experience in system and web programming
>> --
>> coreboot mailing list: coreboot@coreboot.org
>> https://www.coreboot.org/mailman/listinfo/coreboot
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] [GSoC 2016] ROM-O-Matic project

[Yurii Shevtsov]

Hello) I want to be a GSoC 2016 student. I really liked the idea of
ROM-O-Matic project. Also it's a nice name. So, as I understood, the end
user should get a website with a ROM configurator and a big 'Download'
button, right?

I'm student of Odessa polytechnic university, computer science. I have a
good as for student experience in system and web programming
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot