coreboot May 2004

coreboot@coreboot.org

35 participants
149 discussions

HDAMA+FILO booting SUSE Linux
by Craig C Forney 12 May '04

12 May '04

First, thanks for fixing the broken sourceforge LinuxBIOS tree earlier this week. I've been using LinuxBIOS successfully for some custom dense board designs being used for hardware verification, primarily running memtest86. I only have a serial port available. I'm using an Arima HDAMA board as a known working testbed for trying software before running it on our own boards. At this point, I'd like to attempt to boot up Linux. The first step is getting it to work properly on the Arima HDAMA board. I have booted and loaded Suse 9.0 Professional (I'm awaiting delivery of 9.1), as well as the Suse 9.1 Live CD, without problems with the standard Phoenix BIOS on the Arima HDAMA board. Using LinuxBIOS plus FILO, I'm not having much luck. I've checked through the archives, but I'm not finding the right combination of steps that works. -- Booting of the Suse 9.0 DVD in an attempt to install Linux on disk gets up to the point where yast has determined the proper partition sizes during it's initial config screens, but then hangs. It's in the middle of the yast formatted screens, so I don't know a good way to copy this to an email. -- Booting an already loaded 9.0 system panics the kernel: POSIX conformance testing by UNIFIX mtrr: v2.02 (20020716)) CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K (64 bytes/line/2 way) CPU: L2 Cache: 1024K (64 bytes/line/8 way) CPU0: stepping 01 per-CPU timeslice cutoff: 5119.55 usecs. task migration cache decay timeout: 10 msecs. Booting processor 1/1 rip 6000 page 000001000261a000 Not respondin<4>NMI Watchdog detected LOCKUP on CPU0, eip ffffffff80204027, registers: CPU 0 Pid: 0, comm: swapper Not tainted RIP: 0010:[<ffffffff80204027>]{serial_in+71} RSP: 0018:ffffffff804dfda8 EFLAGS: 00000202 RAX: 0000000000000000 RBX: 00000000000f4238 RCX: 0000000000008000 RDX: 00000000000003fd RSI: 0000000000000005 RDI: ffffffff804837a0 RBP: ffffffff804837a0 R08: 000000000000006e R09: 00000000409fa439 R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff80413bf4 R13: 000000000000000d R14: 0000000000000010 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff804cb3c0(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0 Process swapper (pid: 0, stackpage=ffffffff804df000) Stack: ffffffff804dfda8 0000000000000018 0000000000040000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Call Trace: <EOE> [<ffffffff80209ff0>]{serial_console_write+96} [<ffffffff80124fcc>]{__call_console_drivers+76} [<ffffffff80125127>]{call_console_drivers+231} [<ffffffff801254b2>]{release_console_sem+82} [<ffffffff80125355>]{vprintk+357} [<ffffffff801253fd>]{printk+141} [<ffffffff802d164c>]{__delay+12} Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89 d0 83 f8 console shuts up ... -- Booting the Suse 9.1 Live CD (I copied all the files on the Live CD to the root file system on an already installed Suse 9.0 system) boot: hda3:/livecd/vmlinuz root=/dev/hda3 initrd=hda3:/livecd/initrd.gz console=ttyS0,115200 Found Linux version 2.6.4-52-default (geeko@buildhost) #1 Wed Apr 7 02:08:30 UTC 2004 bzImage. Loading kernel... ok Loading initrd... ok Jumping to entry point... Linux version 2.6.4-52-default (geeko@buildhost) (gcc version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 0000000040000000 (usable) 128MB vmalloc/ioremap area available. 128MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 262144 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:16 HighMem zone: 32768 pages, LIFO batch:8 DMI not present. ACPI: Unable to locate RSDP Built 1 zonelists Kernel command line: root=/dev/hda3 console=ttyS0,115200 Initializing CPU#0 PID hash table entries: 4096 (order 12: 32768 bytes) CKRM Initialized Detected 1403.889 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Memory: 1009620k/1048576k available (1969k kernel code, 37972k reserved, 677k data, 212k init, 131072k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 2760.70 BogoMIPS Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. Failure registering capabilities with the kernel selinux_register_security: Registering secondary module capability Capability LSM initialized Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) checking if image is initramfs... it is Freeing initrd memory: 26442k freed CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: AMD 02/05 stepping 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX do_initcalls init_elf_binfmt NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay ACPI: ACPI tables contain no PCI IRQ routing entries PCI: Invalid ACPI-PCI IRQ routing table PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) ... the first call_usermodehelper: pci_bus CPU 0: Machine Check Exception: 0000000000000004 Bank 4: b200000000070f0f Kernel panic: CPU context corrupt So, it's pretty clear I am missing a crucial step (or two or three) to booting Linux successfully with LinuxBIOS+FILO. I'd appreciate some help in identifying the basic steps. Thanks, Craig Forney Opus Innovations LLC

1 0

flash_rom with exclude range
by YhLu 12 May '04

12 May '04

Ollie, I add exclude range feature to the Pm49FL004, and it should apply to other chip. But can not make getopt work with input parameter. Please check it. I hardcode exclude_start_position to 0x60000, and exclude_end_postion to 0x8000. Regards YH

1 0

答复: Lessons learned and more ???
by YhLu 12 May '04

12 May '04

How about the mem install configuration? Regards YH -----邮件原件----- 发件人: Jay Miller [mailto:jmiller@actuality-systems.com] 发送时间: 2004年5月12日 9:43 收件人: linuxbios(a)clustermatic.org 主题: Lessons learned and more ??? Thanks everyone for your help! It took me some time to realize the reason that I wasn't seeing any data on the VGA console is because it doesn't work on the S2885. But I have my null modem connected and am seeing lots of interesting stuff now. YH sent me a pre-built S2885 image and the FIRST time it executed I got this: LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 starting... setting up resource map....done. coherent_ht_finalize done Ram1.00 Ram1.01 Ram2.00 Ram2.01 No memory for this cpu Ram3 Initializing memory: done Initializing memory: ........................................................... ........................................................................ ........................................................................ ........ ........................................................................ . failed Clearing LinuxBIOS memory: done Ram4 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 booting... Finding PCI configuration type. PCI: Using configuration type 1 Enumerating static devices... Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Northbridge Enumerating: AMD K8 CPU Enumerating: AMD K8 Enumerating: AMD 8111 Southbridge Enumerating: Winbond w83627hf Enumerating buses... amdk8_scan_root_bus amdk8_scan_root_bus: start scaning pci bus PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [ffff/ffff] enabled PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.1 No device operations PCI: 00:19.2 [ffff/ffff/00ffff] has unknown h PCI: 00:19.2 No device operations PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.3 No device operations amdk8_scan_chains max: 0 starting... Hyper transport scan link: 0 max: 1 PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004 HyperT reset not needed PCI: pci_scan_bus for bus 1 PCI: 01:01.0 [1022/7454] ops PCI: 01:01.0 [1022/7454] enabled PCI: 01:02.0 [1022/7455] bus ops PCI: 01:02.0 [1022/7455] enabled PCI: pci_scan_bus for bus 2 PCI: 02:00.0 [10de/0333] enabled PCI: pci_scan_bus returning with max=02 PCI: pci_scan_bus returning with max=02 Hyper transport scan link: 0 new max: 2 Hypertransport scan link done Hyper transport scan link: 2 max: 3 PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003 amd8111_enable_dev: enabling PCI: 03:00.0 [1022/7460] PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007 HyperT reset not needed PCI: pci_scan_bus for bus 3 PCI: 03:01.0 [1022/7450] bus ops PCI: 03:01.0 [1022/7450] enabled PCI: 03:01.1 [1022/7451] ops PCI: 03:01.1 [1022/7451] enabl PCI: 03:02.0 [1022/7450] bus ops PCI: 03:02.0 [1022/7450] enabled PCI: 03:02.1 [1022/7451] ops PCI: 03:02.1 [1022/7451] enabled amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460] PCI: 03:03.0 [1022/7460] bus ops amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460] PCI: 03:03.0 [1022/7460] enabled amd8111_enable_dev: enabling PCI: 03:04.0 [1022/7468] PCI: 03:04.0 [1022/7468] bus ops amd8111_enable: enabling PCI: 03:04.0 [1022/7468] PCI: 03:04.0 [1022/7468] enabled amd8111_enable_dev: enabling PCI: 03:04.1 [102 PCI: 03:04.1 [1022/7469] ops amd8111_enable_dev: enabling PCI: 03:04.1 [1022/7469] PCI: 03:04.1 [1022/7469] enabled amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a] amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a] PCI: 03:04.2 [1022/746a] enabled amd8111_enable_dev: enabling PCI: 03:04.3 [1022/746b] PCI: 03:04.3 [1022/746b] ops amd8111_enable: enabling PCI: 03:04.3 [1022/746b] PCI: 03:04.3 [1022/746b] enabled amd8111_enable_dev: enabling PCI: 03:04.5 [1022/746d] PCI: 03:04.5 [1022/746d] ops amd8111_enable: enabling PCI: 03:04.5 [1022/746d] PCI: 03:04.5 [1022/746d] enabled amd8111_enable_dev: enabling PCI: 03:04.6 [1022/746e] PCI: 03:04.6 [1022/746e] ops amd8111_enable: disabling PCI: 03:04.6 [1022/746e] PCI: 03:04.6 [1022/746e] disabled PCI: pci_scan_bus for bus 4 PCI: 04:09.0 [14e4/16a7] enabled PCI: pci_scan_bus returning with max=04 PCI: pci_scan_bus for bus 5 PCI: pci_scan_bus returning with max=05 PCI: pci_scan_bus for bus 6 amd8111_enable_dev: enabling PCI: 06:00.0 [1022/7464] PCI: 06:00.0 [102 amd8111_enable: enabling PCI: 06:00.0 [1022/7464] PCI: 06:00.0 [1022/7464] enabled amd8111_enable_dev: enabling PCI: 06:00.1 [1022/7464] PCI: 06:00.1 [1022/7464] ops amd8111_enable: enabling PCI: 06:00.1 [1022/7464] PCI: 06:00.1 [1022/7464] enabled amd8111_enable_dev: enabling PCI: 06:00.2 [1022/7463] PCI: 06:00.2 [1022/7463] ops amd8111_enable: disabling PCI: 06:00.2 [1022/7463] PCI: 06:00.2 [1022/7463] disabled amd8111_enable_dev: enabling PCI: 06:01.0 [1022/7462] PCI: 06:01.0 [1022/7462] ops PCI: 06:01.0 [1022 PCI: 06:01.0 [1022/7462] disabled PCI: 06:0b.0 [1095/3114] enabled PCI: 06:0c.0 [104c/8023] ops PCI: 06:0c.0 [104c/8023] enabled PCI: pci_scan_bus returning with max=06 scan_static_bus for PCI: 03:04.0 PNP: 002e.0 enabled PNP: 002e.1 disabled PNP: 002e.2 enabled PNP: 002e.3 disabled PNP: 002e.5 enabled PNP: 002e.6 disabled PNP: 002e.7 disabled PNP: 002e.8 disabled PNP: 002e.9 disabled PNP: 002e.a disabled PNP: 002e.b enabled scan_static_bus done PCI: pci_scan_bus returning with max=06 Hyper transport scan link: 2 new Hypertransport scan link done amdk8_scan_chains max: 6 done amdk8_scan_chains max: 6 starting... This looked pretty good, but I didn't know what it was trying to start. Unfortunately the next time the same image executed (reset via power cycle) I got this: LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting... setting up resource map....done. No connection to Node 1. ht reset - LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting... setting up resource map....done. No connection to Node 1. Ram1.00 Ram1.01 Ram2.00 Ram2.01 No memory for this cpu Ram3 Initializing memory: done Initializing memory: ........................................................... ........................................................................ ........ ........................................................................ ........ ........................................................................ . failed Clearing LinuxBIOS memory: done Ram4 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 booting... Has anyone seen this issue? Is something not getting reset? BTW, my own image does the same thing. Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

Re: Dealing with Bus Master Enable
by YhLu 12 May '04

12 May '04

OK for me. YH -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年5月12日 9:40 收件人: LinuxBIOS; YhLu 主题: Dealing with Bus Master Enable YHLu, I have a new idea about the bus master enable and subsystem ids. We should do it with config tool. We can add new config keywords like busmaster and subsystem and use some generic code to enable the bit and program the subsystems ids. Thus we can remove a lot of codes in src/driver and mainboard/tyan. How do you think ? Ollie

1 0

Lessons learned and more ???
by Jay Miller 12 May '04

12 May '04

Thanks everyone for your help! It took me some time to realize the reason that I wasn't seeing any data on the VGA console is because it doesn't work on the S2885. But I have my null modem connected and am seeing lots of interesting stuff now. YH sent me a pre-built S2885 image and the FIRST time it executed I got this: LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 starting... setting up resource map....done. coherent_ht_finalize done Ram1.00 Ram1.01 Ram2.00 Ram2.01 No memory for this cpu Ram3 Initializing memory: done Initializing memory: ........................................................... ........................................................................ ........................................................................ ........ ........................................................................ . failed Clearing LinuxBIOS memory: done Ram4 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 booting... Finding PCI configuration type. PCI: Using configuration type 1 Enumerating static devices... Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Northbridge Enumerating: AMD K8 CPU Enumerating: AMD K8 Enumerating: AMD 8111 Southbridge Enumerating: Winbond w83627hf Enumerating buses... amdk8_scan_root_bus amdk8_scan_root_bus: start scaning pci bus PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [ffff/ffff] enabled PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.1 No device operations PCI: 00:19.2 [ffff/ffff/00ffff] has unknown h PCI: 00:19.2 No device operations PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.3 No device operations amdk8_scan_chains max: 0 starting... Hyper transport scan link: 0 max: 1 PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004 HyperT reset not needed PCI: pci_scan_bus for bus 1 PCI: 01:01.0 [1022/7454] ops PCI: 01:01.0 [1022/7454] enabled PCI: 01:02.0 [1022/7455] bus ops PCI: 01:02.0 [1022/7455] enabled PCI: pci_scan_bus for bus 2 PCI: 02:00.0 [10de/0333] enabled PCI: pci_scan_bus returning with max=02 PCI: pci_scan_bus returning with max=02 Hyper transport scan link: 0 new max: 2 Hypertransport scan link done Hyper transport scan link: 2 max: 3 PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003 amd8111_enable_dev: enabling PCI: 03:00.0 [1022/7460] PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007 HyperT reset not needed PCI: pci_scan_bus for bus 3 PCI: 03:01.0 [1022/7450] bus ops PCI: 03:01.0 [1022/7450] enabled PCI: 03:01.1 [1022/7451] ops PCI: 03:01.1 [1022/7451] enabl PCI: 03:02.0 [1022/7450] bus ops PCI: 03:02.0 [1022/7450] enabled PCI: 03:02.1 [1022/7451] ops PCI: 03:02.1 [1022/7451] enabled amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460] PCI: 03:03.0 [1022/7460] bus ops amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460] PCI: 03:03.0 [1022/7460] enabled amd8111_enable_dev: enabling PCI: 03:04.0 [1022/7468] PCI: 03:04.0 [1022/7468] bus ops amd8111_enable: enabling PCI: 03:04.0 [1022/7468] PCI: 03:04.0 [1022/7468] enabled amd8111_enable_dev: enabling PCI: 03:04.1 [102 PCI: 03:04.1 [1022/7469] ops amd8111_enable_dev: enabling PCI: 03:04.1 [1022/7469] PCI: 03:04.1 [1022/7469] enabled amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a] amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a] PCI: 03:04.2 [1022/746a] enabled amd8111_enable_dev: enabling PCI: 03:04.3 [1022/746b] PCI: 03:04.3 [1022/746b] ops amd8111_enable: enabling PCI: 03:04.3 [1022/746b] PCI: 03:04.3 [1022/746b] enabled amd8111_enable_dev: enabling PCI: 03:04.5 [1022/746d] PCI: 03:04.5 [1022/746d] ops amd8111_enable: enabling PCI: 03:04.5 [1022/746d] PCI: 03:04.5 [1022/746d] enabled amd8111_enable_dev: enabling PCI: 03:04.6 [1022/746e] PCI: 03:04.6 [1022/746e] ops amd8111_enable: disabling PCI: 03:04.6 [1022/746e] PCI: 03:04.6 [1022/746e] disabled PCI: pci_scan_bus for bus 4 PCI: 04:09.0 [14e4/16a7] enabled PCI: pci_scan_bus returning with max=04 PCI: pci_scan_bus for bus 5 PCI: pci_scan_bus returning with max=05 PCI: pci_scan_bus for bus 6 amd8111_enable_dev: enabling PCI: 06:00.0 [1022/7464] PCI: 06:00.0 [102 amd8111_enable: enabling PCI: 06:00.0 [1022/7464] PCI: 06:00.0 [1022/7464] enabled amd8111_enable_dev: enabling PCI: 06:00.1 [1022/7464] PCI: 06:00.1 [1022/7464] ops amd8111_enable: enabling PCI: 06:00.1 [1022/7464] PCI: 06:00.1 [1022/7464] enabled amd8111_enable_dev: enabling PCI: 06:00.2 [1022/7463] PCI: 06:00.2 [1022/7463] ops amd8111_enable: disabling PCI: 06:00.2 [1022/7463] PCI: 06:00.2 [1022/7463] disabled amd8111_enable_dev: enabling PCI: 06:01.0 [1022/7462] PCI: 06:01.0 [1022/7462] ops PCI: 06:01.0 [1022 PCI: 06:01.0 [1022/7462] disabled PCI: 06:0b.0 [1095/3114] enabled PCI: 06:0c.0 [104c/8023] ops PCI: 06:0c.0 [104c/8023] enabled PCI: pci_scan_bus returning with max=06 scan_static_bus for PCI: 03:04.0 PNP: 002e.0 enabled PNP: 002e.1 disabled PNP: 002e.2 enabled PNP: 002e.3 disabled PNP: 002e.5 enabled PNP: 002e.6 disabled PNP: 002e.7 disabled PNP: 002e.8 disabled PNP: 002e.9 disabled PNP: 002e.a disabled PNP: 002e.b enabled scan_static_bus done PCI: pci_scan_bus returning with max=06 Hyper transport scan link: 2 new Hypertransport scan link done amdk8_scan_chains max: 6 done amdk8_scan_chains max: 6 starting... This looked pretty good, but I didn't know what it was trying to start. Unfortunately the next time the same image executed (reset via power cycle) I got this: LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting... setting up resource map....done. No connection to Node 1. ht reset - LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting... setting up resource map....done. No connection to Node 1. Ram1.00 Ram1.01 Ram2.00 Ram2.01 No memory for this cpu Ram3 Initializing memory: done Initializing memory: ........................................................... ........................................................................ ........ ........................................................................ ........ ........................................................................ . failed Clearing LinuxBIOS memory: done Ram4 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 booting... Has anyone seen this issue? Is something not getting reset? BTW, my own image does the same thing. Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com

1 0

Dealing with Bus Master Enable
by Li-Ta Lo 12 May '04

12 May '04

YHLu, I have a new idea about the bus master enable and subsystem ids. We should do it with config tool. We can add new config keywords like busmaster and subsystem and use some generic code to enable the bit and program the subsystems ids. Thus we can remove a lot of codes in src/driver and mainboard/tyan. How do you think ? Ollie

1 0

答复: New problems with building Baremetal
by YhLu 11 May '04

11 May '04

You mean the frame_list[]....? YH -----邮件原件----- 发件人: YhLu 发送时间: 2004年5月11日 21:53 收件人: Takeshi Sone 抄送: Steven James; Linuxbios 主题: 答复: New problems with building Baremetal YES, I have modified that with phy_to_virt for mem range for OHCI. I can not debug UHCI, because I can not find such adapter. Amd 8111 is OHCI. Please let me know if you can debug the code. Regards YH -----邮件原件----- 发件人: Takeshi Sone [mailto:ts1@tsn.or.jp] 发送时间: 2004年5月11日 21:28 收件人: YhLu 抄送: Steven James; Linuxbios 主题: Re: New problems with building Baremetal YH, I have tried porting Steven's USB driver into FILO some months ago (without success, though). FILO is running on virtual address, but hardware that does DMA needs to know physical address, so some translation is needed when you pass some memory address to hardware registers. I believe this situation is same in Etherboot. (In fact, I stealed the idea of relocation/virtual addressing from Etherboot.) > Steven, > > I made some progress, and it met failed transaction. > > Regards > > YH > > [FILO]FILO version 0.4.1 (root@tst2723-rh9) Tue May 11 20:39:11 PDT 2004 > Press <Enter> for default boot, or <Esc> for boot prompt... timed out > boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf > LinuxLabs USB bootloader > raw frame_list is at 000795c0 > frame_list is at 0007a000 > frame_list_link: addr: 000785d0 > frame_list_link: raw addr: efef5f40 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070560 > raw frame_list is at 0007b5c0 > frame_list is at 0007c000 > frame_list_link: addr: 000785f0 > frame_list_link: raw addr: efef5f60 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 000705a0 > raw frame_list is at 0007d5c0 > frame_list is at 0007e000 > frame_list_link: addr: 00078610 > frame_list_link: raw addr: efef5f80 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 000705e0 > raw frame_list is at 0007f5c0 > frame_list is at 00080000 > frame_list_link: addr: 00078630 > frame_list_link: raw addr: efef5fa0 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070620 > Found OHCI at 0d1a2690 > Resetting OHCI > USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting > framelist > to: efef7970 > Starting OHCI > Found OHCI at 0d1a3690 > Resetting OHCI > USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting > framelist > to: efef9970 > Starting OHCI > poll_usb1 i=0 poll_o_root_hub1 v=00000100 poll_o_root_hub1 > v=00000100 > poll_o_root_hub1 v=00000100poll_usb1 i=1 poll_o_root_hub1 v=00000100 > poll_o_root_hub1 v=00010101 poll_o_root_hub2 > v=00010101poll_o_root_hub21 > v=00010101 Connection on port 0d1a36e8 > poll_o_root_hub211 v=00000101 poll_o_root_hub212 v=00000101 > poll_o_root_hub213 v=00000101 poll_o_root_hub214 v=00000101 New USB > device, setting address 00000003 > UHCI at 0d1a3690 > failed_transaction: TD(00070660): > failed_transaction: type: SETUP > failed_transaction: retries: 00000003 > failed_transaction: IOC > failed_transaction: active: 00000001 > failed_transaction: device_addr: 00000000 > failed_transaction: endpoint: 00000000 > failed_transaction: data_toggle: 00000000 > failed_transaction: max_transfer: 00000007 > failed_transaction: actual: 00000000 > failed_transaction: link: > failed_transaction: addr: 00070680 > failed_transaction: raw addr: efeedff0 > failed_transaction: terminate: 00000000 > failed_transaction: queue: 00000000 > failed_transaction: depth: 00000000 > failed_transaction: TD(00070680): > failed_transaction: type: IN > failed_transaction: retries: 00000000 > failed_transaction: active: 00000001 > failed_transaction: device_addr: 00000000 > failed_transaction: endpoint: 00000000 > failed_transaction: data_toggle: 00000001 > failed_transaction: max_transfer: 000007ff > failed_transaction: actual: 00000000 > failed_transaction: link: > failed_transaction:ddr: 10182690 > failed_transaction:aw addr: 00000000 > failed_transaction:erminate: 00000001 > failed_transaction:ueue: 00000000 > failed_transaction:epth: 00000000 > configure_device: set_address failed! > configure_device: can't set address! bailing! > > > > -- Takeshi _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

答复: New problems with building Baremetal
by YhLu 11 May '04

11 May '04

YES, I have modified that with phy_to_virt for mem range for OHCI. I can not debug UHCI, because I can not find such adapter. Amd 8111 is OHCI. Please let me know if you can debug the code. Regards YH -----邮件原件----- 发件人: Takeshi Sone [mailto:ts1@tsn.or.jp] 发送时间: 2004年5月11日 21:28 收件人: YhLu 抄送: Steven James; Linuxbios 主题: Re: New problems with building Baremetal YH, I have tried porting Steven's USB driver into FILO some months ago (without success, though). FILO is running on virtual address, but hardware that does DMA needs to know physical address, so some translation is needed when you pass some memory address to hardware registers. I believe this situation is same in Etherboot. (In fact, I stealed the idea of relocation/virtual addressing from Etherboot.) > Steven, > > I made some progress, and it met failed transaction. > > Regards > > YH > > [FILO]FILO version 0.4.1 (root@tst2723-rh9) Tue May 11 20:39:11 PDT 2004 > Press <Enter> for default boot, or <Esc> for boot prompt... timed out > boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf > LinuxLabs USB bootloader > raw frame_list is at 000795c0 > frame_list is at 0007a000 > frame_list_link: addr: 000785d0 > frame_list_link: raw addr: efef5f40 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070560 > raw frame_list is at 0007b5c0 > frame_list is at 0007c000 > frame_list_link: addr: 000785f0 > frame_list_link: raw addr: efef5f60 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 000705a0 > raw frame_list is at 0007d5c0 > frame_list is at 0007e000 > frame_list_link: addr: 00078610 > frame_list_link: raw addr: efef5f80 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 000705e0 > raw frame_list is at 0007f5c0 > frame_list is at 00080000 > frame_list_link: addr: 00078630 > frame_list_link: raw addr: efef5fa0 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070620 > Found OHCI at 0d1a2690 > Resetting OHCI > USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting > framelist > to: efef7970 > Starting OHCI > Found OHCI at 0d1a3690 > Resetting OHCI > USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting > framelist > to: efef9970 > Starting OHCI > poll_usb1 i=0 poll_o_root_hub1 v=00000100 poll_o_root_hub1 > v=00000100 > poll_o_root_hub1 v=00000100poll_usb1 i=1 poll_o_root_hub1 v=00000100 > poll_o_root_hub1 v=00010101 poll_o_root_hub2 > v=00010101poll_o_root_hub21 > v=00010101 Connection on port 0d1a36e8 > poll_o_root_hub211 v=00000101 poll_o_root_hub212 v=00000101 > poll_o_root_hub213 v=00000101 poll_o_root_hub214 v=00000101 New USB > device, setting address 00000003 > UHCI at 0d1a3690 > failed_transaction: TD(00070660): > failed_transaction: type: SETUP > failed_transaction: retries: 00000003 > failed_transaction: IOC > failed_transaction: active: 00000001 > failed_transaction: device_addr: 00000000 > failed_transaction: endpoint: 00000000 > failed_transaction: data_toggle: 00000000 > failed_transaction: max_transfer: 00000007 > failed_transaction: actual: 00000000 > failed_transaction: link: > failed_transaction: addr: 00070680 > failed_transaction: raw addr: efeedff0 > failed_transaction: terminate: 00000000 > failed_transaction: queue: 00000000 > failed_transaction: depth: 00000000 > failed_transaction: TD(00070680): > failed_transaction: type: IN > failed_transaction: retries: 00000000 > failed_transaction: active: 00000001 > failed_transaction: device_addr: 00000000 > failed_transaction: endpoint: 00000000 > failed_transaction: data_toggle: 00000001 > failed_transaction: max_transfer: 000007ff > failed_transaction: actual: 00000000 > failed_transaction: link: > failed_transaction:ddr: 10182690 > failed_transaction:aw addr: 00000000 > failed_transaction:erminate: 00000001 > failed_transaction:ueue: 00000000 > failed_transaction:epth: 00000000 > configure_device: set_address failed! > configure_device: can't set address! bailing! > > > > -- Takeshi

1 0

Re: New problems with building Baremetal
by YhLu 11 May '04

11 May '04

Steven, I made some progress, and it met failed transaction. Regards YH [FILO]FILO version 0.4.1 (root@tst2723-rh9) Tue May 11 20:39:11 PDT 2004 Press <Enter> for default boot, or <Esc> for boot prompt... timed out boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf LinuxLabs USB bootloader raw frame_list is at 000795c0 frame_list is at 0007a000 frame_list_link: addr: 000785d0 frame_list_link: raw addr: efef5f40 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000001 frame_list_link: depth: 00000000 dummy_td = 00070560 raw frame_list is at 0007b5c0 frame_list is at 0007c000 frame_list_link: addr: 000785f0 frame_list_link: raw addr: efef5f60 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000001 frame_list_link: depth: 00000000 dummy_td = 000705a0 raw frame_list is at 0007d5c0 frame_list is at 0007e000 frame_list_link: addr: 00078610 frame_list_link: raw addr: efef5f80 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000001 frame_list_link: depth: 00000000 dummy_td = 000705e0 raw frame_list is at 0007f5c0 frame_list is at 00080000 frame_list_link: addr: 00078630 frame_list_link: raw addr: efef5fa0 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000001 frame_list_link: depth: 00000000 dummy_td = 00070620 Found OHCI at 0d1a2690 Resetting OHCI USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting framelist to: efef7970 Starting OHCI Found OHCI at 0d1a3690 Resetting OHCI USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting framelist to: efef9970 Starting OHCI poll_usb1 i=0 poll_o_root_hub1 v=00000100 poll_o_root_hub1 v=00000100 poll_o_root_hub1 v=00000100poll_usb1 i=1 poll_o_root_hub1 v=00000100 poll_o_root_hub1 v=00010101 poll_o_root_hub2 v=00010101poll_o_root_hub21 v=00010101 Connection on port 0d1a36e8 poll_o_root_hub211 v=00000101 poll_o_root_hub212 v=00000101 poll_o_root_hub213 v=00000101 poll_o_root_hub214 v=00000101 New USB device, setting address 00000003 UHCI at 0d1a3690 failed_transaction: TD(00070660): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: 00070680 failed_transaction: raw addr: efeedff0 failed_transaction: terminate: 00000000 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 failed_transaction: TD(00070680): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction:ddr: 10182690 failed_transaction:aw addr: 00000000 failed_transaction:erminate: 00000001 failed_transaction:ueue: 00000000 failed_transaction:epth: 00000000 configure_device: set_address failed! configure_device: can't set address! bailing!

2 1

Is pc80/vgabios.c still used in LB2 ?
by Li-Ta Lo 11 May '04

11 May '04

Hello, I am trying to build rom iamge for EPIA and finding a good way to do vga in LinuxBIOS. I found that the pc80/vgabios.c is not used for EPIA and the southbridge_via_vt8231_control is redefinde in southbridge/via/vt8231/vt8231.c and used. There is nothing about vga in that file. How does EPIA enable its VGA chip ? Ollie

2 1

← Newer
1
...
7
8
9
10
11
12
13
14
15
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 May 2004