Yu-Cheng Liu | 3 Jul 09:53 2015

Question about making Qemu diskimg

Hello

I have some questions about making Qemu disk image.

1. In QEMU_Build_Tutorial ,one step is to copy root file system to the diskimg " # cp -R /* /mnt/rootfs ",I what  know what files are necessary ?(I don't want put all of it,it might be too large) 


2. Is it necessary to put Debian in diskimg?


3. I can't figure out this situation :  
I can't successfully boot my disk image ,but can boot by QEMU download image,so I try to create a empty disk image , format it as (EXT2/EXT3/EXT4). mount QEMU download image and copy all of files into my image mount's directory.Boot my disk image again,and It does't work.What's wrong with my idea?I thought change my image contents to download's and it can be work.It seems not.


thank for your help~



--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
francisco dominguez | 3 Jul 21:35 2015
Picon

About coreboot

Hi, I'm new, I would like to help develop coreboot is C, I am interested to collaborate because I like to learn more about C and take the chance to help this fantastic community.

What language is written coreboot?
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Adam Duncan | 3 Jul 16:39 2015
Picon

Looking for Broadwell board for coreboot build

Hi, I'm looking for a board with an Intel broadwell on it that I can get a coreboot build going for. Do you have any recommendations?

Are there any commercial boards with the broadwell that are currently supported?

If not, do you know which boards would be the easiest to focus on?

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
kroms | 3 Jul 16:27 2015
Picon

T400 screen issue / EDID handling

Hello,

I allready contacted Francis from libreboot and he forwared me to this 
list, because it seems to be an issue regarding coreboot.

I have flashed a Lenovo T400 with libreboot.

The T400 has an Intel GPU and I am able to use it with an external 
display connected to the onboard vga-port.

The issue is, that I can't use the internal display, which is an 
1440x900 Samusung LTN141WD-L05, EDID dump:

https://paste.debian.net/plainh/b3699c60

It seems like the internal screen is powered on while booting but it 
stays black.

Francis assumes that this is due to bugs in how coreboot handles the 
EDID.

Here is an EDID dump of a working display:

http://paste.debian.net/plainh/776705d5

Anyone is able to help?

Thanks in advance!

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Adam Duncan | 3 Jul 16:27 2015
Picon

Recommended broadwell board w coreboot support

Hi, I'm looking for a board with an Intel broadwell on it that I can get a coreboot build going for. Do you have any recommendations?

Are there any commercial boards with the broadwell that are currently supported?

If not, do you know which boards would be the easiest to focus on?

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Paul Menzel | 2 Jul 22:42 2015
Picon
Picon

CBMEM console deactivated in coreboot and activated SeaBIOS

Dear coreboot folks,

if the CBMEM console is disabled in coreboot and only enabled in
SeaBIOS, currently SeaBIOS does not write any messages to the CBMEM
console (SeaBIOS commit f24eb2f85 (build: CONFIG_VGA_FIXUP_ASM should
depend on CONFIG_BUILD_VGABIOS)).

    $ more src/fw/coreboot.c
    […]
    struct cb_cbmem_ref *cbref = find_cb_subtable(cbh, CB_TAG_CBMEM_CONSOLE);
    if (cbref) {
        cbcon = (void*)(u32)cbref->cbmem_addr;
        debug_banner();
        dprintf(1, "Found coreboot cbmem console  <at>  %llx\n", cbref->cbmem_addr);
    }
    […]

Does the CBMEM specification(?) allow to add the CBMEM console
section(?) – CB_TAG_CBMEM_CONSOLE 0x17 – after coreboot has run? If
yes, I could try to adapt SeaBIOS to do just that in case coreboot does
not set it up.

Thanks,

Paul
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Bill Toner | 2 Jul 20:10 2015
Picon

board bringup/debug howto?

Amd's embedded developer site suggests the sage smartprobe for jtag debugging a target board. Sage's website shows this is discontinued. Whay other options are there for bringup and lowlevel firmware and os driver debug? 

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Alexander Couzens | 2 Jul 19:42 2015
Picon

rtc migrations / century byte used

Hi,

I mentioned some problems while debugging windows on a x201.
Also linux throw a warning with the RTC, but it could recover
the correct time.
coreboot multiple use of one nvram byte on lots of boards.
On most board 0x32/b400 is used by some nvram settings as well as the OS interprets the time (century) from
the same byte.
The century byte saves the century in bcd format. The default location is 0x32 / b400.

find src/mainboard/ -iname cmos.layout | xargs grep -h '^400'  | sort | uniq -c
    112 400          1       e       1        power_on_after_fail
     33 400          1       e       2        hyper_threading
      1 400          8       h       0        century
      9 400          8       h       0        volume
      1 400         8         r       0        stumpy_usb_reset_disable
      2 400         8       h       0        volume
# 37 boards can be removed from this list, because they disabled the century byte in facp.

This leads to 3 topic:
 * how can we change cmos.layout in a way no or less settings gets lost? e.g. add a version field and a way to
migrate these. or do we ignore the loss of data?
 * do we want to support the century byte?
 * how do we fix the multiusage, because it makes problems atm.

best
lynxis

--
Alexander Couzens

mail: lynxis <at> fe80.eu
jabber: lynxis <at> jabber.ccc.de
mobile: +4915123277221
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
echelon | 1 Jul 10:46 2015
Picon

trouble ahead?

Hello,

Sorry to fall in catastrophism again, but what do you think about that:

http://www.kitguru.net/components/anton-shilov/microsoft-is-interested-to-buy-advanced-micro-devices-source/

Quite bad news for coreboot isnt it?....

:-/

Florentin

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

WordPress | 1 Jul 03:01 2015

New on blogs.coreboot.org: [GSoC] coreboot for ARM64 Qemu – Week #4 and #5

A new post titled "[GSoC] coreboot for ARM64 Qemu – Week #4 and #5" has been published on the coreboot blog. Find the full post at http://blogs.coreboot.org/blog/2015/07/01/gsoc-coreboot-for-arm64-qemu-week-4-and-5/

From this week I started dealing with the core aspects of aarch64 design. I continued with the process of building the armv8, along with handling the required patching-up, interfacing, hook-ups. In my last post, I had talked about the toolchain building error (in binutils) for arm64 which I was facing on OSX. I had to remove the –enable-gold flag from the binutils. After making this small update, the build_BINUTILS looked like this, and I was able to get the toolchain working.

build_BINUTILS() { if [ $TARGETARCH == "x86_64-elf" ]; then ADDITIONALTARGET=",i386-elf" fi CC="$CC" ../binutils-${BINUTILS_VERSION}/configure --prefix=$TARGETDIR \ --target=${TARGETARCH} --enable-targets=${TARGETARCH}${ADDITIONALTARGET} \ --disable-werror --disable-nls --enable-lto \ --enable-plugins --enable-multilibs CFLAGS="$HOSTCFLAGS" || touch .failed $MAKE $JOBS || touch .failed $MAKE install DESTDIR=$DESTDIR || touch .failed }

The work had just began after fixing the toolchain. On attempting to building, the faced error I got was :

toolchain.inc:137: *** building bootblock without the required toolchain. Stop.

This was due to certain wrongly configured CONFIG options in the Kconfig. After this stage the initial bring-up of arm64 looked stable. Moving forward, I was met with an error in src/arch/arm64/c_entry.c

src/arch/arm64/c_entry.c: In function ‘arm64_init': src/arch/arm64/c_entry.c:52:2: error: implicit declaration of function ‘cpu_set_bsp’ [-Werror=implicit-function-declaration] cpu_set_bsp();

The inclusion of necessary files and structures were correct, and I kept getting this error. Furquan ultimately pointed to change 257370  following which, I could get past this. After this, I had to solve another BSD/OSX issue about date in genbuild_h.sh to get my build progressing.

Subsequently, some architectural decisions had to be made for the armv8. In the initial version, I had been banking on cbfs_media based structure in media.c, for creating functions for read, write and map. But the older formulation (in cbfs_core.c and cbfs_core.h) is changed now. In order to keep up, and to maintain uniformity, we decided to handle this as it is handled in armv7, i.e by creating a mapping to the qemu memory mapped space. Another point of discussion for stage loading. It is being brought up similar to armv7 for now. This might change in the future. Also the organisation for UART was finalised. plo11.c is included, as in  src/drivers/uart/Makefile.inc. by setting the DRIVERS_UART_PL011 in armv8 Kconfig.

Next hitch was dealing with SMP. In my proposal, I had suggested that incorporating smp into the emulation could be a long term goal. But since smp is a part of core arm64 logic, this cannot be completely ignored at this stage. I am met with this

coreboot/src/arch/arm64/stage_entry.S:94: undefined reference to `smp_processor_id’
build/arch/arm64/c_entry.romstage.o: In function `seed_stack':

 

A cpu file which adds smp_processor_id() is needed at this moment, which I am currently working on. Next week’s plan is to get past these (and meet new unforeseen issues ) and boot off on qemu.

 

 

 

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
HW42 | 30 Jun 13:22 2015
Picon

Support for Fujitsu Laptops

Hi,

are there any ongoing efforts to support (some) Fujitsu laptops?

While I'm ready to test things I don't have the required x86 firmware
development skills to do it myself.

Thank you.

HW42

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Gmane