coreboot November 2006

coreboot@coreboot.org

61 participants
260 discussions

[LinuxBIOS] r2492 - trunk/LinuxBIOSv2/util/flashrom
by svn＠openbios.org 07 Nov '06

07 Nov '06

Author: stepan Date: 2006-11-07 11:22:20 +0100 (Tue, 07 Nov 2006) New Revision: 2492 Modified: trunk/LinuxBIOSv2/util/flashrom/flash_enable.c Log: Support for VIA VT82C686 in flashrom utility (trivial) closes #30 Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/LinuxBIOSv2/util/flashrom/flash_enable.c =================================================================== --- trunk/LinuxBIOSv2/util/flashrom/flash_enable.c 2006-11-06 10:51:15 UTC (rev 2491) +++ trunk/LinuxBIOSv2/util/flashrom/flash_enable.c 2006-11-07 10:22:20 UTC (rev 2492) @@ -414,6 +414,7 @@ {0x1106, 0x8231, "VT8231", enable_flash_vt8231}, {0x1106, 0x3177, "VT8235", enable_flash_vt8235}, {0x1106, 0x3227, "VT8237", enable_flash_vt8231}, + {0x1106, 0x0686, "VT82C686", enable_flash_amd8111}, {0x1078, 0x0100, "CS5530", enable_flash_cs5530}, {0x100b, 0x0510, "SC1100", enable_flash_sc1100}, {0x1039, 0x0008, "SIS5595", enable_flash_sis5595},

1 0

[LinuxBIOS] asus A8N-VM CSM
by Ward Vandewege 06 Nov '06

06 Nov '06

Hi all, On Thursday, Oct 12, 2006, Uwe Hermann said: >I'd really, really like to see a bunch of popular, cheap, mainstream >boards supported out of the box. IMHO this is really essential to get >more developers on board. > >Looking at a few random shops here in Germany, it seems that the most >popular brands are Asus, ASRock, MSI, Gigabyte for mainbaords in the >price range of 40-80 Euros. So; we've acquired a couple of machines based on an Asus A8N-VM CSM board (http://usa.asus.com/products4.aspx?l1=3&l2=15&l3=210&model=766&modelmenu=1), with an Opteron 150. Uwe, this board costs $80 at Newegg so I guess it falls into your cheap & common category. This is the lspci output: 0000:00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 0000:00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 0000:00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 0000:00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 0000:00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 0000:00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 0000:00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 0000:00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 0000:00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 0000:00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 0000:00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 0000:00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2) 0000:00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 0000:00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2) 0000:00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2) 0000:00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 0000:00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 0000:00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 0000:00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 0000:00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 0000:00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 0000:00:10.1 0403: nVidia Corporation MCP51 High Definition Audio (rev a2) 0000:00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 0000:03:00.0 Ethernet controller: Intel Corporation: Unknown device 105e (rev 06) 0000:03:00.1 Ethernet controller: Intel Corporation: Unknown device 105e (rev 06) 0000:04:05.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 0000:04:08.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 04) The intel ethernet controllers are plug in cards. The SuperIO chip is - according to the URL pasted above - an Nvidia nforce 430MCP. The actual chip on the mainboard reads: Nvidia P5080239 0534A2 MCP51-N-A2 GH 9940.1 The bios rom is an SST 49LF0048. I tried flashrom. No dice: # ./flashrom -V Calibrating delay loop... Setting up microsecond timing loop 601M loops per second ok No LinuxBIOS table found. Warning: Unknown system. Flash detection will most likely fail. Trying Am29F040B, 512 KB probe_29f040b: id1 0xff, id2 0xff Trying Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Trying At29C040A, 512 KB probe_jedec: id1 0xff, id2 0xff Trying Mx29f002, 256 KB probe_29f002: id1 0xec, id2 0x66 Trying SST29EE020A, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying SST28SF040A, 512 KB probe_28sf040: id1 0xff, id2 0xff Trying SST39SF010A, 128 KB probe_jedec: id1 0x50, id2 0x0 Trying SST39SF020A, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying SST39SF040, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST39VF020, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying SST49LF040B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF040, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF020A, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF002A/B, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying SST49LF003A/B, 384 KB probe_jedec: id1 0x6d, id2 0xe1 Trying SST49LF004A/B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying Pm49FL002, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying Pm49FL004, 512 KB probe_jedec: id1 0xff, id2 0xff Trying W29C011, 128 KB probe_jedec: id1 0x50, id2 0x0 Trying W29C020C, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying W49F002U, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying W49V002A, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying W49V002FA, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying W39V040A, 512 KB probe_jedec: id1 0xff, id2 0xff Trying W39V040B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying M29F040B, 512 KB probe_29f040b: id1 0xff, id2 0xff Trying M29F400BT, 512 KB probe_m29f400bt: id1 0xff, id2 0xff Trying 82802ab, 512 KB probe_82802ab: id1 0xff, id2 0xff Trying 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Trying F49B002UA, 256 KB probe_jedec: id1 0xec, id2 0x66 Trying LHF00L04, 1024 KB probe_lhf00l04: id1 0xff, id2 0xff No EEPROM/flash device found. This is with the SST part switched in (biossavior). Similar problem with the biossavior set to RD1: # ./flashrom -V Calibrating delay loop... Setting up microsecond timing loop 601M loops per second ok No LinuxBIOS table found. Warning: Unknown system. Flash detection will most likely fail. Trying Am29F040B, 512 KB probe_29f040b: id1 0xff, id2 0xff Trying Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Trying At29C040A, 512 KB probe_jedec: id1 0xff, id2 0xff Trying Mx29f002, 256 KB probe_29f002: id1 0xcf, id2 0x6f Trying SST29EE020A, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying SST28SF040A, 512 KB probe_28sf040: id1 0xff, id2 0xff Trying SST39SF010A, 128 KB probe_jedec: id1 0xff, id2 0xff Trying SST39SF020A, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying SST39SF040, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST39VF020, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying SST49LF040B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF040, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF020A, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF002A/B, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying SST49LF003A/B, 384 KB probe_jedec: id1 0xa3, id2 0xb8 Trying SST49LF004A/B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying Pm49FL002, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying Pm49FL004, 512 KB probe_jedec: id1 0xff, id2 0xff Trying W29C011, 128 KB probe_jedec: id1 0xff, id2 0xff Trying W29C020C, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying W49F002U, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying W49V002A, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying W49V002FA, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying W39V040A, 512 KB probe_jedec: id1 0xff, id2 0xff Trying W39V040B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying M29F040B, 512 KB probe_29f040b: id1 0xff, id2 0xff Trying M29F400BT, 512 KB probe_m29f400bt: id1 0xff, id2 0xff Trying 82802ab, 512 KB probe_82802ab: id1 0xff, id2 0xff Trying 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Trying F49B002UA, 256 KB probe_jedec: id1 0xcf, id2 0x6f Trying LHF00L04, 1024 KB probe_lhf00l04: id1 0xff, id2 0xff No EEPROM/flash device found. Is there any hope for this board? If so; what should I try next? Thanks, Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

4 14

Re: [LinuxBIOS] Tyan s2892 the OLPC way
by Lu, Yinghai 06 Nov '06

06 Nov '06

Any reason for using kernel in flash: Target system only have usb keyboard installed. YH

1 0

Re: [LinuxBIOS] Disabled device help
by Lu, Yinghai 06 Nov '06

06 Nov '06

That should be fine. YH -----Original Message----- From: Myles Watson [mailto:myles@mouselemur.cs.byu.edu] Sent: Monday, November 06, 2006 9:37 AM To: Lu, Yinghai; linuxbios(a)linuxbios.org Subject: RE: [LinuxBIOS] Disabled device help Thanks a lot! It worked fine, except it missed the last 4GB of the allocation. This is an ugly way of getting it back. I'm not sure what the elegant way would be. The lower 32-bits need to be filled with ones in order for the space to be allocated correctly. Otherwise a 4GB allocation would show up as a one byte allocation. Now /proc/iomem shows my device at 8000000000-bfffffffff Myles --- drivers/pci/probe.c 2006-11-06 09:23:03.000000000 -0700 +++ drivers/pci/probe_new.c 2006-11-06 10:17:08.000000000 -0700 @@ -203,7 +203,7 @@ res->end = res->start + sz; if (szhi) { /* This BAR needs > 4GB? Wow. */ - res->end |= (unsigned long)szhi<<32; + res->end |= ((unsigned long)szhi<<32|0xffffffffUL); } #else if (szhi) { >Please check the patch. >YH >The Kernel pci_read_bases in drivers/pci/probe.c. has problem when size >if bigger than 4G. >It will first check the 32 bit SPACE_ADDRESS, and pci_size will return >0, So it will skip that resource. And the pre-set values is ignored. >And later, it will try to allocate the value. It will fail. >I will produce one patch for you. >YH >>My large device gets disabled somewhere in LinuxBIOS or the kernel. This >>is the encouraging line from LinuxBIOS telling me that the registers are >>indeed set correctly. >>PCI: 05:01.0 18 <- [8000000000 - bfffffffff] prefmem64 >>Unfortunately, Linux sees something different and fails to allocate this >>region because it sees it at 00000080-000000bf and that conflicts with >>other things. >>Does anyone have a pointer to where I should look for this problem? Has >>anyone else had problems with devices larger than 4GB? >>Thanks, >>Myles

1 0

Re: [LinuxBIOS] Disabled device help
by Lu, Yinghai 06 Nov '06

06 Nov '06

The Kernel pci_read_bases in drivers/pci/probe.c. has problem when size if bigger than 4G. It will first check the 32 bit SPACE_ADDRESS, and pci_size will return 0, So it will skip that resource. And the pre-set values is ignored. And later, it will try to allocate the value. It will fail. I will produce one patch for you. YH -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Lu, Yinghai Sent: Friday, November 03, 2006 11:46 AM To: myles(a)mouselemur.cs.byu.edu; LinuxBIOS Subject: Re: [LinuxBIOS] Disabled device help Boot log? In LinuxBIOS, there is CONFIG_PCI_64BIT_PREF_MEM, did you try to enable it in you MB Options.lb In the kernel, there is pci_assign_unassigned_resources that try to allocate resource for some devices, and it could cause problem because Opteron could bave multi ht chain, Aka peer root bus, and every root bus need to have its own ioport_resource, and iomem_resource. But that only happen when BIOS is not allocating resource correctly. And LinuxBIOS does a good job, and every device have be handled properly. In case, you have werid pci devices, you still can use pci_quirks in kernel to do some fix up. YH -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Myles Watson Sent: Friday, November 03, 2006 11:02 AM To: 'LinuxBIOS' Subject: [LinuxBIOS] Disabled device help My large device gets disabled somewhere in LinuxBIOS or the kernel. This is the encouraging line from LinuxBIOS telling me that the registers are indeed set correctly. PCI: 05:01.0 18 <- [8000000000 - bfffffffff] prefmem64 Unfortunately, Linux sees something different and fails to allocate this region because it sees it at 00000080-000000bf and that conflicts with other things. Does anyone have a pointer to where I should look for this problem? Has anyone else had problems with devices larger than 4GB? Thanks, Myles -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

5 6

Re: [LinuxBIOS] Fwd: Hello, I have a problem to put the linuxbios on my mainboard ms6163.
by Li Haiqiang 06 Nov '06

06 Nov '06

I write the 'ls -xxx' results to the PCI config registers. Can it work? ----- Original Message ---- From: Richard Smith <smithbone(a)gmail.com> To: Li Haiqiang <haiqiang2linux(a)yahoo.com> Cc: LinuxBIOS mailinglist <linuxbios(a)linuxbios.org> Sent: Monday, November 6, 2006 12:25:38 PM Subject: Re: [LinuxBIOS] Fwd: Hello, I have a problem to put the linuxbios on my mainboard ms6163. Li Haiqiang wrote: > What does debug code 0xf9 mean? > It stopped here. Li, The 440bx is NOT COMPLETE. It will NOT function. It is BROKEN. The port is not finished. Its does not enable RAM. Hopefully, one of those translates correctly. Do you understand? To make it work you need to add a lot of code. My earlier email talks about the necessary steps to get 440bx into a working shape. -- Richard A. Smith

3 3

Re: [LinuxBIOS] #14: Rename "stream" to "payload"
by LinuxBIOS 06 Nov '06

06 Nov '06

#14: Rename "stream" to "payload" ----------------------------------+----------------------------------------- Reporter: uwe | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Cosmetic fixes Component: code | Version: v2 Resolution: | Keywords: Due_close: DD/MM/YYYY | Include_gantt: 0 Dependencies: #22 | Due_assign: DD/MM/YYYY Patchstatus: there is no patch | ----------------------------------+----------------------------------------- Changes (by uwe): * patchstatus: => there is no patch -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/14#comment:5> LinuxBIOS <http://www.linuxbios.org/>

1 0

Re: [LinuxBIOS] #22: sed error in abuild
by LinuxBIOS 06 Nov '06

06 Nov '06

#22: sed error in abuild -----------------------------------------+---------------------------------- Reporter: uwe | Owner: uwe Type: defect | Status: closed Priority: critical | Milestone: Component: testsystem | Version: v2 Resolution: fixed | Keywords: Due_close: MM/DD/YYYY | Include_gantt: 0 Dependencies: | Due_assign: MM/DD/YYYY Patchstatus: patch has been committed | -----------------------------------------+---------------------------------- Changes (by uwe): * patchstatus: patch is ready to be committed => patch has been committed -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/22#comment:5> LinuxBIOS <http://www.linuxbios.org/>

1 0

[LinuxBIOS] r2491 - trunk/LinuxBIOSv2/util/abuild
by svn＠openbios.org 06 Nov '06

06 Nov '06

Author: uwe Date: 2006-11-06 11:51:15 +0100 (Mon, 06 Nov 2006) New Revision: 2491 Modified: trunk/LinuxBIOSv2/util/abuild/abuild Log: Fix bug in 'sed' invocation in abuild, which causes build errors in certain situations (Closes #22, refs #14). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/LinuxBIOSv2/util/abuild/abuild =================================================================== --- trunk/LinuxBIOSv2/util/abuild/abuild 2006-11-05 18:50:49 UTC (rev 2490) +++ trunk/LinuxBIOSv2/util/abuild/abuild 2006-11-06 10:51:15 UTC (rev 2491) @@ -163,7 +163,7 @@ sed -i.pre -e s,VENDOR,$VENDOR,g \ -e s,MAINBOARD,$MAINBOARD,g \ - -e s,PAYLOAD,$PAYLOAD,g \ + -e s,payload\ PAYLOAD,payload\ $PAYLOAD,g \ -e s,CROSSCC,"$CC",g \ -e s,CROSS_PREFIX,"$CROSS_COMPILE",g \ -e s,CROSS_HOSTCC,"$HOSTCC",g \

1 0

[LinuxBIOS] #26: flashrom: Support for PIIX4/PIIX4E/PIIX4M
by LinuxBIOS 06 Nov '06

06 Nov '06

#26: flashrom: Support for PIIX4/PIIX4E/PIIX4M ----------------------------+----------------------------------------------- Reporter: uwe | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: flashrom | Version: v2 Keywords: | Include_gantt: 0 Dependencies: | Due_assign: MM/DD/YYYY Due_close: MM/DD/YYYY | ----------------------------+----------------------------------------------- Add support for Intel PIIX4/PIIX4E/PIIX4M based mainboards to flashrom. Tested on real hardware, reading, detecting and writing various chips works. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> --- Just curious: in the datasheet I see three BIOS-related bits, "Lower BIOS Enable", "Extended BIOS Enable", and "1-Meg Extended BIOS Enable". I only enabled the "Extended BIOS Enable" (FFF80000-FFFDFFFF); do I need to touch one of the others, too? -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/26> LinuxBIOS <http://www.linuxbios.org/>

4 14

← Newer
1
...
16
17
18
19
20
21
22
...
26
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 November 2006