coreboot October 2007

coreboot@coreboot.org

84 participants
481 discussions

[LinuxBIOS] About VGA question in the EPIA-M motherboard
by GTLin＠via.com.tw 26 Oct '07

26 Oct '07

Hi all, During compile linuxbios for EPIA-M, have some error message. The way that I compile as follow: At first, I build a payload “filo.elf” and put it in / According to HOWTO document, I fix some setting. In LinuxBIOSv2-2860/src/mainboard/via/epia-m/Options.lb default CONFIG_PCI_ROM_RUN=1 default CONFIG_CONSOLE_VGA=1 In LinuxBIOSv2-2860/targets/via/epia-m/Config.lb romimage "normal" option USE_FALLBACK_IMAGE=0 #option ROM_IMAGE_SIZE=128*1024 option ROM_IMAGE_SIZE=64*1024 option LINUXBIOS_EXTRA_VERSION=".0-Normal" payload /filo.elf end romimage "fallback" option USE_FALLBACK_IMAGE=1 #option ROM_IMAGE_SIZE=128*1024 option ROM_IMAGE_SIZE=60*1024 option LINUXBIOS_EXTRA_VERSION=".0-Fallback" payload /filo.elf end In LinuxBIOSv2-2860/targets/via/epia-m/via_epia-m/Makefile ./linuxbios.rom: normal/linuxbios.rom fallback/linuxbios.rom cat /crtbios.rom fallback/linuxbios.rom > ./linuxbios.rom .PHONY: all clean fallback-clean normal-clean fallback/linuxbios.rom normal/linuxbios.rom After compile, it has some error message. /usr/LinuxBIOSv2-2860/src/lib/version.c rm -f linuxbios.a ar cr linuxbios.a malloc.o lapic_cpu_init.o pci_ops.o lapic.o smbus_ops.o memset.o pci_ops_auto.o linuxbios_table.o fallback_boot.o pciexp_device.o tables.o keyboard.o acpi_tables.o pnp_device.o printk.o dsdt.o irq_tables.o pcix_device.o decode.o pci_device.o console.o fadt.o elfboot.o hardwaremain.o boot.o i8259.o delay.o version.o pci_ops_mmconf.o memcmp.o exception.o secondary.o isa-dma.o acpi.o pcibios.o hypertransport.o vtxprintf.o ops.o prim_ops.o root_device.o cardbus_device.o uart8250.o sys.o device_util.o rl5c476.o ./option_table.o compute_ip_checksum.o device.o mtrr.o northbridge.o memcpy.o agp_device.o clog2.o vt1211.o pirq_routing.o memmove.o microcode.o pci_rom.o delay_tsc.o pci_ops_conf2.o pci_ops_conf1.o mc146818rtc.o cache.o fpu.o rom_stream.o debug.o c_start.o ops2.o biosemu.o vsprintf.o cpu.o static.o gcc -m32 -nostdlib -r -o linuxbios_ram.o c_start.o vt8235_lpc.o uart8250_console.o vt8235.o vt8235_ide.o mainboard.o vt8235_usb.o vga_console.o vt8235_nic.o model_centaur_init.o linuxbios.a /usr/lib/gcc-lib/i586-suse-linux/3.3.3/libgcc.a gcc -m32 -nostdlib -nostartfiles -static -o linuxbios_ram -T /usr/LinuxBIOSv2-2860/src/config/linuxbios_ram.ld linuxbios_ram.o linuxbios_ram.o(.text+0xe26a): In function `vga_init': : undefined reference to `setup_realmode_idt' linuxbios_ram.o(.text+0xe27b): In function `vga_init': : undefined reference to `do_vgabios' linuxbios_ram.o(.text+0xe280): In function `vga_init': : undefined reference to `vga_enable_console' collect2: ld returned 1 exit status make[1]: *** [linuxbios_ram] Error 1 make[1]: Leaving directory `/usr/LinuxBIOSv2-2860/targets/via/epia-m/via_epia-m/normal' make: *** [normal/linuxbios.rom] Error 1 I have trace source code and can’t fix it. Can you help me to answer what it happen? Thank for your kindness help. BR, GT GT Lin 林俊廷 CPU Platform Division –RD Core Logic Software Engineer VIA Technologies, Inc. 1F, 531, Chung-Cheng Road Hsin-Tien, Taipei 231, Taiwan Tel: 886-2-2218-5452 Ext:7727 Fax: 886-2-8667-1803 E-Mail: GTLin(a)via.com.tw <mailto:GTLin@via.com.tw> Http://www.viatech.com <http://www.viatech.com/>

1 0

[LinuxBIOS] ASUS M2N-SLI Deluxe
by Arturo Mann 26 Oct '07

26 Oct '07

Hello there, I am wondering if this board is supported at all: Asus M2N-SLI Deluxe, based on an nVidia MCP55 (NF570-SLI), running with an Amd Athlon64 6000+ X2 The lspci output is: 00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1) 00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2) 00:01.2 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a2) 00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2) 00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1) 00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) 00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) 00:05.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) 00:06.0 PCI bridge: nVidia Corporation MCP55 PCI bridge (rev a2) 00:06.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2) 00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) 00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) 00:0a.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) 00:0c.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) 00:0d.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) 00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04) 01:07.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04) 01:07.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) 01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 06:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) 06:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) 07:00.0 VGA compatible controller: nVidia Corporation NV45 [GeForce 6800 GTO] (rev a2) The bios is located inside a PLCC chip, 4MiB (I would think it is an SS49LF..xxx series part) Thanks, -- ------------------------ ---- Stop the RIAA, and their DRM! www.defectivebydesign.org ---- ---- Stop the TCPA from taking away OUR freedom! www.againsttcpa.com/ ----- ---- Arturo Mann, arturo.mann(a)gmail.com ----

3 8

[LinuxBIOS] PT-6IBD motherboard - winmax or azza (i don't know)
by Ziga Mlinar 25 Oct '07

25 Oct '07

Hi everybody. I have a motherboard that has PT-6IBD written on it with big letters. IManufacturer could be Winmax or Azza as I have found out. But i+m not sure. In the attached files are the outputs of 4 programs. # flashrom -V # superiotool -dV # lspci -tvnn # getpir > irq_tables.c The superio chip has the following written on it: Winbond: W83977EF-AW AM. MEGA. 87-96 This is my first post to this mailing list, tell me if there is more info needed. I'll be glad to post it. Žiga

2 1

[LinuxBIOS] [BULDROM] Further categorize boards by vendor
by Jordan Crouse 25 Oct '07

25 Oct '07

With the addition of the Tyan board today, we've reached our 9th platform supported in buildrom (yay!). Its starting to get a little crowded in there, so lets start categorizing the boards to make the list more manageable. I wanted to do it on a CPU basis, but IRC convinced me to do it by board vendor, so here it is. Jordan -- Jordan Crouse Systems Software Development Engineer Advanced Micro Devices, Inc. [BULDROM] Further categorize boards by vendor Buildrom is getting to successful for its own good.. :) Categorize the boards by vendor to make them easier to find. Signed-off-by: Jordan Crouse <jordan.crouse(a)amd.com> Index: buildrom-devel/config/platforms/Config.in =================================================================== --- buildrom-devel.orig/config/platforms/Config.in 2007-10-24 17:23:52.000000000 -0600 +++ buildrom-devel/config/platforms/Config.in 2007-10-24 17:38:37.000000000 -0600 @@ -1,6 +1,31 @@ menu "Platform Configuration" choice + prompt "Vendor for the platform target" + default VENDOR_AMD + help + Select a vendor category for the target you want to build for + +config VENDOR_AMD + bool "AMD" + +config VENDOR_ARTEC + bool "Artec Group" + +config VENDOR_DIGITALLOGIC + bool "Digital Logic" + +config VENDOR_GIGABYTE + bool "Gigabyte" + +config VENDOR_PCENGINES + bool "PC Engines" + +config VENDOR_TYAN + bool "Tyan" +endchoice + +choice prompt "Platform target for the ROM" default PLATFORM_NORWICH help @@ -8,38 +33,47 @@ config PLATFORM_NORWICH bool "AMD Geode LX 'Norwich'" + depends VENDOR_AMD select PLATFORM config PLATFORM_DBE61 bool "Artec Group dbe61" + depends VENDOR_ARTEC select PLATFORM config PLATFORM_ALIX1C bool "PC Engines ALIX1.C" + depends VENDOR_PCENGINES select PLATFORM config PLATFORM_MSM800SEV bool "Digital Logic msm800sev" + depends VENDOR_DIGITALLOGIC select PLATFORM config PLATFORM_DB800 bool "AMD DB800" + depends VENDOR_AMD select PLATFORM config PLATFORM_M57SLI bool "Gigabyte M57SLI" + depends VENDOR_GIGABYTE select PLATFORM config PLATFORM_TYAN_S2882 bool "Tyan S2882" + depends VENDOR_TYAN select PLATFORM config PLATFORM_TYAN_S2891 bool "Tyan S2891" + depends VENDOR_TYAN select PLATFORM config PLATFORM_SERENGETI_CHEETAH bool "AMD Serengeti_Cheetah" + depends VENDOR_AMD select PLATFORM endchoice endmenu

3 4

[LinuxBIOS] r50 - buildrom-devel/config/platforms
by svn＠openbios.org 25 Oct '07

25 Oct '07

Author: jcrouse Date: 2007-10-25 17:05:31 +0200 (Thu, 25 Oct 2007) New Revision: 50 Modified: buildrom-devel/config/platforms/Config.in Log: [BULDROM] Further categorize boards by vendor Buildrom is getting to successful for its own good.. :) Categorize the boards by vendor to make them easier to find. Signed-off-by: Jordan Crouse <jordan.crouse(a)amd.com> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: buildrom-devel/config/platforms/Config.in =================================================================== --- buildrom-devel/config/platforms/Config.in 2007-10-24 22:35:08 UTC (rev 49) +++ buildrom-devel/config/platforms/Config.in 2007-10-25 15:05:31 UTC (rev 50) @@ -1,45 +1,79 @@ menu "Platform Configuration" choice + prompt "Vendor for the platform target" + default VENDOR_AMD + help + Select the vendor for the plaform you are building for + +config VENDOR_AMD + bool "AMD" + +config VENDOR_ARTEC + bool "Artec Group" + +config VENDOR_DIGITALLOGIC + bool "Digital Logic" + +config VENDOR_GIGABYTE + bool "GIGABYTE" + +config VENDOR_PCENGINES + bool "PC Engines" + +config VENDOR_TYAN + bool "Tyan" +endchoice + +choice prompt "Platform target for the ROM" default PLATFORM_NORWICH help - Select the target to build the LinuxBIOS ROM for + Select the platform you are building for config PLATFORM_NORWICH bool "AMD Geode LX 'Norwich'" + depends VENDOR_AMD select PLATFORM config PLATFORM_DBE61 - bool "Artec Group dbe61" + bool "Artec Group DBE61" + depends VENDOR_ARTEC select PLATFORM config PLATFORM_ALIX1C bool "PC Engines ALIX1.C" + depends VENDOR_PCENGINES select PLATFORM config PLATFORM_MSM800SEV - bool "Digital Logic msm800sev" + bool "Advanced Digital Logic MSM800SEV" + depends VENDOR_DIGITALLOGIC select PLATFORM config PLATFORM_DB800 bool "AMD DB800" + depends VENDOR_AMD select PLATFORM config PLATFORM_M57SLI - bool "Gigabyte M57SLI" + bool "GIGABYTE GA-M57SLI-S4" + depends VENDOR_GIGABYTE select PLATFORM config PLATFORM_TYAN_S2882 bool "Tyan S2882" + depends VENDOR_TYAN select PLATFORM config PLATFORM_TYAN_S2891 bool "Tyan S2891" + depends VENDOR_TYAN select PLATFORM config PLATFORM_SERENGETI_CHEETAH - bool "AMD Serengeti_Cheetah" + bool "AMD Serengeti-Cheetah" + depends VENDOR_AMD select PLATFORM endchoice endmenu

1 0

Re: [LinuxBIOS] r2875 - trunk/util/flashrom
by Peter Stuge 25 Oct '07

25 Oct '07

On Thu, Oct 18, 2007 at 02:29:05AM +0200, svn(a)openbios.org wrote: > The following boards require the specification of the board name, if > no LinuxBIOS table is found: > @@ -55,9 +55,11 @@ > * ASUS P5A: use -m asus:p5a > * IBM x3455: use -m ibm:x3455 > * EPoX EP-BX3: use -m epox:ep-bx3 > -* GIGABYTE GA-M57SLI v2.0: use -m gigabyte:m57sli > -* GIGABYTE GA-M61P-S3: use -m gigabyte:m61ps3 > +* GIGABYTE GA-M57SLI-S4 v2.0: use -m gigabyte:m57sli > +* GIGABYTE GA-M61P-S3: use -m gigabyte:m61p > +* MSI K8N Neo3: use -m msi:k8n-neo3 Could we get this compiled into flashrom so that it can be shown if a board can't be detected? //Peter

2 1

[LinuxBIOS] r2897 build service
by LinuxBIOS information 25 Oct '07

25 Oct '07

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "stuge" checked in revision 2897 to the LinuxBIOS source repository and caused the following changes: Change Log: Added Am29LV040B Looking through the sources of Uniflash utility I found that this chip is no more no less than low-voltage variant of Am29F040B but with different ID. So I created a very quick patch (attached). Signed-off-by: Peter Lemenkov <lemenkov(a)gmail.com> Acked-by: Peter Stuge <peter(a)stuge.se> Build Log: Compilation of arima:hdama is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=hdama&vendor=… Compilation of ibm:e325 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=e325&vendor=i… Compilation of ibm:e326 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=e326&vendor=i… Compilation of iei:juki-511p is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=juki-511p&ven… Compilation of iwill:dk8s2 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=dk8s2&vendor=… Compilation of iwill:dk8x is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=dk8x&vendor=i… Compilation of newisys:khepri is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2897&device=khepri&vendor… If something broke during this checkin please be a pain in stuge's neck until the issue is fixed. If this issue is not fixed within 24h the revision should be backed out. Best regards, LinuxBIOS automatic build system

1 0

[LinuxBIOS] [flashrom] patch: added Am29LV040B (trivial)
by Peter Lemenkov 25 Oct '07

25 Oct '07

Hello All! Looking through the sources of Uniflash utility I found that this chip is no more no less than low-voltage variant of Am29F040B but with different ID. So I created a very quick patch (attached). BTW anyone have tried to reuse sources of Uniflash. Although it uses some proprietary calls I found it useful. Signed-off-by: Peter Lemenkov <lemenkov(a)gmail.com> -- With best regards!

2 1

[LinuxBIOS] r2897 - trunk/util/flashrom
by svn＠openbios.org 25 Oct '07

25 Oct '07

Author: stuge Date: 2007-10-25 06:11:11 +0200 (Thu, 25 Oct 2007) New Revision: 2897 Modified: trunk/util/flashrom/flash.h trunk/util/flashrom/flashchips.c Log: Added Am29LV040B Looking through the sources of Uniflash utility I found that this chip is no more no less than low-voltage variant of Am29F040B but with different ID. So I created a very quick patch (attached). Signed-off-by: Peter Lemenkov <lemenkov(a)gmail.com> Acked-by: Peter Stuge <peter(a)stuge.se> Modified: trunk/util/flashrom/flash.h =================================================================== --- trunk/util/flashrom/flash.h 2007-10-24 20:17:04 UTC (rev 2896) +++ trunk/util/flashrom/flash.h 2007-10-25 04:11:11 UTC (rev 2897) @@ -63,6 +63,7 @@ #define AMD_ID 0x01 /* AMD */ #define AM_29F040B 0xA4 +#define AM_29LV040B 0x4F #define AM_29F016D 0xAD #define AMIC_ID 0x37 /* AMIC */ Modified: trunk/util/flashrom/flashchips.c =================================================================== --- trunk/util/flashrom/flashchips.c 2007-10-24 20:17:04 UTC (rev 2896) +++ trunk/util/flashrom/flashchips.c 2007-10-25 04:11:11 UTC (rev 2897) @@ -28,6 +28,8 @@ struct flashchip flashchips[] = { {"Am29F040B", AMD_ID, AM_29F040B, 512, 64 * 1024, probe_29f040b, erase_29f040b, write_29f040b}, + {"Am29LV040B", AMD_ID, AM_29LV040B, 512, 64 * 1024, + probe_29f040b, erase_29f040b, write_29f040b}, {"Am29F016D", AMD_ID, AM_29F016D, 2048, 64 * 1024, probe_29f040b, erase_29f040b, write_29f040b}, {"AE49F2008", ASD_ID, ASD_AE49F2008, 256, 128,

1 0

[LinuxBIOS] [PATCH] fix vga output in v2 qemu target
by Stefan Reinauer 25 Oct '07

25 Oct '07

see patch... not pretty, but it does the job. I vote for making v3 pretty. The v2 target of Qemu is not worth more effort. -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

2 1

← Newer
1
...
10
11
12
13
14
15
16
...
49
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 October 2007