Re: [coreboot] Runtime config

2018-04-17 Thread bartek.pastudzki 3mdeb.com
Hello again, on Fri, 13 Apr 2018 18:35:58, Nico Huber wrote: > I think our primary focus should be to define a common interface, first, > for different implementations. There's already coreboot's "option table" > that is stored in RTC/CMOS RAM. Marcello has started some work to

Re: [coreboot] Runtime config

2018-04-13 Thread Julius Werner
> > And you seem to assume that CBFS is memory mapped which might not always > be the case. > This is a very important part to keep in mind when we are talking UART. There has been an attempt inside the Chrome OS team before to make the UART runtime-configurable, and it fell flat on its face

Re: [coreboot] Runtime config

2018-04-13 Thread Nico Huber
Hello Bartek, On 11.04.2018 22:48, bartek.pastudzki 3mdeb.com wrote: We have runtime configuration arguments implemented for our platform in out fork. This is very simple, we just add few lines in SeaBIOS configuration file on CBFS (https://bit.ly/2qmX9nT — config example,

[coreboot] Runtime config

2018-04-11 Thread bartek.pastudzki 3mdeb.com
Hi We have runtime configuration arguments implemented for our platform in out fork. This is very simple, we just add few lines in SeaBIOS configuration file on CBFS (https://bit.ly/2qmX9nT — config example, https://bit.ly/2v5Era6 — handling code). There are only boolean values, no syntax,