[coreboot] Adding support for a system near you
Could we put Peter's great presentation on the Wiki somewhere? http://events.ccc.de/congress/2009/Fahrplan/events/3661.en.html Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] When should we retire newconfig?
On January 9, 2010 at 9:11 PM Myles Watson myle...@gmail.com wrote: -Original Message- Am 09.01.2010 13:29, schrieb j...@settoplinux.org: Yes you can add Thomson IP1000 and RCA RM4100 to the list. They build fine with Kconfig. Have you boot tested them yet? I tried them about a month ago (begining of December) and they were booting fine with filo. Unless something drastic has changed since then??? Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Future coreboot phases?
On January 10, 2010 at 7:31 AM ron minnich rminn...@gmail.com wrote: great idea, we need it. I think it ought to be a .tex file. But this is a good start, needs to be in svn yes and a wiki page please?? Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Future coreboot phases?
On January 11, 2010 at 1:52 PM Patrick Georgi patr...@georgi-clan.de wrote: Am 11.01.2010 14:42, schrieb Peter Stuge: I don't think svn or wiki matters. .tex is nice because you can easily make .pdf and print. Ron has inspired me to use Lyx. :) markdown can be transformed to tex for those that want it (and thus to pdf), but it's still editable with a simple text editor (unlike lyx files, or tex files of reasonable complexity). Lyx for windows is basically non-existant, for example. I think it's more important to save it than to have the righttm format. I think a wiki page would be fine. Right, and as said, one or the other please. So wiki it is? My vote is for wiki... Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Test : printing current time in serial debug
On January 11, 2010 at 2:24 PM Peter Stuge pe...@stuge.se wrote: conged...@voila.fr wrote: I want to display the current date and time inside functions like add_mainboard_resources, suspend_resume or to find the elapsed time between the end of coreboot and the end of the payload for example. I suggest to do this is by passive measurement outside the running code, e.g. by timestamping messages on the serial port or by timing edges or data on a signal or bus which is accessible throughout the execution of coreboot and the rest of the system. Kevin O'Connor has written a script for serial port timestamping which is available in the SeaBIOS repository. It also does accounting for the serial port output overhead in coreboot, which is nice. I search how to get the current time from protected mode in coreboot. Since there is no library, I think the only way is to call real mode int 1ah from protected mode, but I can't find any example. Is it the only way ? There are no BIOS interrupt services available in coreboot. If you need them, you can use coreboot with a SeaBIOS payload, but it will not help during execution of coreboot itself. If someone can help me or gives me the source to implement this feature. Basically you have to rely on what the hardware provides you. There are several different timer peripherals in a modern x86 system and which one you should use depends on lots of parameters (resolution and maximum primarily, but also the cost of using the timers) for the times that you want to measure, if you choose to do it internally in the coreboot code. If you have an Intel chipset, I have meade some recent discoveries (thanks to serialice) that the ICH southbridges actually have a timer built into the power management registers. You could always do a read of this register at the starting point and another read of this register at the ending point to calculate load time if that is what you are looking for(some vender bios's use this method to calulate memory timing). Hope that helps. Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] When should we retire newconfig?
On January 8, 2010 at 4:56 PM Myles Watson myle...@gmail.com wrote: All boards still work on newconfig - once we drop that, there are several possibilities for cleaning up. Boards that were recently tested with kconfig and tinybootblock: emulation/qemu-x86 kontron/986lcd-m amd/serengeti_cheetah_fam10 asus/m2v-mx_se with kconfig, but not with tiny bootblock: I've tested: tyan/s2895 tyan/s2892 Hugh's tested: arima/hdama Yes you can add Thomson IP1000 and RCA RM4100 to the list. They build fine with Kconfig. In fact they do not build the old way anymore, only with Kconfig. Is there some kind of guilde line or list of things that need to be done to cleanup/convert on each board? I would say: 1. Run util/kbuildall/kbuildall vendor/board 2. Fix Kconfig mismatches in src/mainboard/vendor/board/Kconfig 3. Build and boot test (and report to the list) Soon we'll need to start only reporting Kconfig build errors on the mailing list. Then we can fix kbuildall to use an older version of newconfig for its comparisons, then we'll be able to phase it out. ok but what needs to be done to use tinybootblock? Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] When should we retire newconfig?
On January 8, 2010 at 7:37 AM Patrick Georgi patr...@georgi-clan.de wrote: Am 08.01.2010 01:09, schrieb j...@settoplinux.org: Hello Patrick, Are there any boards that have completely crossed over that I can look at for an example? All boards still work on newconfig - once we drop that, there are several possibilities for cleaning up. Boards that were recently tested with kconfig and tinybootblock: emulation/qemu-x86 kontron/986lcd-m amd/serengeti_cheetah_fam10 asus/m2v-mx_se Is there some kind of guilde line or list of things that need to be done to cleanup/convert on each board? Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] When should we retire newconfig?
On January 6, 2010 at 12:03 PM Patrick Georgi patr...@georgi-clan.de wrote: Hi, With r5000 all boards build with kconfig. The last step of the buildconfig project is to eliminate the old system so we're down to one method of building an image. What issues remain before we can remove newconfig from the tree? My list currently contains: * Kconfig must match newconfig for all boards, as appropriate. The automatic KBuild report on the list (which can be regenerated locally by running util/kbuildall/kbuildall) gives some indication on how much work is left in that area. * More testing I'm not sure how many boards and chipsets were successfully run with a kconfig image recently. * Fallback/normal switch While the hard part in code is done for the switch (via tinybootblock), there are some issues left. kbuild always builds just one image, not two as would be necessary to build fallback/normal in a single pass. Question is, do we want that? In my opinion, it's more sensible to have a way to add to and update an existing coreboot image, and expect users who rely on fallback/normal to build twice (into the same image), with an appropriate configuration for each run. Either way, this requires support in the build system (either to update, or to build twice in one go), and some alternative tinybootblock routine. * Documentation I'll try to work out some documentation for the new config system and code flow (esp. tinybootblock). Apart from that, with kconfig, many of the build tutorials on the wiki will be outdated. Hello Patrick, Are there any boards that have completely crossed over that I can look at for an example? Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] FOSDEM2010 devroom needs speakers :)
On January 7, 2010 at 11:39 PM Rudolf Marek r.ma...@assembler.cz wrote: Hi again, Btw what is the duration of the talk? Rudolf Marek - ACPI and Suspend/Resume under coreboot Ever wanted to know more about ACPI? The aim of the talk is to introduce the software part of ACPI as well as provide the necessary hardware details to get the bigger picture. The tour through Coreboot ACPI implementation will be given. Suspend and resume procedure will be presented with all nifty parts explained. Thats it. I think I need like hour or hour and half for this. Do you like it? What sort of audience should I expect? Perhaps it could even start with a question - what OS needs to know about the hardware - and then show how it is connected to the ACPI (irq routing, PM, PCI buses). When done, one could show how this is implemented in Coreboot/what files and what does it do. Plus perhaps some hints how to port ACPI to some new board. At the end I would like to describe the suspend/resume with some details and pitfalls. Maybe some a or the is missing in the abstract. We don't use them in Czech language so I don't have big sense for them. Dam I wish I could be there! Sounds like it is going to be a pretty good agenda. Is anyone going to get all the talks on video (crossing my fingers)? Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [flashrom] We have a FOSDEM DevRoom!
On December 2, 2009 at 12:22 AM Luc Verhaegen l...@skynet.be wrote: On Wed, Dec 02, 2009 at 01:13:18AM +0100, Carl-Daniel Hailfinger wrote: On 02.12.2009 00:36, Luc Verhaegen wrote: The kind FOSDEM organizers have given us a DevRoom on saturday the 6th of February, as requested. Thanks a lot for organizing this, Luc! Yes this is a great oppritunity Luc. I wish I could be there... Well, i definitely want you to do the introductory flashrom talk. But on the other hand, the introductory part with flashrom is rather limited, after which you can go and delve deeper into one or several further topics that you mentioned. Chances are that it gets filmed in HDTV and makes it onto phoronix.com. And for showing off, maybe we should get a webcam along that we then can use to show hardware up close on the projector. According to the wiki it looks like you want to get into bios security a bit. This may be an opritune time to introduce SerialICE??? Thanks - Joe -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
