coreboot January 2018

coreboot@coreboot.org

60 participants
155 discussions

Re: [coreboot] BDX-DE PCI init fail
by Zoran Stojsavljevic 03 Jan '18

03 Jan '18

Hello Hilbert, I am currently at job, so I do not have any time to look into it/into your maximal log, enabled now. Somebody from Google folks assigned to Coreboot might want to chime in. :-) I will look to your log later tonite. Thank you, Zoran On Wed, Jan 3, 2018 at 9:56 AM, Hilbert Tu(杜睿哲_Pegatron) <Hilbert_Tu(a)pegatroncorp.com> wrote: > Hi Zoran, > > I have changed to maximal log level and found SMBus init was failed when enabling clock gating. Do you have any comments about this? Thanks. > > -Hilbert > > -----Original Message----- > From: Hilbert Tu(杜睿哲_Pegatron) > Sent: Tuesday, January 02, 2018 9:41 AM > To: 'Zoran Stojsavljevic' > Cc: David Hendricks; coreboot(a)coreboot.org > Subject: Re: [coreboot] BDX-DE PCI init fail > > Hi Zoran, > > The log was just at following link: > http://mail.coreboot.org/pipermail/coreboot/attachments/20171227/b07eb74e/a… > With messages: > > MTRR check > Fixed MTRRs : Enabled > Variable MTRRs: Enabled > > By the way, I have tried to use U-Boot and Grub2 as payload, but I don't think the payload was executed since it failed at PCI 00:1f.3 init. > > -Hilbert > > -----Original Message----- > From: Zoran Stojsavljevic [mailto:zoran.stojsavljevic@gmail.com] > Sent: Saturday, December 30, 2017 2:32 PM > To: Hilbert Tu(杜睿哲_Pegatron) > Cc: David Hendricks; coreboot(a)coreboot.org > Subject: Re: [coreboot] BDX-DE PCI init fail > >> I still have same issue even tried to comment out the 1f.3 device in >> ./src/mainboard/intel/camel- backmountain_fsp/devicetree.cb then >> rebuild coreboot. > > You wrote that you submitted the log. Is this the full log? I doubt. I do NOT see physical memory layout as well as MTRR layout. > > Could you, please, submit the full/complete log? > > Which payload are you using? SeaBIOS? > > Thank you, > Zoran > > On Fri, Dec 29, 2017 at 5:58 AM, Hilbert Tu(杜睿哲_Pegatron) > <Hilbert_Tu(a)pegatroncorp.com> wrote: >> Hi David, >> >> >> >> Thanks for your information. >> >> I still have same issue even tried to comment out the 1f.3 device in >> ./src/mainboard/intel/camelbackmountain_fsp/devicetree.cb then rebuild >> coreboot. >> >> Could you let me know how to do that? >> >> >> >> -Hilbert >> >> >> >> From: David Hendricks [mailto:david.hendricks@gmail.com] >> Sent: Friday, December 29, 2017 9:46 AM >> To: Hilbert Tu(杜睿哲_Pegatron) >> Cc: coreboot(a)coreboot.org >> Subject: Re: [coreboot] BDX-DE PCI init fail >> >> >> >> Hi Hilbert, >> >> Have you had any luck? I have a board with a similar problem. >> Commenting out the entry for device 1f.3 in devicetree.cb seemed to >> help (I copied src/mainboard/intel/camelbackmountain_fsp for my project). >> >> >> >> On Wed, Dec 27, 2017 at 2:17 AM, Hilbert Tu(杜睿哲_Pegatron) >> <Hilbert_Tu(a)pegatroncorp.com> wrote: >> >> Hi, >> >> >> >> I am porting coreboot on Intel BDX-DE platform and it gets stuck when >> init PCI 00:1f.3. This device should be SMBus, serial management bus. >> But I don’t know why this happened. Does anyone can give me some hint? >> Attached is my boot up log. Thanks in advance. >> >> >> >> -Hilbert >> >> This e-mail and its attachment may contain information that is >> confidential or privileged, and are solely for the use of the >> individual to whom this e-mail is addressed. If you are not the >> intended recipient or have received it accidentally, please >> immediately notify the sender by reply e-mail and destroy all copies >> of this email and its attachment. Please be advised that any >> unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. >> 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件 >> 通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。 >> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot >> >> >> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot > This e-mail and its attachment may contain information that is confidential or privileged, and are solely for the use of the individual to whom this e-mail is addressed. If you are not the intended recipient or have received it accidentally, please immediately notify the sender by reply e-mail and destroy all copies of this email and its attachment. Please be advised that any unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. > 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。

1 0

Re: [coreboot] BDX-DE PCI init fail
by Hilbert Tu(杜睿哲_Pegatron) 03 Jan '18

03 Jan '18

Hi Zoran, I have changed to maximal log level and found SMBus init was failed when enabling clock gating. Do you have any comments about this? Thanks. -Hilbert -----Original Message----- From: Hilbert Tu(杜睿哲_Pegatron) Sent: Tuesday, January 02, 2018 9:41 AM To: 'Zoran Stojsavljevic' Cc: David Hendricks; coreboot(a)coreboot.org Subject: RE: [coreboot] BDX-DE PCI init fail Hi Zoran, The log was just at following link: http://mail.coreboot.org/pipermail/coreboot/attachments/20171227/b07eb74e/a… With messages: MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled By the way, I have tried to use U-Boot and Grub2 as payload, but I don't think the payload was executed since it failed at PCI 00:1f.3 init. -Hilbert -----Original Message----- From: Zoran Stojsavljevic [mailto:zoran.stojsavljevic@gmail.com] Sent: Saturday, December 30, 2017 2:32 PM To: Hilbert Tu(杜睿哲_Pegatron) Cc: David Hendricks; coreboot(a)coreboot.org Subject: Re: [coreboot] BDX-DE PCI init fail > I still have same issue even tried to comment out the 1f.3 device in > ./src/mainboard/intel/camel- backmountain_fsp/devicetree.cb then > rebuild coreboot. You wrote that you submitted the log. Is this the full log? I doubt. I do NOT see physical memory layout as well as MTRR layout. Could you, please, submit the full/complete log? Which payload are you using? SeaBIOS? Thank you, Zoran On Fri, Dec 29, 2017 at 5:58 AM, Hilbert Tu(杜睿哲_Pegatron) <Hilbert_Tu(a)pegatroncorp.com> wrote: > Hi David, > > > > Thanks for your information. > > I still have same issue even tried to comment out the 1f.3 device in > ./src/mainboard/intel/camelbackmountain_fsp/devicetree.cb then rebuild > coreboot. > > Could you let me know how to do that? > > > > -Hilbert > > > > From: David Hendricks [mailto:david.hendricks@gmail.com] > Sent: Friday, December 29, 2017 9:46 AM > To: Hilbert Tu(杜睿哲_Pegatron) > Cc: coreboot(a)coreboot.org > Subject: Re: [coreboot] BDX-DE PCI init fail > > > > Hi Hilbert, > > Have you had any luck? I have a board with a similar problem. > Commenting out the entry for device 1f.3 in devicetree.cb seemed to > help (I copied src/mainboard/intel/camelbackmountain_fsp for my project). > > > > On Wed, Dec 27, 2017 at 2:17 AM, Hilbert Tu(杜睿哲_Pegatron) > <Hilbert_Tu(a)pegatroncorp.com> wrote: > > Hi, > > > > I am porting coreboot on Intel BDX-DE platform and it gets stuck when > init PCI 00:1f.3. This device should be SMBus, serial management bus. > But I don’t know why this happened. Does anyone can give me some hint? > Attached is my boot up log. Thanks in advance. > > > > -Hilbert > > This e-mail and its attachment may contain information that is > confidential or privileged, and are solely for the use of the > individual to whom this e-mail is addressed. If you are not the > intended recipient or have received it accidentally, please > immediately notify the sender by reply e-mail and destroy all copies > of this email and its attachment. Please be advised that any > unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. > 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件 > 通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。 > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot > > > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot This e-mail and its attachment may contain information that is confidential or privileged, and are solely for the use of the individual to whom this e-mail is addressed. If you are not the intended recipient or have received it accidentally, please immediately notify the sender by reply e-mail and destroy all copies of this email and its attachment. Please be advised that any unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。

1 0

Re: [coreboot] How to properly conform with GPLv2 for Coreboot and SeaBIOS on an embedded system
by Lewis, Ian (Microstar Laboratories) 03 Jan '18

03 Jan '18

Hello Werner, > The way we decided to deal with the GPL-obligations is: Thank you for your detailed explanation of how you handle your GPL responsibilities. What you describe makes perfect sense to me. You have the advantage on us of having an output device on your system. And, since you run Linux your user base must be well aware of GPL. Still, the more I look at this, the more it sounds like we would meet our obligations if we provide an About tab in our control panel application, and from there present the license and provide a means to fetch the source code from our hardware, thus tying the source tightly with the firmware. Every user must have that application installed to be able to run our hardware at all no matter how they got the hardware. So, every user who ever had the device and had any ability to use it would have access to the About tab. Assuming this setup works for our responsibility, this also seems to free our customers from having to do anything to comply with GPL, though clearly we have to make them aware that our system contains GPL licensed code. I do have one question: You clearly have no issue for your compliance. But, do you tell your OEM customers that they need to provide the GPL license to their customers as part of their product packaging, or do you consider the availability of all the required information built into your system (in the screen you describe) sufficient to meet your OEM's responsibilities as well as your own as long as they do not add any new GPL licensed code that you have not handled? Ian

1 0

Re: [coreboot] Coreboot with an UEFI payload to boot (Clover) an Thinkpad X230 Hackintosh
by Zoran Stojsavljevic 02 Jan '18

02 Jan '18

> Are there people from Google company working on Coreboot ? YES, they are. GOOGLE employed most of the Coreboot designers and founders, hanging on this list. Practicaly GOOGLE got control over Coreboot project. > In order to get debug traces from my X230, should I use a EHCI Debug Port ? You should set your serial port on your X230 (I doubt you have it), or USB (EHCI is USB 2.0) port converted to serial tty0, which will show probably as /dev/ttyUSB0 on debug serial port on another machine (using for example Putty or Minicom as serial emulation terminals). Cable looks something like this (you need to figure it out what do you need at the serial end: male or female): https://www.staples.de/content/images/product/5869644_1_xnl.jpg Zoran On Tue, Jan 2, 2018 at 1:44 PM, my First name is Test And my last Name is iPation <testipation(a)live.com> wrote: > > > On 01/01/2018 20:23, Zoran Stojsavljevic wrote: > > > Here, (again), somebody from GOOGLE Coreboot folks should help you with this > transition (from DXE/Tiano Core to OS Boot Loader/GRUB2). OK? > > > Hi Zoran, I'm sorry if I don't really understand what you mean by "somebody > from GOOGLE Coreboot folks" > My english is a bit bad. > Are there people from Google company working on Coreboot ? > > > Or, you can also post some complete debug traces (from FSP till GRUB2 or > whatever), so me and/or somebody else should look into them, to see what is > going on here??? > > > In order to get debug traces from my X230, should I use a EHCI Debug Port ? > > > Zoran > _______ > >

1 0

Re: [coreboot] Coreboot with an UEFI payload to boot (Clover) an Thinkpad X230 Hackintosh
by my First name is Test And my last Name is iPation 02 Jan '18

02 Jan '18

On 01/01/2018 20:23, Zoran Stojsavljevic wrote: Here, (again), somebody from GOOGLE Coreboot folks should help you with this transition (from DXE/Tiano Core to OS Boot Loader/GRUB2). OK? Hi Zoran, I'm sorry if I don't really understand what you mean by "somebody from GOOGLE Coreboot folks" My english is a bit bad. Are there people from Google company working on Coreboot ? Or, you can also post some complete debug traces (from FSP till GRUB2 or whatever), so me and/or somebody else should look into them, to see what is going on here??? In order to get debug traces from my X230, should I use a EHCI Debug Port ? Zoran _______

1 0

Re: [coreboot] Coreboot with an UEFI payload to boot (Clover) an Thinkpad X230 Hackintosh
by my First name is Test And my last Name is iPation 02 Jan '18

02 Jan '18

On 01/01/2018 21:07, Branden Waldner wrote: > Hello, > > If I'm understanding this correctly, you are unable to get > Coreboot/TianoCore to correctly load/boot efi grub2 (on disk). If this > isn't working your not even able to get to chainloading Clover. > (Unless grub2 is working, but booting Ubuntu isn't?). Yes that's right. > > You could either try to get your Coreboot/TianoCore working, or, as > you mentioned you could try using Coreboot/SeaBIOS/Duet(Tianocore). > Doesn't Clover already include using Duet as an option (to boot from > mbr/non-uefi)? Yes that's right too. > If you can get the original bios to boot only in legacy > you could see if you can get a working Duet or mbr boot Clover setup > working and then try to boot it with Coreboot/SeaBIOS. So I've just tried Coreboot/SeaBIOS (on flash) + CloverMBR/macOS (on disk), and it worked!! > Some uefi > bios's won't boot into legacy mode if they see a gpt disk or a ESP > partition though. You should even be able to install a mbr boot block > for grub2 from Ubuntu while otherwise keeping the efi grub installed > (I think the full auto-install grub2 packages conflict though). > > Branden So yes, I think CloverEFI can also be installed like Duet (Coreboot/SeaBIOS/CloverEFI) on flash, so I'll try to figure out this config. Thanks very much.

1 0

Re: [coreboot] BDX-DE PCI init fail
by Hilbert Tu(杜睿哲_Pegatron) 02 Jan '18

02 Jan '18

Hi Zoran, The log was just at following link: http://mail.coreboot.org/pipermail/coreboot/attachments/20171227/b07eb74e/a… With messages: MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled By the way, I have tried to use U-Boot and Grub2 as payload, but I don't think the payload was executed since it failed at PCI 00:1f.3 init. -Hilbert -----Original Message----- From: Zoran Stojsavljevic [mailto:zoran.stojsavljevic@gmail.com] Sent: Saturday, December 30, 2017 2:32 PM To: Hilbert Tu(杜睿哲_Pegatron) Cc: David Hendricks; coreboot(a)coreboot.org Subject: Re: [coreboot] BDX-DE PCI init fail > I still have same issue even tried to comment out the 1f.3 device in > ./src/mainboard/intel/camel- backmountain_fsp/devicetree.cb then > rebuild coreboot. You wrote that you submitted the log. Is this the full log? I doubt. I do NOT see physical memory layout as well as MTRR layout. Could you, please, submit the full/complete log? Which payload are you using? SeaBIOS? Thank you, Zoran On Fri, Dec 29, 2017 at 5:58 AM, Hilbert Tu(杜睿哲_Pegatron) <Hilbert_Tu(a)pegatroncorp.com> wrote: > Hi David, > > > > Thanks for your information. > > I still have same issue even tried to comment out the 1f.3 device in > ./src/mainboard/intel/camelbackmountain_fsp/devicetree.cb then rebuild > coreboot. > > Could you let me know how to do that? > > > > -Hilbert > > > > From: David Hendricks [mailto:david.hendricks@gmail.com] > Sent: Friday, December 29, 2017 9:46 AM > To: Hilbert Tu(杜睿哲_Pegatron) > Cc: coreboot(a)coreboot.org > Subject: Re: [coreboot] BDX-DE PCI init fail > > > > Hi Hilbert, > > Have you had any luck? I have a board with a similar problem. > Commenting out the entry for device 1f.3 in devicetree.cb seemed to > help (I copied src/mainboard/intel/camelbackmountain_fsp for my project). > > > > On Wed, Dec 27, 2017 at 2:17 AM, Hilbert Tu(杜睿哲_Pegatron) > <Hilbert_Tu(a)pegatroncorp.com> wrote: > > Hi, > > > > I am porting coreboot on Intel BDX-DE platform and it gets stuck when > init PCI 00:1f.3. This device should be SMBus, serial management bus. > But I don’t know why this happened. Does anyone can give me some hint? > Attached is my boot up log. Thanks in advance. > > > > -Hilbert > > This e-mail and its attachment may contain information that is > confidential or privileged, and are solely for the use of the > individual to whom this e-mail is addressed. If you are not the > intended recipient or have received it accidentally, please > immediately notify the sender by reply e-mail and destroy all copies > of this email and its attachment. Please be advised that any > unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. > 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件 > 通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。 > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot > > > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot This e-mail and its attachment may contain information that is confidential or privileged, and are solely for the use of the individual to whom this e-mail is addressed. If you are not the intended recipient or have received it accidentally, please immediately notify the sender by reply e-mail and destroy all copies of this email and its attachment. Please be advised that any unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。

1 0

Coreboot with an UEFI payload to boot (Clover) an Thinkpad X230 Hackintosh
by Branden Waldner 01 Jan '18

01 Jan '18

Hello, If I'm understanding this correctly, you are unable to get Coreboot/TianoCore to correctly load/boot efi grub2 (on disk). If this isn't working your not even able to get to chainloading Clover. (Unless grub2 is working, but booting Ubuntu isn't?). You could either try to get your Coreboot/TianoCore working, or, as you mentioned you could try using Coreboot/SeaBIOS/Duet(Tianocore). Doesn't Clover already include using Duet as an option (to boot from mbr/non-uefi)? If you can get the original bios to boot only in legacy you could see if you can get a working Duet or mbr boot Clover setup working and then try to boot it with Coreboot/SeaBIOS. Some uefi bios's won't boot into legacy mode if they see a gpt disk or a ESP partition though. You should even be able to install a mbr boot block for grub2 from Ubuntu while otherwise keeping the efi grub installed (I think the full auto-install grub2 packages conflict though). Branden

1 0

Re: [coreboot] Coreboot with an UEFI payload to boot (Clover) an Thinkpad X230 Hackintosh
by Zoran Stojsavljevic 01 Jan '18

01 Jan '18

> Then I’ve tried Coreboot/TianoCore (on flash) + Grub2(EFI)/Ubuntu (on > disk), and it didn’t worked. I have a black screen with a blinking cursor > (top left screen). Hello Fred, Let me clear for you the theory, since I see that you need a bit more knowledge here (I apologize for not using text mode, since I import picture in this email). Let me import the picture how your stock UEFI (BIOS) looks like: [image: Inline image 1] You see, your INTEL FSP and Coreboot are nothing more, then SEC + PEI (intermingled), where in PEI phase CPU + Chipset Init (most of it) belong to FSP, less of Chipset Init + almost entire Board Init belong to Coreboot, + minimal of DXE (the minimum set of drivers to make OS boot loader to work). Tiano Core is the following: entire/full set of DXE (device drivers) with UEFI calls, to make it UEFI compatible, + probably Boot Dispatcher. (Final) OS Boot loader is actually GRUB2. Here, (again), *somebody from GOOGLE Coreboot folks should help* you with this transition (from DXE/Tiano Core to OS Boot Loader/GRUB2). OK? Or, you can also post some complete debug traces (from FSP till GRUB2 or whatever), so me and/or somebody else should look into them, to see what is going on here??? Zoran _______ On Mon, Jan 1, 2018 at 7:57 PM, my First name is Test And my last Name is iPation <testipation(a)live.com> wrote: > > > > While doing Coreboot + Tiano Core (or UEFI) in flash & GRUB2 + Ubuntu > > on drive, you should check and see if you see the same as me?! At > > least using stock BIOS??? > > _______ > > Hi Zoran, > I think you missed some lines in my previous replies: > > I’ve tried the stock UEFI Bios (on flash) + Grub2(EFI)/Ubuntu (on 1st > disk, 1st to boot) + Clover(EFI)/macOS (on 2nd disk), well, it worked, > Grub(EFI) can chainload to boot Clover (which boot macOS). > So yes, I agree with you with the efi hierarchy, and grubx64.efi. It > works with stock EFI Bios. > > > Then I’ve tried Coreboot/TianoCore (on flash) + Grub2(EFI)/Ubuntu (on > disk), and it didn’t worked. I have a black screen with a blinking > cursor (top left screen). > > > > >> So I’ve tried to build a Grub2 EFI as payload for Coreboot, but without > success. > > Nope. You have GRUB2 on drive, already. You should build Coreboot + > > Tiano Core in flash (then have drive GRUB2 + Ubuntu), but here > > somebody from Coreboot-GOOGLE folks should give you a hand. > > > > Should work, as my best understanding is. > > > > Zoran > > _______ > > > > > >

1 0

Re: [coreboot] Coreboot with an UEFI payload to boot (Clover) an Thinkpad X230 Hackintosh
by my First name is Test And my last Name is iPation 01 Jan '18

01 Jan '18

> While doing Coreboot + Tiano Core (or UEFI) in flash & GRUB2 + Ubuntu > on drive, you should check and see if you see the same as me?! At > least using stock BIOS??? > _______ Hi Zoran, I think you missed some lines in my previous replies: I’ve tried the stock UEFI Bios (on flash) + Grub2(EFI)/Ubuntu (on 1st disk, 1st to boot) + Clover(EFI)/macOS (on 2nd disk), well, it worked, Grub(EFI) can chainload to boot Clover (which boot macOS). So yes, I agree with you with the efi hierarchy, and grubx64.efi. It works with stock EFI Bios. Then I’ve tried Coreboot/TianoCore (on flash) + Grub2(EFI)/Ubuntu (on disk), and it didn’t worked. I have a black screen with a blinking cursor (top left screen). >> So I’ve tried to build a Grub2 EFI as payload for Coreboot, but without success. > Nope. You have GRUB2 on drive, already. You should build Coreboot + > Tiano Core in flash (then have drive GRUB2 + Ubuntu), but here > somebody from Coreboot-GOOGLE folks should give you a hand. > > Should work, as my best understanding is. > > Zoran > _______ > >

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot January 2018