coreboot

coreboot@coreboot.org

12 participants
39779 discussions

答复: Using DATA I/O to burn flash
by YhLu 11 May '04

11 May '04

I tried to send you one prebuilt image, but I can not reach you. -----邮件原件----- 发件人: Jay Miller [mailto:jmiller@actuality-systems.com] 发送时间: 2004年5月11日 4:56 收件人: linuxbios(a)clustermatic.org 主题: Using DATA I/O to burn flash We've got a Data I/O machine and I would like to use it to burn my linuxbios.rom image to flash. What format is this image? If I'm not mistaken it's ELF, but the DATA I/O doesn't have a listing for ELF files. Has anyone used this type of burner to flash their BIOS chips? 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: Using DATA I/O to burn flash
by ron minnich 11 May '04

11 May '04

On Tue, 11 May 2004, Jay Miller wrote: > What format is this image? it's a raw set of bytes. It's an image. > Has anyone used this type of burner to flash their BIOS chips? yes, it works fine. I used to do it all the time. ron

1 0

Re: Using DATA I/O to burn flash
by Stefan Reinauer 11 May '04

11 May '04

* Jay Miller <jmiller(a)actuality-systems.com> [040511 13:55]: > We've got a Data I/O machine and I would like to use it to burn my > linuxbios.rom image to flash. > > What format is this image? If I'm not mistaken it's ELF, but the DATA > I/O doesn't have a listing for ELF files. Has anyone used this type of > burner to flash their BIOS chips? Only the payload is ELF. That is the code that is executed after hardware setup is done. This allows easy development of applications on top of LinuxBIOS. The LinuxBIOS image itself is just a raw 1:1 image of what needs to be burned to the flash chip. No headers, no bells, no whistles. Stefan

3 2

Using DATA I/O to burn flash
by Jay Miller 11 May '04

11 May '04

We've got a Data I/O machine and I would like to use it to burn my linuxbios.rom image to flash. What format is this image? If I'm not mistaken it's ELF, but the DATA I/O doesn't have a listing for ELF files. Has anyone used this type of burner to flash their BIOS chips? Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com

1 0

Com. script for /dev/ttyS0
by Mathieu Deschamps 11 May '04

11 May '04

Hello, As i've seen there are no tool to handle ttyS0 communication, I've done some tiny scripts to handle this in bash so it relies on linux. It logs and calculate the elapse time of hearing, that could be interrupt. That's very minimal, I find it useful and the command line of hear isn't that simple. To use them, you just have to check out your com driver with your actual LB Baud rate : [root@ge] cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:9600 tx:967431 rx:955468 fe:2155 brk:2 1: uart:16550A port:2F8 irq:3 baud:9600 tx:3 rx:0 Then copy these file hear.sh and digest.sh (note:render 'em executable) ------------------------------------------------------------------- #!/bin/sh # # Hear! script listen & log from ttyS0 (serial port a.k.a COM1) # Mathieu Deschamps for mangove-systems # VERSION="07/05/04|16:24:03 MD" i="Bienvenu(e) dans Hear! v. $VERSION j'ecoute sur ttyS0 ..." ter=`tty` if [ "x$1" = "x" ]; then echo "Usage $0 log_to_file" exit 0 else LOG="$1" fi echo $i echo "Logging in $LOG" echo "****************************************************" >>"$LOG" echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> "$LOG" echo " tty in use : $ter from ttyS0 " >>"$LOG" echo "****************************************************" >>"$LOG" /usr/bin/time -pao "$LOG" -- cat -sbA </dev/ttyS0 | tee -a "$LOG" ./digest.sh $LOG -s ------------------------------------------------------------------------- #!/bin/bash # # Script to digest hard-human readable hear! logs # Mathieu Deschamps for mangrove-systems # VERSION="11/05/04|09:40:28 MD" SUPP=0 DAT="`date +%d\-%m\-%y\ %T`" if [ "x$1" = "x" ]; then echo "usage: $0 hear!_log_file [--suppress-log,-s] " echo "v. $VERSION" exit 0 else FIL="$1" fi [ "x$2" = "x-s" ] || [ "x$2" = "x--suppress-log" ] && SUPP=1 if [ -f "$FIL.adv" ]; then mv "$FIL.adv" "$FIL.adv.$DAT" fi cat $FIL | while read line; do [ "x$line" != "x$" ] && echo "$line" done > "$FIL.adv" ( [ $? -eq 0 ]; echo "$FIL digested into $FIL.adv" ) || echo "Digestion gets harden ...blurp (error) " [ $SUPP -eq 1 ] && rm -f $FIL 2>&1 >/dev/null ------------------------------------------------------------------------ Of course, first, you should test hear.sh in typing : echo "test" >/dev/ttyS0 on you build station and see what you'll get, to end and close dialog you can send a /dev/null or CTRL Interrup the listener. It has helped me keeping trails, so if could for you. mathieu

1 0

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

10 May '04

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 >

1 0

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

10 May '04

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

2 1

New problems with building Baremetal
by Gregg C Levine 10 May '04

10 May '04

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

2 2

RE: TS-5300 Support
by ron minnich 10 May '04

10 May '04

On Mon, 10 May 2004, Jacob Alifrangis (LISTS) wrote: > The uboot project has amd elan support already. yep. We can use some of that code too. ron

1 0

TS-5300 Support
by Jacob Alifrangis (LISTS) 10 May '04

10 May '04

Is there any support in the tree for a Technologic Systems TS-5x00 board. We are developing an embedded project and would like to use linuxbios to start the boards up. If anybody wants to develop for the board, and can promise us a timeline, we will ship you a unit asap. The boards are available at http://www.embeddedx86.com/

4 5

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