March 2016 - coreboot - mail.coreboot.org

Typo in util/crossgcc/buildgcc
by Yurii Shevtsov March 11, 2016

March 11, 2016

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

1 0

QEMU x86_64 Q35 Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand March 11, 2016

March 11, 2016

The QEMU x86_64 Q35 fails verification for branch master as of commit The following tests failed: BOOT_FAILURE Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem 1e70cda soc/intel/apollolake: Avoid UART BAR relocation at ramstage e953dce soc/intel/apollolake: Add ids of internal SoC PCI devices <172 commits skipped> a95baf9 device: Add device path display support 800e964 arch/arm64: Compile arm-trusted-firmware with coreboot timestamp 21111be intel/kunimitsu: Set USB Type A current limit to 2A 9f54297 board_status.sh: Be smarter about cbfstool usage f43e51d board_status: Add script that will set up a ubuntu live image See attached log for details This message was automatically generated from Raptor Engineering's QEMU x86_64 Q35 test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

3 2

ASUS KFSN4-DRE (K8) Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand March 11, 2016

March 11, 2016

The ASUS KFSN4-DRE (K8) fails verification for branch master as of commit c7a1a3e994135bb405662e2f52d0b22efa899c3d The following tests failed: BOOT_FAILURE Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE (K8) test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

2 1

ASUS KGPE-D16 Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand March 11, 2016

March 11, 2016

The ASUS KGPE-D16 fails verification for branch master as of commit c7a1a3e994135bb405662e2f52d0b22efa899c3d The following tests failed: BOOT_FAILURE Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem See attached log for details This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

ASUS KFSN4-DRE Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand March 11, 2016

March 11, 2016

The ASUS KFSN4-DRE fails verification for branch master as of commit c7a1a3e994135bb405662e2f52d0b22efa899c3d The following tests failed: BOOT_FAILURE Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

GSoC proposal
by Haran Sivaram March 10, 2016

March 10, 2016

Hello CoreBoot, Loved reading about what you do and hoping I'd get a chance to help with it. I'd started programming pretty late in highschool, around the time I was 15-16 years old. Once I got into college 2 years later was when I really started getting into programming. In college I first got into a robotics automation and building team that participates in RoboCon in every year. I was primarily working with interfacing components like sensors, encoders, communication modules to arduino and avr boards. Majority of my knowledge with hardware and firmware stems from here. Later on I moved into android app development and have done multiple projects ranging from freelance, my own projects and interning with app based startups. My contribution to open source code is something I'm quite ashamed of. Though I feel like I have worked on projects(apps) which would do really well on the OS platforms, I cannot put the code up as the organisations I built these apps for are trying to start a business with it. My own projects comprise of libraries put together to make life a little easier for users, so not really worth open source mention. The idea I would like to propose to you isn't something that would fall completely into your field of work, but a company like this could really help build the technology needed. As an overview it's a way for an individual to talk to his/her car, preferably using a smart phone or a dash board interface, to not only read car info but also to remap the ECU of the car and to control a variety of the electronic components in the vehicle. I had worked individually using an arduino board plugged into a 9pin car On Board Diagnostics (OBD) port. Using a Bluetooth module I relayed information from my ardunio board to my Android device, but my more ambitious plans required better technology and more insight into the operating system of the car. I hope that gives you brief idea about me and what I want to do, waiting to hear from you. -- Regards Haran Sivaram

1 0

Re: [coreboot] [GSoC 2016] ROM-O-Matic project
by Peter Stuge March 10, 2016

March 10, 2016

Hi guys, (I have a server problem but am sortof recovering.) ron minnich wrote: > Do we have any record as to how uniform, e.g., the x220 experience > has been? This is an important question. It comes down to the mainboard of course. Judging from the schematics and hardware in the wild there's not too much variation with ThinkPads; the *only* significant variation in the (admittedly very) old 60 generation is whether a mainboard has discrete graphics or not, and even then that only matters for using the correct option ROM. There might be a bit more variation with newer generations because they are more complex, but not too much. //Peter

1 0

Re: [coreboot] [GSoC 2016] ROM-O-Matic project
by Alexander Couzens March 9, 2016

March 9, 2016

On Wed, 09 Mar 2016 22:30:44 +0000 ron minnich <rminnich(a)gmail.com> wrote: > That's great to hear. So it sounds like rom o matic would be handy. > > That said, w.r.t. features. I'm not big on features. coreboot is a > chance to brick your laptop. That means > rom o matic should never ever ever give you a bad coreboot image. > What would be cool would be to have a program they can run that > creates a string, and the either you paste > that string into a form or it connects and pastes it in (but what > about DDOS?) and you get back a URL for an image > that is known to work. Could the coreboot board status repo be used to > determine this? > > I think the messy part is that just because you have, say, an "x220", > doesn't mean coreboot works on it, because PCs > are never the same, even given the same number. So you need a very > long signature that can confirm the coreboot > running on everyone else's "x220" will work on yours. > > Do we have any record as to how uniform, e.g., the x220 experience has > been? I know the chromebook uniformity is pretty good. They are uniform, beside the case of the spi. Most x220 have a spi in a SOIC8, but some have a WSON or mlp8 case. I had problems with my x220 because I desolered the wson chip and soldered a SOIC8 which wasn't quite supported by coreboot. I say the "normal" coreboot user wouldn't do that ;). They only use a clip. Best, lynxis -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604

1 0

Re: [coreboot] [GSoC 2016] ROM-O-Matic project
by Alexander Couzens March 9, 2016

March 9, 2016

On Wed, 09 Mar 2016 20:57:23 +0000 ron minnich <rminnich(a)gmail.com> wrote: > 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 I know a lot people who don't know or have problems compiling coreboot on their own or they don't want to spent hours to compiling the toolchain + coreboot. For these people rom-o-matic is a nice thing. German hacker culture likes coreboot a lot. Last coreboot user group meeting a journalist showed up. Someone spent her a x60 and she would like to have coreboot on it. But after disassembling the hardware down to the board itself, it turns out, she already got coreboot. I never looked at the x60 bios booting up :). There are also the cryptoparty people, they also support coreboot. zaolin is doing installation partys at his hackerspace, too. And may others do the same. -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604

2 1

Re: [coreboot] [GSoC 2016] ROM-O-Matic project
by ron minnich March 9, 2016

March 9, 2016

On Wed, Mar 9, 2016 at 4:16 AM Yurii Shevtsov <ungetch(a)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

1 0