coreboot

coreboot@coreboot.org

12 participants
39779 discussions

答复: 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

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

11 May '04

when prompt boot: input uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf YH -----邮件原件----- 发件人: YhLu 发送时间: 2004年5月11日 10:37 收件人: Steven James 抄送: Gregg C Levine; Linuxbios 主题: 答复: 答复: New problems with building Baremetal Steven, I just sent you the tar ball include OHCI support, Please let know if you got it. It can not reset the OHCI yet. Regards YH -----邮件原件----- 发件人: YhLu 发送时间: 2004年5月10日 16:11 收件人: Steven James 抄送: Gregg C Levine; Linuxbios 主题: 答复: 答复: New problems with building Baremetal Good, I will pack the code into tar and send to you. Regards YH -----邮件原件----- 发件人: Steven James [mailto:pyro@linuxlabs.com] 发送时间: 2004年5月10日 15:57 收件人: YhLu 抄送: Gregg C Levine; Linuxbios 主题: Re: 答复: New problems with building Baremetal Greetings, Actually, it is my own implementation, though I did use the 2.4.x kernel's uhci.c as a guide. I couldn't use that as is since it had a good many kernel dependencies and was interrupt driven. I did have it loading as a module at one point to test things. If you want, I can get a machine here set up and test/debug your merge. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office & fax 866.545.6306 ----------------------------------------------------------------------- On Mon, 10 May 2004, YhLu wrote: > Steven, > > The uhci.c is from 2.4.22 or 2.6.5? > > I merged your code into FILO in Etherboot, but at last I found that the USB > in AMD8111 is ohci. And I can not debug uhci now. > > Regards > > YH > > -----邮件原件----- > 发件人: Steven James [mailto:pyro@linuxlabs.com] > 发送时间: 2004年5月10日 12:55 > 收件人: Gregg C Levine > 抄送: Linuxbios > 主题: Re: New problems with building Baremetal > > Greetings, > > In the lib directory, try removing ide.o from DEPS for now. That should > get the library to compile. > > The rest is all warnings except at the end where it can't link against > libbaremetal.a > > G'day, > sjames > > > -------------------------steven james, director of research, linux labs > ... ........ ..... .... 230 peachtree st nw ste 2701 > the original linux labs atlanta.ga.us 30303 > -since 1995 http://www.linuxlabs.com > office & fax 866.545.6306 > ----------------------------------------------------------------------- > > > On Mon, 10 May 2004, Gregg C Levine wrote: > > > Hello from Gregg C Levine > > Now something else has happened. I've managed to build a copy of GCC > > version 2.9.5.3 and have it installed in the /opt directory. But > > there are unusual problems in the building of the bare metal library, > > here's a script output regarding the errors: > > Script started on Mon May 10 14:47:28 2004 > > root@who5:/usr/src/lobos/freebios/util/baremetal/lib# make > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/printk.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > serial_subr.o serial_subr.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > subr.o subr.c > > In file included from subr.c:16: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/vsprintf.c > > In file included from ../../../src/lib/vsprintf.c:18: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/memcpy.c > > In file included from ../../../src/lib/memcpy.c:1: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/malloc.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/memset.c > > In file included from ../../../src/lib/memset.c:1: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/compute_ip_checksum.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > elfboot.o elfboot.c > > In file included from elfboot.c:8: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > boot.o boot.c > > In file included from boot.c:4: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/pc80/ide/ide.c > > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory > > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory > > make: *** [ide.o] Error 1 > > root@who5:/usr/src/lobos/freebios/util/baremetal/lib# exit > > Script done on Mon May 10 14:47:36 2004 > > > > Obviously some of those errors can be corrected by reminding the make > > file to find the include files that GCC 2.95.3 prefers. But the ones > > that concern me, are the "missing files" for the IDE issues. > > > > And here's the latest problem with the USB attachment to bare metal: > > Script started on Mon May 10 14:49:02 2004 > > root@who5:/usr/src/lobos/freebios/util/baremetal/usb# make > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o uhci.o uhci.c > > uhci.c:332: warning: `USBCMD' redefined > > uhci.h:290: warning: this is the location of the previous definition > > uhci.c:333: warning: `USBSTS' redefined > > uhci.h:291: warning: this is the location of the previous definition > > uhci.c:334: warning: `USBINTR' redefined > > uhci.h:292: warning: this is the location of the previous definition > > uhci.c:335: warning: `FRNUM' redefined > > uhci.h:293: warning: this is the location of the previous definition > > uhci.c:336: warning: `FLBASE' redefined > > uhci.h:294: warning: this is the location of the previous definition > > uhci.c:337: warning: `SOFMOD' redefined > > uhci.h:295: warning: this is the location of the previous definition > > uhci.c:338: warning: `PORTSC1' redefined > > uhci.h:296: warning: this is the location of the previous definition > > uhci.c:339: warning: `PORTSC2' redefined > > uhci.h:297: warning: this is the location of the previous definition > > uhci.c: In function `ctrl_msg': > > uhci.c:776: warning: assignment makes pointer from integer without a > > cast > > uhci.c: In function `hub_port_reset': > > uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible > > pointer type > > uhci.c: In function `usb_hub_init': > > uhci.c:1272: warning: assignment makes pointer from integer without a > > cast > > uhci.c: In function `configure_device': > > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from > > incompatible pointer type > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o usb_scsi_low.o usb_scsi_low.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o debug.o debug.c > > In file included from debug.c:31: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o scsi_cmds.o scsi_cmds.c > > In file included from scsi_cmds.c:26: > > /usr/include/sys/types.h:152: warning: redefinition of `ushort' > > uhci.h:13: warning: `ushort' previously declared here > > scsi_cmds.c: In function `ll_read_block': > > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ll_write_block': > > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ll_read_long': > > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `get_capacity': > > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `query': > > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ReportLUNS': > > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ReportOpCodes': > > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `CheckVolumes': > > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `CheckPartitions': > > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `UnitReady': > > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o pci_util.o pci_util.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o block_fill_inbuf.o > > block_fill_inbuf.c > > In file included from block_fill_inbuf.c:8: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > make: *** No rule to make target `../lib/baremetal.a', needed by > > `usbboot.elf'. Stop. > > root@who5:/usr/src/lobos/freebios/util/baremetal/usb# exit > > Script done on Mon May 10 14:49:10 2004 > > > > Again I expect that by instructing the make file to use the include > > files supplied by GCC 2.95.3, that most of the errors will be gone, > > but I'm listing those for reference. > > ------------------- > > Gregg C Levine hansolofalcon(a)worldnet.att.net > > ------------------------------------------------------------ > > "The Force will be with you...Always." Obi-Wan Kenobi > > "Use the Force, Luke." Obi-Wan Kenobi > > > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios(a)clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ 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

Steven, I just sent you the tar ball include OHCI support, Please let know if you got it. It can not reset the OHCI yet. Regards YH -----邮件原件----- 发件人: YhLu 发送时间: 2004年5月10日 16:11 收件人: Steven James 抄送: Gregg C Levine; Linuxbios 主题: 答复: 答复: New problems with building Baremetal Good, I will pack the code into tar and send to you. Regards YH -----邮件原件----- 发件人: Steven James [mailto:pyro@linuxlabs.com] 发送时间: 2004年5月10日 15:57 收件人: YhLu 抄送: Gregg C Levine; Linuxbios 主题: Re: 答复: New problems with building Baremetal Greetings, Actually, it is my own implementation, though I did use the 2.4.x kernel's uhci.c as a guide. I couldn't use that as is since it had a good many kernel dependencies and was interrupt driven. I did have it loading as a module at one point to test things. If you want, I can get a machine here set up and test/debug your merge. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office & fax 866.545.6306 ----------------------------------------------------------------------- On Mon, 10 May 2004, YhLu wrote: > Steven, > > The uhci.c is from 2.4.22 or 2.6.5? > > I merged your code into FILO in Etherboot, but at last I found that the USB > in AMD8111 is ohci. And I can not debug uhci now. > > Regards > > YH > > -----邮件原件----- > 发件人: Steven James [mailto:pyro@linuxlabs.com] > 发送时间: 2004年5月10日 12:55 > 收件人: Gregg C Levine > 抄送: Linuxbios > 主题: Re: New problems with building Baremetal > > Greetings, > > In the lib directory, try removing ide.o from DEPS for now. That should > get the library to compile. > > The rest is all warnings except at the end where it can't link against > libbaremetal.a > > G'day, > sjames > > > -------------------------steven james, director of research, linux labs > ... ........ ..... .... 230 peachtree st nw ste 2701 > the original linux labs atlanta.ga.us 30303 > -since 1995 http://www.linuxlabs.com > office & fax 866.545.6306 > ----------------------------------------------------------------------- > > > On Mon, 10 May 2004, Gregg C Levine wrote: > > > Hello from Gregg C Levine > > Now something else has happened. I've managed to build a copy of GCC > > version 2.9.5.3 and have it installed in the /opt directory. But > > there are unusual problems in the building of the bare metal library, > > here's a script output regarding the errors: > > Script started on Mon May 10 14:47:28 2004 > > root@who5:/usr/src/lobos/freebios/util/baremetal/lib# make > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/printk.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > serial_subr.o serial_subr.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > subr.o subr.c > > In file included from subr.c:16: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/vsprintf.c > > In file included from ../../../src/lib/vsprintf.c:18: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/memcpy.c > > In file included from ../../../src/lib/memcpy.c:1: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/malloc.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/memset.c > > In file included from ../../../src/lib/memset.c:1: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/lib/compute_ip_checksum.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > elfboot.o elfboot.c > > In file included from elfboot.c:8: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c -o > > boot.o boot.c > > In file included from boot.c:4: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -c > > ../../../src/pc80/ide/ide.c > > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory > > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory > > make: *** [ide.o] Error 1 > > root@who5:/usr/src/lobos/freebios/util/baremetal/lib# exit > > Script done on Mon May 10 14:47:36 2004 > > > > Obviously some of those errors can be corrected by reminding the make > > file to find the include files that GCC 2.95.3 prefers. But the ones > > that concern me, are the "missing files" for the IDE issues. > > > > And here's the latest problem with the USB attachment to bare metal: > > Script started on Mon May 10 14:49:02 2004 > > root@who5:/usr/src/lobos/freebios/util/baremetal/usb# make > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o uhci.o uhci.c > > uhci.c:332: warning: `USBCMD' redefined > > uhci.h:290: warning: this is the location of the previous definition > > uhci.c:333: warning: `USBSTS' redefined > > uhci.h:291: warning: this is the location of the previous definition > > uhci.c:334: warning: `USBINTR' redefined > > uhci.h:292: warning: this is the location of the previous definition > > uhci.c:335: warning: `FRNUM' redefined > > uhci.h:293: warning: this is the location of the previous definition > > uhci.c:336: warning: `FLBASE' redefined > > uhci.h:294: warning: this is the location of the previous definition > > uhci.c:337: warning: `SOFMOD' redefined > > uhci.h:295: warning: this is the location of the previous definition > > uhci.c:338: warning: `PORTSC1' redefined > > uhci.h:296: warning: this is the location of the previous definition > > uhci.c:339: warning: `PORTSC2' redefined > > uhci.h:297: warning: this is the location of the previous definition > > uhci.c: In function `ctrl_msg': > > uhci.c:776: warning: assignment makes pointer from integer without a > > cast > > uhci.c: In function `hub_port_reset': > > uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible > > pointer type > > uhci.c: In function `usb_hub_init': > > uhci.c:1272: warning: assignment makes pointer from integer without a > > cast > > uhci.c: In function `configure_device': > > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from > > incompatible pointer type > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o usb_scsi_low.o usb_scsi_low.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o debug.o debug.c > > In file included from debug.c:31: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o scsi_cmds.o scsi_cmds.c > > In file included from scsi_cmds.c:26: > > /usr/include/sys/types.h:152: warning: redefinition of `ushort' > > uhci.h:13: warning: `ushort' previously declared here > > scsi_cmds.c: In function `ll_read_block': > > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ll_write_block': > > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ll_read_long': > > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `get_capacity': > > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `query': > > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ReportLUNS': > > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `ReportOpCodes': > > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `CheckVolumes': > > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `CheckPartitions': > > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > scsi_cmds.c: In function `UnitReady': > > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from > > incompatible pointer type > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o pci_util.o pci_util.c > > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG > > -DZKERNEL_START=0xfff00000 -c -o block_fill_inbuf.o > > block_fill_inbuf.c > > In file included from block_fill_inbuf.c:8: > > ../include/string.h:9: warning: conflicting types for built-in > > function `strcpy' > > make: *** No rule to make target `../lib/baremetal.a', needed by > > `usbboot.elf'. Stop. > > root@who5:/usr/src/lobos/freebios/util/baremetal/usb# exit > > Script done on Mon May 10 14:49:10 2004 > > > > Again I expect that by instructing the make file to use the include > > files supplied by GCC 2.95.3, that most of the errors will be gone, > > but I'm listing those for reference. > > ------------------- > > Gregg C Levine hansolofalcon(a)worldnet.att.net > > ------------------------------------------------------------ > > "The Force will be with you...Always." Obi-Wan Kenobi > > "Use the Force, Luke." Obi-Wan Kenobi > > > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios(a)clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

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