coreboot April 2011

coreboot@coreboot.org

66 participants
229 discussions

Start a nNew thread

[PATCH] Initialize i8259 in i82371eb southbridge code
by Stefan Reinauer 25 Apr '11

25 Apr '11

This should allow to get rid of a hack when running u-boot as a coreboot payload. Stefan

2 1

Re: [coreboot] coreboot and Clang/LLVM
by Антон Кочков 25 Apr '11

25 Apr '11

Attached log with make V=1 Best regards, Anton Kochkov. 2011/4/25 Stefan Reinauer <stefan.reinauer(a)coreboot.org>: > * Антон Кочков <anton.kochkov(a)gmail.com> [110425 21:15]: >> Nope this is error of specifics of -I option for clang >> gcc works ok on the same tree >> >> Also this file already here. > > Hm.. the message is caused by romcc though. > > Can you run make V=1 with clang? > >

3 3

[PATCH] console/console.h cleanup
by Stefan Reinauer 25 Apr '11

25 Apr '11

See patch

2 3

Fwd: coreboot and Clang/LLVM
by Антон Кочков 25 Apr '11

25 Apr '11

Nope this is error of specifics of -I option for clang gcc works ok on the same tree Also this file already here. Best regards, Anton Kochkov. 2011/4/25 Stefan Reinauer <stefan.reinauer(a)coreboot.org>: > * Антон Кочков <anton.kochkov(a)gmail.com> [110423 06:55]: >> Hello! >> I'm trying to build coreboot with Clang/LLVM. Why? >> Because Clang produce nice error/warning messages, which help find a bugs. >> >> Here will be discussion about such things. >> >> Attached first log: >> ROMCC mainboard/emulation/qemu-x86/bootblock.inc >> src/arch/x86/init/bootblock_simple.c:1:10: fatal error: 'bootblock_common.h' file not found >> #include <bootblock_common.h> > > Looks like your checked out tree is messed up. It does not even die > calling clang, but ROMCC, on a file that certainly exists. > > Stefan > > >

1 0

coreboot and Clang/LLVM
by Антон Кочков 25 Apr '11

25 Apr '11

Hello! I'm trying to build coreboot with Clang/LLVM. Why? Because Clang produce nice error/warning messages, which help find a bugs. Here will be discussion about such things. Attached first log: Best regards, Anton Kochkov.

3 2

Re: [coreboot] coreboot Digest, Vol 74, Issue 74
by Paulo Alexandre A.P. de Oliveira 25 Apr '11

25 Apr '11

Hi guys, I'd like to make a question: Is Toshiba NB305 netbook supported by coreboot? If so what bios flashing program should i use? Flash Rom or the manufacturer proprietary one? (flash rom is advising me of not supported laptop, can i override this?) Best wishes, Paulo Oliveira Em 25-04-2011 10:00, coreboot-request(a)coreboot.org escreveu: > Send coreboot mailing list submissions to > coreboot(a)coreboot.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.coreboot.org/mailman/listinfo/coreboot > or, via email, send a message with subject or body 'help' to > coreboot-request(a)coreboot.org > > You can reach the person managing the list at > coreboot-owner(a)coreboot.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of coreboot digest..." > > > Today's Topics: > > 1. Re: Asus L1N64 (Paul Menzel) > 2. Re: Beijing meetup 4/25 (Hamo) > 3. Re: [PATCH]Change all type declaration to uintxx_t (Hamo) > 4. Re: [PATCH] Update the document of CBFS (Hamo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 24 Apr 2011 17:51:12 +0200 > From: Paul Menzel <paulepanter(a)users.sourceforge.net> > To: coreboot(a)coreboot.org > Subject: Re: [coreboot] Asus L1N64 > Message-ID: <1303660272.3956.18.camel@mattotaupa> > Content-Type: text/plain; charset="utf-8" > > Dear Julian, > > > Am Sonntag, den 24.04.2011, 08:34 -0700 schrieb Julian Shulika: > > [?] > >> This file devicetree.cb that I attached, is not suitable for GCC >> compiler yet . Thank you for your future help. > I am sorry. I do not know what to do, but hopefully the developers can. > You can also try to join the IRC channel to get help. > > > Thanks, > > Paul >

2 1

Trac reminder: list of new ticket(s)
by coreboot tracker 25 Apr '11

25 Apr '11

1 0

[PATCH] Update the document of CBFS
by Hamo 25 Apr '11

25 Apr '11

CBFS document is a little old since the structure of it has changed a lot specially CBFS master header. This patch updated the document to show the newest structure of CBFS. Signed-off-by: Yang Bai <hamo.by(a)gmail.com> Index: documentation/cbfs.txt =================================================================== --- documentation/cbfs.txt (revision 6534) +++ documentation/cbfs.txt (working copy) @@ -144,10 +144,13 @@ The following is the structure of the master header: struct cbfs_header { - unsigned int magic; - unsigned int size; - unsigned int align; - unsigned int offset; + u32 magic; + u32 version; + u32 romsize; + u32 bootblocksize; + u32 align; + u32 offset; + u32 pad[2]; }; The meaning of each member is as follows: @@ -156,9 +159,14 @@ magic number is 0x4F524243, which is 'ORBC' in ASCII. -'size' is the size of the ROM in bytes. Coreboot will subtract 'size' from +'version' is a 32 bit number that shows the version of CBFS master header. +Since only one version exists now, it should always be 0x31313131. + +'romsize' is the size of the ROM in bytes. Coreboot will subtract 'romsize' from 0xFFFFFFFF to locate the beginning of the ROM in memory. +'bootblocksize' is the size of the bootblock in bytes. + 'align' is the number of bytes that each component is aligned to within the ROM. This is used to make sure that each component is aligned correctly with @@ -193,11 +201,11 @@ Each CBFS component starts with a header: struct cbfs_file { - char magic[8]; - unsigned int len; - unsigned int type; - unsigned int checksum; - unsigned int offset; + char magic[8]; + u32 len; + u32 type; + u32 checksum; + u32 offset; }; 'magic' is a magic value used to identify the header. During runtime, @@ -287,11 +295,11 @@ The header is defined as: struct cbfs_stage { - unsigned int compression; - unsigned long long entry; - unsigned long long load; - unsigned int len; - unsigned int memlen; + u32 compression; /** Compression type */ + u64 entry; /** entry point */ + u64 load; /** Where to load in memory */ + u32 len; /** length of data to load */ + u32 memlen; /** total length of object in memory */ }; 'compression' is an integer defining how the data is compressed. There @@ -355,12 +363,12 @@ The following is the structure of each segment header: struct cbfs_payload_segment { - unsigned int type; - unsigned int compression; - unsigned int offset; - unsigned long long load_addr; - unsigned int len; - unsigned int mem_len; + u32 type; + u32 compression; + u32 offset; + u64 load_addr; + u32 len; + u32 mem_len; }; 'type' is the type of segment, one of the following: -- """ Keep It Simple,Stupid. """ Chinese Name: 白杨 Nick Name: Hamo Homepage: http://hamobai.com/ GPG KEY ID: 0xA4691A33 Key fingerprint = 09D5 2D78 8E2B 0995 CF8E 4331 33C4 3D24 A469 1A33

2 3

Beijing meetup 4/25
by Marc Jones 25 Apr '11

25 Apr '11

Hi all, Sorry for the short notice. I am in Beijing this week and we have a mini meetup on Monday night. I think that Zheng, Kerry, Jason, and Hamo might be attending. I'm not sure where it will be located. Send me an email if you would like to join us. Marc -- http://se-eng.com

2 1

Asus L1N64
by Julian Shulika 24 Apr '11

24 Apr '11

Hi everyone. Please,help community to add support for Asus L1N64. I can't create folder /src/mainboard/asus/L1N64 via SVN. I have three files only

2 3

← Newer
1
2
3
4
5
6
7
8
...
23
Older →

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 April 2011