coreboot

coreboot@coreboot.org

5 participants
39705 discussions

Wow! A hole in linuxbios PCI mastery setup?
by Kevin Hester 14 Jan '03

14 Jan '03

Hi all, I think I've noticed a general linux-BIOS problem: Some PCI devices are not being enabled for bus mastery! Let me more clearly explain the context: 1) According to my handy PCI book: All bus master capable PCI devices must implement bit 2 of the command register. 2) Most devices that implement this bit power up default to 1. This is good, because linuxbios has not been setting this bit to 1. 3) A user reported a problem with a 802.11b card, and upon investigation I discovered the chip used on this card does not default to a 1 for bus master enable. (See attached lspci output) After some testing, I realized that the same card on a non LinuxBIOS based machine works correctly - i.e. by the time the kernel is up I see that this bus master enable bit is 1. I know that the Award BIOS on this second machine must have set this bus master enable bit - because the kernel and drivers are identical. I verified this by dumping the appropriate config registers early on in kernel start-up. My theory is that the Award BIOS is doing something that we are not: During the IO/Mem space assignment process it is setting the bus master bit for most devices. By "most devices" I mean any device that is not behind a bridge that inhibits bus mastery. My PCI Sys Arch book (by Shanley and Anderson) says that some crummy bridges may not support bus mastery (i.e. they have a bit 2 of the command register that always reads as zero). If a device is behind a bridge that does not support mastery, it must have its mastery bit cleared. Does anyone have a copy of the $$$ PCI architecture spec so they can check this? My PCI System Architecture book is vague on the topic. My proposed fix: * Add pci_enable_bus_masters() that does the following: * Calls pci_enable_bus_master(0) to enable devices directly connected to the host bridge * Add pci_enable_bus_master(devfn) that does the following: * Try to enable bus mastery for this device. * If the device is a bridge: * If the write of master enable fails, then write zero to all "bus master enable" bits for devices behind that bridge (including all subordinate buses) * If the write of master enable succeeds, then call pci_enable_bus_master for all devices on the secondary bus behind this bridge. (i.e. not for all subordinate busses) I've added these functions and called them after the standard linuxbios PCI setup. The problem card now works as well as it did with Award BIOS. What to ya'll think? I'm particularly interested in quotes from the PCI architecture spec. Kevin --- On a linux BIOS machine: 00:14.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01) Subsystem: D-Link System Inc: Unknown device 3501 Flags: medium devsel, IRQ 5 Memory at feb00000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 00: 60 12 73 38 02 00 90 02 01 00 80 02 08 40 00 00 10: 08 00 b0 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 11 01 35 30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 00 00 40: 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 7e e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 On a non linux BIOS machine: 00:0a.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01) Subsystem: D-Link System Inc: Unknown device 3501 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at ee000000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 00: 60 12 73 38 07 00 90 02 01 00 80 02 08 20 00 00 10: 08 00 00 ee 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 11 01 35 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 00 00 40: 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 7e e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

4 5

[ANNOUNCE] mkelfImage 2.0
by ebiederman＠lnxi.com 14 Jan '03

14 Jan '03

After a long and tedious grind I am pleased to announce version 2.0 of mkelfImage. New features. - One single binary - Itanium support - All of the code is in C. - New and exciting easter eggs (err bugs can you find them before I do?...) Available at: ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-2.0.tar.gz rpms can be built with rpm -ta mkelfImage-2.0.tar.gz alien will make perfectly serviceable debs from those... The decision to go with pure C is that it is both relatively portable, and it reduces maintenance when I add a feature. I tried perl and it handles the interesting code only with the utmost protest. Adding checksums and other interesting pieces is much easier if it only needs to be both coded in one language, and usually the C implementation is much easier than the perl. Plus C is fast :) Have fun, Eric

2 2

help!
by xu xuning 14 Jan '03

14 Jan '03

Hi, I have success to boot from my doc by using the pre-made images from http://www.cwlinux.com/download/,but now i want to know how to boot from IDE drive? BTW,how to use winfast6300-etherboot.rom and winfast6300-ide.rom? _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

1 0

[commit] TigerMPX (760MPX)
by steven james 13 Jan '03

13 Jan '03

Greetings, Primary and fallback images are working with this commit. It's looking fairly solid. G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

1 0

Option Parameters for Linuxbios.
by sivakumar 11 Jan '03

11 Jan '03

Hi all, Can any one help me in understanding the following parameter used for the configuration of the LinuxBIOS. biosbase 0xffff0000 rambase 0x00000800 option XIP_ROM_BASE=0xffff0000 option XIP_ROM_SIZE=0x10000 option STACK_SIZE=0x2000 option ZKERNEL_START=0xfff40000 option ZKERNEL_MASK=0x3ed Also I have one more query, When executing the linuxbios, it is executing the instrcution twice (i.e., I am getting output twice). I have attached the serial console output below. How to get rid of this? LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4 (four)starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 000001d0Ram Enable 5 Ram Enable 6 Content of CAPPTR 04Content of BCC 06Ram4 Ram5 Ram6 Copying LinuxBIOS to ram. 00000800ffff0f80 ecx value during image copy 00000000Jumping to LinuxBIOS. Calling hardwaremain ... LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4 (four)starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 000001d0Ram Enable 5 Ram Enable 6 Content of CAPPTR 04Content of BCC 06Ram4 Ram5 Ram6 Copying LinuxBIOS to ram. 00000800ffff0f80 ecx value during image copy 00000000Jumping to LinuxBIOS. Calling hardwaremain ... Thanks, Siva -- sivakumar <sivakumar.subramani(a)wipro.com> wipro

4 6

Geode sc2200 vga
by John Allen 11 Jan '03

11 Jan '03

I have successfully built LinuxBIOS to load a kernel from my IDE drive and boot using a serial console. Now I would like to test the VGA funtionality of my board. Has anyone had any experience getting the VGA to turn on and work within LinuxBIOS and/or Linux? John

6 8

[commit] Support for Tyan TigerMPX (amd760MPX)
by steven james 11 Jan '03

11 Jan '03

Greetings, I have made the initial commit for this board/chipset Currently, I have it booting into Linux with everything appearing to work. Early next week will be testing, getting primary/fallback builds working and general cleanup. G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

1 0

missing _estack
by gnat＠gnat.ca 11 Jan '03

11 Jan '03

Hello, I've been trying to figure out how these things are setup. If I use one of the sis5xx mainboard configs, I get an error stating that _estack is undefined. Where is it supposed to be? Obviously, it has something to do with setting up a stack. I just don't understand where it is supposed to come from. Since I'm patterning my mainboard (sis530 based) on those as examples. This causes a small problem. Can anyone help me? -- Nathanael Noblet ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 1

via epia 800
by Jarmo Torvinen 11 Jan '03

11 Jan '03

Hi all, I'm building a (multimedia) set-top-box using Via epia 800-mainboard. The system works fine with linux except the bios boot-delay is too long. I was hoping if someone could point me to a simple documentation howto setup linuxbios for this board for reduced boot time? I have downloaded the rom-image from http://www.cwlinux.com/downloads/linuxbios-sdk/images/romimages/epia.rom but I'm still wondering if it is good for booting from hda1? Does the kernel installed in hda1 have to be the cwlinux-patched version or may I use my own vanilla-kernel? I think there will be lot of questions regarding this matter in the future because of the numerous people building around this mobo, so maybe someone who got it working could write a simple HowTo or FAQ of this "issue". Jarmo Torvinen

2 1

Geode debugging
by Adam Bezanson 11 Jan '03

11 Jan '03

Anyone know what is typically used for debugging a Geode x200 based design? By this I mean a JTAG/BDM or ICE for debugging say, LinuxBIOS and the Linux Kernel/Linux device drivers. I think this would be needed to support audio (VSA/SMM support) since getting it working without an ICE of some kind would be next to impossible. I can't really find any info on the web about it other then here: http://www.fs2.com they make an ISA-GEODE but it only seems to support GX2 based processors. Any suggestions? Thanks, Adam

3 3

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