coreboot

coreboot@coreboot.org

11 participants
39713 discussions

RE: Stuck. Compile error with a clean tree.
by Ronald G. Minnich 29 Nov '04

29 Nov '04

On Mon, 29 Nov 2004, Dave Aubin wrote: > Although this will only help you if you are getting to a 2.6 kernel > And have a network connection. he's nowhere near that far. He's got to get the northbridge working so memory works. It doesn't. serial port is the only way. ron

1 0

RE: Stuck. Compile error with a clean tree.
by Dave Aubin 29 Nov '04

29 Nov '04

Do you have access to the network? If you don't have a com cable (like I did in the beginning) then You could try netconsole. Here are some links to what it is. http://lwn.net/Articles/43852/ http://technocrat.net/article.pl?sid=04/08/14/0236245&mode=nested Although this will only help you if you are getting to a 2.6 kernel And have a network connection. Dave -----Original Message----- From: linuxbios-admin(a)clustermatic.org [mailto:linuxbios-admin@clustermatic.org] On Behalf Of Adam Talbot Sent: Monday, November 29, 2004 5:19 PM To: Ronald G. Minnich Cc: linuxbios(a)clustermatic.org Subject: Re: Stuck. Compile error with a clean tree. Clean compile of the adl855pc. I changed 2 lines in the config and added one. added: option ROM_SIZE=524288 normal, changed: option ROM_IMAGE_SIZE=0x10000 to option ROM_IMAGE_SIZE=0x15000 fallback, changed: option ROM_IMAGE_SIZE=0x10000 to option ROM_IMAGE_SIZE=0x15000 Still get garbage to the screen... Bad cable? Switched cables, same. Idea, added console redirect to my grub.conf set the speed to 115200 8n1, works fine. Hummm What does it take to get the onboard VGA running? Can you give me a quick "how to"? -Adam Talbot ----- Original Message ----- From: "Ronald G. Minnich" <rminnich(a)lanl.gov> To: "Adam Talbot" <talbotx(a)comcast.net> Cc: <linuxbios(a)clustermatic.org> Sent: Monday, November 29, 2004 1:47 PM Subject: Re: Stuck. Compile error with a clean tree. > that's odd, in the adl855pc I got output just fine. > > For the heck of it, build an adl855pc target and see if you get the same > problem. > > ron > > _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

elfboot
by Gin 29 Nov '04

29 Nov '04

I know it's probably been a while since you look into the elfboot code. In the elfboot.c When it tries to build the ELF segment list, it checks if the segment address is valid by walking through the table of valid memory ranges. What is the reason to do this? Below is the code, the "if " statement seems only guarantee that the new addresses INTERSECT with the valid memory range, not fully contained. for(i = 0; i < mem_entries; i++) { uint64_t mstart, mend; uint32_t mtype; mtype = mem->map[i].type; mstart = mem->map[i].start; mend = mstart + mem->map[i].size; if ((mtype == LB_MEM_RAM) && (start < mend) && (end > mstart)) { break; } }

2 1

RE: pnp_enable_resource not being called
by YhLu 28 Nov '04

28 Nov '04

In the AMD8111_lpc.c static void amd8111_lpc_enable_resources(device_t dev) { pci_dev_enable_resources(dev); enable_childrens_resources(dev); } static struct device_operations lpc_ops = { .read_resources = amd8111_lpc_read_resources, .set_resources = pci_dev_set_resources, .enable_resources = amd8111_lpc_enable_resources, .init = lpc_init, .scan_bus = scan_static_bus, // .enable = amd8111_enable, .ops_pci = &lops_pci, }; So I guess you need to add the device driver for the lpc in SB. Then the scan_static_bus and enable_childrens_resources(dev) will be called. Regards YH -----Original Message----- From: Greg Watson [mailto:gwatson@lanl.gov] Sent: Wednesday, November 24, 2004 1:29 PM To: 'LinuxBIOS' Subject: pnp_enable_resource not being called The sandpoint has the following structure: Northbridge MPC107 --> Southbridge W83C553 --> Superio PC97307 The config file looks like: chip northbridge/motorola/mpc107 device pci_domain 0 on device pci 0.0 on end device pci b.0 on chip southbridge/winbond/w83c553 chip superio/NSC/pc97307 device pnp 15c.0 on end # Kyeboard device pnp 15c.1 on end # Mouse device pnp 15c.2 on end # Real-time Cloc k device pnp 15c.3 on end # Floppy device pnp 15c.4 on end # Parallel port device pnp 15c.5 on end # com2 device pnp 15c.6 on end # com1 device pnp 15c.7 on end # gpio device pnp 15c.8 on end # Power manageme nt end end end # pci to isa bridge device pci b.1 on end # pci ide controller end device cpu_bus 0 on chip cpu/ppc/mpc74xx device cpu 0 on end end end end The dev_enumerate() code is calling the PNP enable routines and the dev_initialize() code is calling the PNP init routine. However the dev_enable() code never calls the PNP enable_resource routine, which means the the PNP devices are never actually enabled. The enable_dev routine for the superio device calls: pnp_enable_devices(dev, &ops, sizeof(pnp_dev_info)/sizeof(pnp_dev_info[0]), pnp_dev_info); where ops is defined as: static struct device_operations ops = { .read_resources = pnp_read_resources, .set_resources = pnp_set_resources, .enable_resources = pnp_enable_resources, .enable = pnp_enable, .init = init, }; Any ideas why this is not working? Is there something else that needs to happen? Greg _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

4 3

compile vga rom
by Gin 28 Nov '04

28 Nov '04

I have an onboard VGA chip that I want to use. Is there a way to compile the onboard VGA rom with the linuxbios? Or would it be easier to use a VGA card? Gin

1 0

boot from an ide
by Gin Lin 25 Nov '04

25 Nov '04

I use FILO as the payload to boot from a Hard Disk, which has a installed linux on it. I noticed if I enabled the ide stream. It tries to read the ELF header from my IDE drive. But I thought the FILO payload should be the one to load the image from the IDE drive. When does it come in and play the role? Anyone can explain the flow of booting if I try to load the INSTALLED linux from a IDE drive. Gin

1 0

Link and Links again
by Li-Ta Lo 25 Nov '04

25 Nov '04

Eric, >From my understanding, the device.link for bridge device does not include the up stream bus. The up stream bus is the device.bus field. So for 'normal' PCI bridges, with one up stream and one down stream buses, its device.links = 1. Am I correct ? Ollie

5 7

Invalidating TLB, cache
by Li-Ta Lo 25 Nov '04

25 Nov '04

Eric, What was the conclusion of invalidating the cache and TLB ? If found that xorl %eax, %eax movl %eax, %cr3 /* Invalidate TLB*/ still exists in the current CVS. Ollie

2 1

Apologies for ignored email...
by ebiederman＠lnxi.com 25 Nov '04

25 Nov '04

I just discovered that the my local system administrators had applied a spam filter to my incoming mail that seems to have has a 2:1 false positive rate when identifying spam. Especially picking on email that was short to the point, and important or interesting. I think I have things under control, but I will have to wait until next week when everyone gets back work to tell for certain. So my apologies for not catching this sooner. It resulted in me ignore several messages I should have because I never received them. Eric

1 0

Re: Compile error
by Adam Talbot 24 Nov '04

24 Nov '04

Cool, go that error fixed, syntax error on my part. My configs is based off the digitallogic/adl855pc. I made a new set of folders in the tree commell/lv-671, in mainboards and targets. I put into place a new irq table for my board. After fixing some more "simple" error's I get these two new errors. The first one I can fix, but am not sure why it comes up. My current config file is nearly unchanged from the digitallogic/adl855pc, i have added one line "option ROM_SIZE=524288" static.c:40: error: `mainboard_commell_lv_671_ops' undeclared here (not in a function) static.c:40: error: initializer element is not constant static.c:40: error: (near initialization for `dev_root.chip_ops') static.c:24: error: storage size of `mainboard_commell_lv_671_info_0' isn't known make[1]: *** [static.o] Error 1 make[1]: Leaving directory `/root/freebios2/targets/commell/lv-671/lv-671/normal' make: *** [normal/linuxbios.rom] Error 1 This has an easy fix of just going through my static.c and changing it from lv-671 to lv671, easily done under vi, but im not sure it there are any golbal effects from such a mod. After that mod the compile goes right past that point and runs into the memory error. This part is beond my sikll with C. You guy's have any ideas? gcc -m32 -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../../i686-pc-linux-gnu/bin/ld: section .reset [00000000fffdfff0 -> 00000000fffdffff] overlaps section .rom [00000000fffd5478 -> 00000000fffe67ef] /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../../i686-pc-linux-gnu/bin/ld: section .id [00000000fffdffd5 -> 00000000fffdffef] overlaps section .rom [00000000fffd5478 -> 00000000fffe67ef] collect2: ld returned 1 exit status make[1]: *** [linuxbios] Error 1 make[1]: Leaving directory `/root/freebios2/targets/commell/lv-671/lv-671/normal' make: *** [normal/linuxbios.rom] Error 1 -Adam Talbot

2 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot