coreboot September 2003

coreboot@coreboot.org

68 participants
171 discussions

Re: why are we still doing this?
by YhLu 25 Sep '03

25 Sep '03

Then where can the config tool got that info to produce >MAINBOARD_PART_NUMBER="hdama" >MAINBOARD_VENDOR="arima" YH -----邮件原件----- 发件人: Greg Watson [mailto:gwatson@lanl.gov] 发送时间: 2003年9月25日 16:53 收件人: ron minnich; linuxbios(a)clustermatic.org 主题: Re: why are we still doing this? No need, since it's done automatically now. Greg At 11:26 AM -0600 25/9/03, ron minnich wrote: >in arima/hdama/Config.lb > >## >## Clean up the motherboard id strings >## >option MAINBOARD_PART_NUMBER="HDAMA" >option MAINBOARD_VENDOR="ARIMA" > > > >OK, the config tool will create this by default: >MAINBOARD_PART_NUMBER="hdama" >MAINBOARD_VENDOR="arima" > >why do we need to put this type of thing in the mainboard config file? > >just wondering > >ron > >_______________________________________________ >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

memory epia-m 127M != 512M
by Niki Waibel 25 Sep '03

25 Sep '03

i use a 512MByte mem module in the epia-m 600mhz and linuxbios sayes: === totalram: 127M === i modified src/northbridge/via/vt8623/northbridge.c === diff -u -N -r freebios-20030924.old/src/northbridge/via/vt8623/northbridge.c freebios-20030924/src/northbridge/via/vt8623/north bridg e.c --- freebios-20030924.old/src/northbridge/via/vt8623/northbridge.c 2003-06-29 18:23:58.000000000 +0200 +++ freebios-20030924/src/northbridge/via/vt8623/northbridge.c 2003-09-24 14:10:22.025680920 +0200 @@ -9,10 +9,14 @@ { unsigned long totalmem; unsigned char bank, mem, prevmem; +#if 0 // fix me later -- there are two more banks at 0x56 and 0x57 unsigned long firstbank = 0x5a, lastbank = 0x5d; +#endif + unsigned long banks[] = { 0x56, 0x57, 0x5a, 0x5b, 0x5c, 0x5d }; + const unsigned long nbanks = 6; + unsigned long i; u8 sma_status, sma_size, sma_size_bits; - u8 val; struct pci_dev *pcidev; @@ -28,8 +32,9 @@ else sma_size = 0x01 << sma_size_bits; - for(totalmem = mem = prevmem = 0, bank = firstbank; - bank <= lastbank; bank++) { + totalmem = mem = prevmem = 0; + for(i=0; i<nbanks; i++) { + bank = banks[i]; pci_read_config_byte(pcidev, bank, &mem); // sanity check. If the mem value is < prevmem, // that is an error, so skip this step. @@ -41,7 +46,7 @@ totalmem += (mem - prevmem) * 16; prevmem = mem; } - + totalmem -= sma_size; totalmem *= 1024; #if 0 === but that did not help. this is no urgent problem, because 128M is enough for the system i want to build. but it could be a problem for other people. niki

6 9

arima mainboard config
by ron minnich 25 Sep '03

25 Sep '03

I find this in the arima mainboard config: ## ROM_SIZE is the size of boot ROM that this board will use. option ROM_SIZE = 524288 This is the wrong place. ROM_SIZE should always be in the target config file, not the mainboard config file. Recall that we no longer allow multiple settings of options, as a way of avoiding the "where did it get set last" syndrome. You only get to set them once. (we also disallow set-after-use, BTW). You can default them. I also note that in Options.lb, we are currently defaulting ROM_SIZE to 262144, also a mistake (mine). So what we need to do: in src/config/Options.lb, ROM_SIZE should have no default value. If you really want a default size for ROM_SIZE in the mainboard config, then default ROM_SIZE = 524288 in the mainboard file that way, for all my arimas on which I am using 1 MB parts, I can set option ROM_SIZE = 1024*1024 in my target config file. If no objections, I am going to remove the default setting in Options.lb, make the mainboard ROM_SIZE settings defaults, so I can continue to set them in the target config files. thanks ron

2 2

adding epia
by ron minnich 25 Sep '03

25 Sep '03

I've added a few things for epia. epia folks please look in freebios2 at src/northbridge/via/vt8601 (not done yet) src/southbridge/via/vt8231 the big thing to look at in the southbridge is how it is set up. The previous code was really out of touch w.r.t. the way you're supposed to do these chips nowadays, so this modified version is worth reading. I'll try to get more done on the mainboard today/tomorrow. ron p.s. freebios2 learning curve is a bit steep, but once you get the hang of it, you will probably like it. It got complicated when the k8 went in.

1 0

epia tree in V2
by ron minnich 25 Sep '03

25 Sep '03

I'm putting together an EPIA tree in V2. Give me a couple days. If this works it's definitely what we want to do. It should work. ron

1 0

arima hdama and bus 1
by ron minnich 25 Sep '03

25 Sep '03

What happens is that linuxbios properly scans and enables bus 1, but the linux that boots never scans bus 1 at all. So something is not quite set up right. More as I find it. ron

2 2

A case for your epia
by Ronald G. Minnich 24 Sep '03

24 Sep '03

http://www.idot.com/TheStore/Desktop/777spec.asp?Product.id=777&Cate.id=14&… $45. So we can get our EPIA with linuxbios from cwlinux.com, and then load them into this case. Might be a way to go. if only we could get 1 Mbyte flash parts for EPIA ... ron

2 1

[FILO] prompt doesn't work...
by NEWBELL7＠magicn.com 24 Sep '03

24 Sep '03

Hi, long time no see. I did build a filo with default config. ( make & make ) serial debug message is like below. But I can't type any command. VGA Console prompt has also the same problem. My Board is likely to EPIA 5000. Does FILO use only PS/2 keyboard as Input Device Driver? FILO !!! Good Idea . Thanks ... from newbie. ======================================================================== == FILO version 0.2 ( newbell@VIPER <mailto:newbell@VIPER> ) Thu Sep 25 09:18:26 KST 2003 Press <Enter> for default boot, or <Esc> for boot prompt... timed out boot: hda1:/boot/kernel.elf Unknown filesystem type boot:

2 1

8MB DiskOnChip
by Thomas Fritz 24 Sep '03

24 Sep '03

heh...asking questions without thinking.. [slaps forehead]...of COURSE it's writable! Now I just have the question...if I can install linux to the DOC, then I don't have to muck about with the BIOS, right? My calculus professor always said, "If you not want to make mistake, do nothing." Oh well...or should I say, Alright! More reading to be done!

1 0

Re: Windows-based terminals - what can be done?
by Thomas Fritz 24 Sep '03

24 Sep '03

>> >>What kind of ROM is this, exactly? Can you peel off the label and read >>what's printed on the chip(s)? > > > probably a DiskOnChip, This looks like the GX1 board I have. > Peel off the labels? Shucks, I can't do that...it'd be against Microsoft policy or something... [scampers off to peel the labels] Hey, it IS a DiskOnChip!...are these things Read-Only, or can they be re-written?

2 1

← Newer
1
2
3
4
5
6
7
8
9
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot September 2003