coreboot

coreboot@coreboot.org

12 participants
39779 discussions

Re: tyan s2880 build broken?
by YhLu 26 Apr '04

26 Apr '04

So I need disable the code always, and don't send the image to the end user. What's pity! YH. -----邮件原件----- 发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] 发送时间: 2004年4月26日 11:12 收件人: YhLu 抄送: linuxbios(a)clustermatic.org 主题: Re: tyan s2880 build broken? YhLu <YhLu(a)tyan.com> writes: > I will change the code to disable the lsi_scsi as the default. > > Do you have lsi 1030 onboard? You need to use it? > > If you need to use it, I send you pre-built image, because I can not publish > the source code of lsi_scsi. LSI don’t want to. If you can't publish the source then distributing the binary with the code compiled from that source linked in violates the GPL. Eric

2 1

amd opteron dram controller
by HC Wang 26 Apr '04

26 Apr '04

Hi, I am working on post code for an embedded opteron board, I have some problem with dram controller initialization, problem I have seen are (1) after setting DramInit bit (bit 8) in dram configuration low register (bus 0, dev 24, func 2, reg 0x90), processor clear this bit after a while but DramEnable (bit 10) and MemClrStatus (bit 11) never set high, is this a problem? If so what is causing it? (2) After DramInit bit is cleared by processor, I can access sdram from 0x00000000 to 0x0009ffff, fill it with pattern and verify it. But I can't write into address space from 0x000A0000 - 0x000EFFFF, even MTRRs associated with it are set to UC type. Is this correct? (3) Can't write memory above 1M (from 0x00100000 and up), but I can alter the memory content by using AMD HDT.. Any ideas? Thanks, HC

3 3

Re: tyan s2880 build broken?
by YhLu 26 Apr '04

26 Apr '04

I will change the code to disable the lsi_scsi as the default. Do you have lsi 1030 onboard? You need to use it? If you need to use it, I send you pre-built image, because I can not publish the source code of lsi_scsi. LSI don’t want to. Regards YH _____ 发件人: HC Wang [mailto:hcwang@netd.com] 发送时间: 2004年4月26日 10:15 收件人: linuxbios(a)clustermatic.org 主题: tyan s2880 build broken? Hi, I checked out linuxbios2 tree from sourceforge.net, and I have problem with building bios for tyan s2880 motherboard, here is the error message from buildtarget tyan/s2880: Configuring PART mainboard, path tyan/s2880 ===> NOTE: Changing default value of LB_CKS_RANGE_START ===> NOTE: Changing default value of LB_CKS_RANGE_END ===> NOTE: Changing default value of LB_CKS_LOC Configuring DIR ../common/lsi_scsi/Config.lb ===> ERROR: Could not open file "/home/hcwang/linux-bios/freebios2/src/mainboard/tyan/s2880/../common/lsi_sc si/Config.lb" tyan/s2880/Config.lb:0 mainboard/tyan/s2880/Config.lb:0 ../common/lsi_scsi/Config.lb:0 [hcwang@primary targets]$ pwd /home/hcwang/linux-bios/freebios2/targets Has anybody experience similar problem? Thanks, HC

3 4

答复: 答复: 答复: tyan s2880 build broken?
by YhLu 26 Apr '04

26 Apr '04

When I using the new config to deal with it, the tool seems doesn’t support expression. I will check that in current config tool. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月26日 10:57 收件人: YhLu 抄送: HC Wang; linuxbios(a)clustermatic.org 主题: Re: 答复: 答复: tyan s2880 build broken? On Mon, 26 Apr 2004, YhLu wrote: > When enabling lsi_scsi support, It need leave 48k in the BIOS ROM for > lsi_scsi fw. So need to change normal mode ROM_SIZE to 512k-48k. OK, BTW you can do this: option ROM_SIZE = 512*1024 - 48*1024 which is not as readable as 512k-48k, but is pretty readable. ron

2 1

答复: 答复: tyan s2880 build broken?
by YhLu 26 Apr '04

26 Apr '04

When enabling lsi_scsi support, It need leave 48k in the BIOS ROM for lsi_scsi fw. So need to change normal mode ROM_SIZE to 512k-48k. After that, cat fwx, normal linuxbios, fallback linuxbios to 512k final image. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月26日 10:49 收件人: YhLu 抄送: HC Wang; linuxbios(a)clustermatic.org 主题: Re: 答复: tyan s2880 build broken? On Mon, 26 Apr 2004, YhLu wrote: > Don't forget 2. otherwise the final image will short some. What should it be? ron

2 1

答复: tyan s2880 build broken?
by YhLu 26 Apr '04

26 Apr '04

1. In freebios2/src/mainboard/tyan/s2880/Config.lb comment out dir ../common/lsi_scsi 2. In freebios2/targets/tyan/s2880/Config.lb comment out option ROM_SIZE = 475136 Don't forget 2. otherwise the final image will short some. Regards YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月26日 10:42 收件人: YhLu 抄送: HC Wang; linuxbios(a)clustermatic.org 主题: Re: tyan s2880 build broken? I just commented out the #dir ../ entry in mainboard/tyan/s2880/Config.lb and the buildtarget seems ok. I will commit. ron

2 1

tyan s2880 build broken?
by HC Wang 26 Apr '04

26 Apr '04

Hi, I checked out linuxbios2 tree from sourceforge.net, and I have problem with building bios for tyan s2880 motherboard, here is the error message from buildtarget tyan/s2880: Configuring PART mainboard, path tyan/s2880 ===> NOTE: Changing default value of LB_CKS_RANGE_START ===> NOTE: Changing default value of LB_CKS_RANGE_END ===> NOTE: Changing default value of LB_CKS_LOC Configuring DIR ../common/lsi_scsi/Config.lb ===> ERROR: Could not open file "/home/hcwang/linux-bios/freebios2/src/mainboard/tyan/s2880/../common/lsi_sc si/Config.lb" tyan/s2880/Config.lb:0 mainboard/tyan/s2880/Config.lb:0 ../common/lsi_scsi/Config.lb:0 [hcwang@primary targets]$ pwd /home/hcwang/linux-bios/freebios2/targets Has anybody experience similar problem? Thanks, HC

2 1

答复: 答复: ATI rage xl.init
by YhLu 26 Apr '04

26 Apr '04

3, 4, 5 already in the CVS tree. YH -----邮件原件----- 发件人: Hendricks David W. [mailto:dwh@lanl.gov] 发送时间: 2004年4月23日 14:52 收件人: YhLu 抄送: Li-Ta Lo; ron minnich; Stefan Reinauer; LinuxBIOS 主题: Re: ´ð¸´: ATI rage xl.init The only thing that didn't patch cleanly on my setup was a config file for a Tyan board. Was there anything else that didn't apply cleanly to a CVS tree, Ollie? It might be nice to get that ATi and btext stuff in there quickly since there are likely others who are very, very interested in this patch. Though I know Ron wanted to review the superIO and PNP changes a little more after finishing his paperwork :-/ On Fri, 23 Apr 2004, YhLu wrote: > So I need to produce another patch except 3, 4 & 5? > > -----ÓÊ¼þÔ¼þ----- > ·¢¼þÈË: Li-Ta Lo [mailto:ollie@lanl.gov] > ·¢ËÍÊ±¼ä: 2004Äê4ÔÂ23ÈÕ 11:00 > ÊÕ¼þÈË: YhLu > ³ËÍ: ron minnich; Stefan Reinauer; LinuxBIOS > Ö÷Ìâ: Re: ATI rage xl.init > > On Fri, 2004-04-23 at 11:56, YhLu wrote: > > You only commit 4 & 5 ? > > > > I haven't commit anything yet. I am busy working on > the ibm/e325 HT enumeration problem. I will look at > the patch next week. > > Ollie > > > -----ÓÊ¼þÔ¼þ----- > > ·¢¼þÈË: Li-Ta Lo [mailto:ollie@lanl.gov] > > ·¢ËÍÊ±¼ä: 2004Äê4ÔÂ21ÈÕ 14:47 > > ÊÕ¼þÈË: YhLu > > ³ËÍ: ron minnich; Stefan Reinauer; LinuxBIOS > > Ö÷Ìâ: Re: ATI rage xl.init > > > > On Tue, 2004-04-20 at 19:38, YhLu wrote: > > > Ron, > > > > > > Please commit ati rage xl support. > > > > > > 1. ati rage xl support > > > 2. add btext_console to use rage xl fb. > > > 3. enable pnp init calling > > > 4. superio Winbond: real enable/disable device. > > > 5. superio Winbond: enable HW > > > 6. Tyan S2850 support update > > > 7. Tyan S2875 support added. > > > 8. Move some PCI master enable driver to /driver dir. > > > > > > Stefan, > > > > > > Please test the filo too, I add the btext_console into it. > > > On vocation? Why using stepan(a)openbios.org ? > > > > > > > > > > > > there are some conflicts between your tree and the current > > CVS. Could you do cvs update and send me the patch again ? > > > > Ollie > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

5 7

Openbios 1.0.RC1 build problems
by Mathieu Deschamps 26 Apr '04

26 Apr '04

Well I've tryied to make dev/bios with the old makefile and it works perfectly and i know why. The version i got unstable200404xx handle 2.6kernel policy change on modules or something like that But I still don't understand these part of your code: ifeq ($(KERNEL)/.config,$(wildcard $(KERNEL)/.config)) include $(KERNEL)/.config endif # see if we need module versions ifdef CONFIG_MODVERSIONS CFLAGS += -DMODVERSIONS endif In the 0.3.2 version in never hear about the need to include the kernel .config. When i say to managed to make it works that true, but it's tainted and this is an ugly "bricologe" Please I really need somebody to get me out of this . mathieu Le ven 23/04/2004 à 15:29, Mathieu Deschamps a écrit : > ok , I try a recent unstable version via openbios/snapshot/ > and just typed make without changing anything, it's seems > a .config file has not been built or a file misses in the > tar into forth directory. > > It's a new source tree organisation :) with a beautifull ncurse > config menu. > > ======================= > checking whether ln -s works... yes > checking for gcc... /usr/bin/gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether /usr/bin/gcc accepts -g... yes > checking for /usr/bin/gcc option to accept ANSI C... none needed > checking how to run the C preprocessor... /usr/bin/gcc -E > checking for bison... bison -y > checking for flex... flex > checking for yywrap in -lfl... yes > checking lex output file root... lex.yy > checking whether yytext is a pointer... yes > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whetherbut I can't find my herd back ! Please... g++ accepts > -g... yes > checking for m4... m4 > checking for as... as > checking for strip... strip > checking for ld... ld > checking for nm... nm > checking for install... install > checking dependency style... new > configure: creating ./config.status > config.status: creating Makefile.defs > config.status: creating mconfig.h > + Entering lxdialog > Compiling checklist.o : ok > Compiling menubox.o : ok > Compiling textbox.o : ok > Compiling yesno.o : ok > Compiling inputbox.o : ok > Compiling util.o : ok > Compiling lxdialog.o : ok > Compiling msgbox.o : ok > = Building lxdialog : ok > + Entering kconfig > Compiling zconf-y.o : ok > Compiling mconf.o : ok > = Building mconfig : ok > Compiling conf.o : ok > = Building config : ok > > > # End of OpenBIOS configuration. > # The next step is probably 'make'. > > config.status: creating Makefile.defs > config.status: creating mconfig.h > config.status: mconfig.h is unchanged > = Building openbios-1.0.RC1 [avr 23 2004 15:03] > + Entering libc > Compiling ctype.o : ok > Compiling extra.o : ok > Compiling misc.o : ok > Compiling string.o : ok > Compiling vsprintf.o : ok > Compiling diskio.o : ok > Compiling byteorder.o : ok > + Entering kernel > Compiling dict.o : ok > Compiling primitives.o : okmake -f Makefile.24 > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 bios_core.c -o bios_core.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 flashchips.c -o flashchips.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 pcisets.c -o pcisets.o > pcisets.c:234: warning: `gporeg_save' defined but not used > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 filesystem.c -o filesystem.o > filesystem.c:292: `THIS_MODULE' undeclared here (not in a function) > filesystem.c:292: initializer element is not constant > filesystem.c:292: (near initialization for `bios_fops.owner') > make: *** [filesystem.o] Error 1 > > Compiling stack.o : ok > Compiling bootstrap.o : ok > = Building forthc : ok > + Entering toke > Compiling toke.o : ok > Compiling emit.o : ok > Compiling dictionary.o : ok > Compiling stack.o : ok > Compiling stream.o : ok > Compiling macros.o : ok > Compiling scanner.o : ok > = Building toke : ok > + Entering forth > make[2]: *** No rule to make target `../.config', needed by > `../obj-x86/build/forth/lib.dict'. Stop. > make[1]: *** [sub-forth-all] Error 2 > make: *** [auto-bootstrap] Error 2 > > -------------------------------- > If i try to make devbios in devbios i have a > --------------------------------- > [unstable/dev/bios]make > > make -C /usr/src/linux SUBDIRS=`pwd` modules > make[1]: Entering directory `/usr/src/linux-2.4.20' > make -C /home/root/projet/src/unstable/utils/devbios > CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i486 > -malign-functions=0 -malign-jumps=0 -malign-loops=0 -DMODULE > -DMODVERSIONS -include > /usr/src/linux-2.4.20/include/linux/modversions.h" MAKING_MODULES=1 > modules > make[2]: Entering directory > `/home/root/projet-20042004/src/unstable/utils/devbios' > make[2]: *** No rule to make target `modules'. Stop. > make[2]: Leaving directory > `/home/root/projet-20042004/src/unstable/utils/devbios' > make[1]: *** [_mod_/home/root/projet/src/unstable/utils/devbios] Error 2 > make[1]: Leaving directory `/usr/src/linux-2.4.20' > make: *** [module] Error 2 > > I also try :wq > > > make -f Makefile.24 > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 bios_core.c -o bios_core.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 flashchips.c -o flashchips.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 pcisets.c -o pcisets.o > pcisets.c:234: warning: `gporeg_save' defined but not used > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 filesystem.c -o filesystem.o > filesystem.c:292: `THIS_MODULE' undeclared here (not in a function) > filesystem.c:292: initializer element is not constant > filesystem.c:292: (near initialization for `bios_fops.owner') > make: *** [filesystem.o] Error 1 > > > What's wrong ? I have lost myself in this new dist. > > mathieu

2 2

Still wandering how to parameter dev/bios
by Mathieu Deschamps 26 Apr '04

26 Apr '04

hello, I still trying to parameter dev/bios to get it open another bios, but I just don't know. By default, insmod bios.o opens main bios into /dev/bios. As written in the README.bios, it is possible to open other devices since it says something on mknod /dev/gfxbios c 104 1 and also mknod /dev/hddbios c 104 2. Making nodes is possible by simply insmoding bios driver don't open every bios. If anyone already get it work onto other bios, please mail me your way so I can study it. Other idea also welcome. mathieu

2 1

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