From zhushisongzhu at yahoo.com  Wed Dec  1 02:23:01 2004
From: zhushisongzhu at yahoo.com (zhu shi song)
Date: Wed Dec  1 02:23:01 2004
Subject: about power on
Message-ID: <20041201123825.35443.qmail@web13204.mail.yahoo.com>

   I hope when power is on, my MB can boot without
press the switch. How can I do that?
   tks
  zhu



		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 


From mark.wilkinson at 2pmtech.com  Wed Dec  1 06:47:00 2004
From: mark.wilkinson at 2pmtech.com (mark.wilkinson at 2pmtech.com)
Date: Wed Dec  1 06:47:00 2004
Subject: CVS Commit
Message-ID: <20041201172044.zjncwsgw4ogg4w0g@2pmtechnologies.com>

Hi All,
      I've just committed changes to the following files used by the VIA Epia

northbridge/via/vt8601/raminit.c
southbridge/via/vt8231/vt8231_early_smbus.c

Changes are as follows :-
  re-written smbus_read_byte based on intel/i82801dbm after suggestion from ron,
  modifications to raminit to handle changes on re-written routine.

Regards
Mark Wilkinson.

----------------------------------------------------------------
This message was sent using ISPMailNow.com


From ebiederman at lnxi.com  Wed Dec  1 10:21:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed Dec  1 10:21:01 2004
Subject: strange prink_debug output with dev_path
In-Reply-To: <3174569B9743D511922F00A0C943142306BA3523@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA3523@TYANWEB>
Message-ID: <m3sm6poiv4.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> What is the difference between 
>         printk_debug("smbus:  %s[%d]->",  dev_path(dev->bus->dev),
> dev->bus->link );
>         printk_debug("%s",  dev_path(dev));
> 
> and 
> 
>         printk_debug("smbus:  %s[%d]->%s",  dev_path(dev->bus->dev),
> dev->bus->link ,  dev_path(dev));
> 
> the first print 
> smbus:  PCI: 01:01.1[0]->I2C: 50
> 
> the second one print
> smbus:  PCI: 01:01.1[0]-> PCI: 01:01.1

dev_path returns the address of a statically allocated buffer
that it puts the path in.  That address is always the same.
So multiple calls to dev_path before printing the path are a
problem.

I had a hard time balancing convenience and safety when
implementing this.

If we need to fix this likely there are 2 possibilities.
1) Pass dev_path the address of a buffer, to write into.
2) Update printk to have a special format flag that
   performs the actions of dev_path.

Except for being a gotcha to watch out for I think we are ok.

Eric


From YhLu at tyan.com  Wed Dec  1 11:11:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec  1 11:11:01 2004
Subject: print_smbus_regs_all
Message-ID: <3174569B9743D511922F00A0C943142306BA3576@TYANWEB>

I add some code to debug_device to dump smbus for S4882.
 
Please let me know if you need me to commit it.
 
                                        device pci 1.3 on 
                                                chip drivers/generic/i2cmux 
                                                        device i2c 18 on #0
                                                                chip
drivers/generic/generic #cpu0 temp
 
device i2c 4c on end
                                                                end 
                                                        end
                                                        device i2c 18 on #1
                                                                chip
drivers/generic/generic #dimm 0-0-0
 
device i2c 30 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-0-1
 
device i2c 31 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-1-0
 
device i2c 32 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-1-1
 
device i2c 33 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-0-0
 
device i2c 50 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-0-1
 
device i2c 51 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-1-0
 
device i2c 52 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 0-1-1
 
device i2c 53 on end
                                                                end
                                                        end
                                                        device i2c 18 on #2
                                                                chip
drivers/generic/generic #dimm 1-0-0
 
device i2c 50 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-0-1
 
device i2c 51 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-1-0
 
device i2c 52 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-1-1
 
device i2c 53 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-0-0
 
device i2c 30 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-0-1
 
device i2c 31 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-1-0
 
device i2c 32 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 1-1-1
 
device i2c 33 on end
                                                                end
                                                        end
                                                        device i2c 18 on #3
                                                                chip
drivers/generic/generic #dimm 2-0-0
 
device i2c 50 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-0-1
 
device i2c 51 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-1-0
 
device i2c 52 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-1-1
 
device i2c 53 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-0-0
 
device i2c 30 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-0-1
 
device i2c 31 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-1-0
 
device i2c 32 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 2-1-1
 
device i2c 33 on end
                                                                end
                                                        end
                                                        device i2c 18 on #4
                                                                chip
drivers/generic/generic #dimm 3-0-0
 
device i2c 50 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-0-1
 
device i2c 51 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-1-0
 
device i2c 52 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-1-1
 
device i2c 53 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-0-0
 
device i2c 30 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-0-1
 
device i2c 31 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-1-0
 
device i2c 32 on end
                                                                end
                                                                chip
drivers/generic/generic #dimm 3-1-1
 
device i2c 33 on end
                                                                end
                                                        end
                                                        device i2c 18 on #0
                                                                chip
drivers/generic/generic #cpu1 temp
 
device i2c 4c on end
                                                                end
                                                        end
                                                        device i2c 18 on #0
                                                                chip
drivers/generic/generic #cpu2 temp
 
device i2c 4c on end
                                                                end
                                                        end
                                                        device i2c 18 on #0
                                                                chip
drivers/generic/generic #cpu3 temp
 
device i2c 4c on end
                                                                end
                                                        end
                                                end # i2cmux
                                                chip drivers/generic/generic
# ADM1027 CPU1 vid and System FAN...
                                                        device i2c 2e on end
                                                end
                                                chip drivers/generic/generic
# Winbond HWM 0x54 CPU1 vid 
                                                        device i2c 2a on end
                                                end
                                                chip drivers/generic/generic
# Winbond HWM 0x92
                                                        device i2c 49 on end
                                                end
                                                chip drivers/generic/generic
# Winbond HWM 0x94
                                                        device i2c 4a on end
                                                end
                                                chip drivers/generic/generic
# ??
                                                        device i2c 69 on end
                                                end
                                        end # acpi
 
smbus:  PCI: 01:04.3[0]->I2C: 18
00: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
10: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
20: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
30: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
40: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
50: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
60: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
70: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
80: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
90: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
a0: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
b0: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
c0: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
d0: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
e0: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
f0: e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 e0 10 f0 00 
smbus:  I2C: 18[0]->I2C: 4c
00: 22 31 92 80 08 46 00 46 00 80 08 46 00 46 00 00 
10: 60 00 00 00 00 00 a4 00 00 55 00 00 00 00 00 00 
20: 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 ff ff 20 3f 00 17 00 04 
50: 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 2e 20 43 dd 8f 00 05 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41 
smbus:  I2C: 18[1]->I2C: 30
00: bad device status= ffffffff
 
smbus:  I2C: 18[1]->I2C: 31
00: bad device status= ffffffff
 
smbus:  I2C: 18[1]->I2C: 32
00: bad device status= ffffffff
 
smbus:  I2C: 18[1]->I2C: 33
00: bad device status= ffffffff
 
smbus:  I2C: 18[1]->I2C: 50
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[1]->I2C: 51
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[1]->I2C: 52
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[1]->I2C: 53
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[2]->I2C: 50
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 67 24 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[2]->I2C: 51
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[2]->I2C: 52
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[2]->I2C: 53
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[2]->I2C: 30
00: bad device status= ffffffff
 
smbus:  I2C: 18[2]->I2C: 31
00: bad device status= ffffffff
 
smbus:  I2C: 18[2]->I2C: 32
00: bad device status= ffffffff
 
smbus:  I2C: 18[2]->I2C: 33
00: bad device status= ffffffff
 
smbus:  I2C: 18[3]->I2C: 50
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[3]->I2C: 51
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[3]->I2C: 52
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[3]->I2C: 53
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[3]->I2C: 30
00: bad device status= ffffffff
 
smbus:  I2C: 18[3]->I2C: 31
00: bad device status= ffffffff
 
smbus:  I2C: 18[3]->I2C: 32
00: bad device status= ffffffff
 
smbus:  I2C: 18[3]->I2C: 33
00: bad device status= ffffffff
 
smbus:  I2C: 18[4]->I2C: 50
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 09 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[4]->I2C: 51
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[4]->I2C: 52
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 15 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[4]->I2C: 53
00: 80 08 07 0d 0b 02 48 00 04 50 65 02 82 08 08 01 
10: 0e 04 18 01 02 26 c0 60 70 00 00 3c 28 3c 28 80 
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 50 64 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 0d 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
smbus:  I2C: 18[4]->I2C: 30
00: bad device status= ffffffff
 
smbus:  I2C: 18[4]->I2C: 31
00: bad device status= ffffffff
 
smbus:  I2C: 18[4]->I2C: 32
00: bad device status= ffffffff
 
smbus:  I2C: 18[4]->I2C: 33
00: bad device status= ffffffff
 
smbus:  I2C: 18[5]->I2C: 4c
00: 22 33 92 80 08 46 00 46 00 80 08 46 00 46 00 00 
10: e0 00 00 00 00 00 a4 00 00 55 00 00 00 00 00 00 
20: 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 ff ff 20 3f 00 17 00 04 
50: 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 21 20 41 dd 8c 00 05 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41 
smbus:  I2C: 18[6]->I2C: 4c
00: 22 31 92 80 08 46 00 46 00 80 08 46 00 46 00 00 
10: e0 00 00 00 00 00 a4 00 00 55 00 00 00 00 00 00 
20: 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 ff ff 20 3f 00 17 00 04 
50: 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 4c 20 46 d9 92 00 0d 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41 
smbus:  I2C: 18[7]->I2C: 4c
00: 21 34 12 80 08 46 00 46 00 80 08 46 00 46 00 00 
10: 20 00 00 00 00 00 a4 00 00 55 00 00 00 00 00 00 
20: 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 ff ff 20 3f 00 17 00 04 
50: 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 7f 3f 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 4a 20 4b d9 91 00 05 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41 
smbus:  PCI: 01:04.3[0]->I2C: 2e
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
20: 00 00 00 00 00 80 80 80 00 00 00 00 00 00 00 00 
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 27 41 60 
40: 04 00 00 02 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f 
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4 
60: c4 c4 00 00 80 80 80 5a 5a 5a 64 64 64 44 40 00 
70: 00 00 00 00 00 00 00 00 00 00 00 55 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
smbus:  PCI: 01:04.3[0]->I2C: 2a
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
20: 60 5f d1 bb a3 a3 4c 1b d7 d5 76 86 6d 86 6d ed 
30: b0 00 00 00 00 00 00 80 20 00 84 00 00 00 00 00 
40: 01 db 0b ff 3f 00 00 52 2a 02 21 44 18 95 80 5c 
50: ff ff 00 ff ff ff 00 80 21 70 ff ff 11 00 ff 05 
60: 60 60 d2 bb a3 a3 4d 1b d9 d5 76 86 6d 86 6d ed 
70: b0 00 00 00 00 00 00 80 20 00 84 00 00 00 00 00 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: 60 60 d2 bb a3 a3 4c 1b d8 d5 76 86 6d 86 6d ed 
b0: b0 00 00 00 00 00 00 80 20 00 84 00 00 00 00 00 
c0: 01 00 00 ff 3f 00 00 52 2a 02 21 44 18 95 80 5c 
d0: ff ff 00 ff ff ff 00 80 21 70 ff ff 11 00 ff 05 
e0: 60 60 d2 bb a3 a3 4d 1b d9 d5 77 86 6d 86 6d ed 
f0: b0 00 00 00 00 00 00 80 20 00 84 00 00 00 00 00 
smbus:  PCI: 01:04.3[0]->I2C: 49
00: 1c bad device status= ffffffff
 
smbus:  PCI: 01:04.3[0]->I2C: 4a
00: bad device status= ffffffff
 
smbus:  PCI: 01:04.3[0]->I2C: 69
00: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
10: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
20: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
30: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
40: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
50: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
60: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
70: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 
80: 00 ff fe 00 2f f8 0f 11 00 10 01 8b 64 0e 18 50 
90: ff 0f 0f 00 ff 01 ff aa ab 00 00 00 03 d3 d3 d3 
a0: 00 ff fe 00 2f f8 0f 11 00 10 01 8b 64 0e 18 50 
b0: ff 0f 0f 00 ff 01 ff aa ab 00 00 00 03 d3 d3 d3 
c0: 00 ff fe 00 2f f8 0f 11 00 10 01 8b 64 0e 18 50 
d0: ff 0f 0f 00 ff 01 ff aa ab 00 00 00 03 d3 d3 d3 
e0: 00 ff fe 00 2f f8 0f 11 00 10 01 8b 64 0e 18 50 
f0: ff 0f 0f 00 ff 01 ff aa ab 00 00 00 03 d3 d3 d3 
Devices initialized
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041201/72c9249a/attachment.html>

From stepan at openbios.org  Wed Dec  1 11:20:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed Dec  1 11:20:01 2004
Subject: error disclosure
Message-ID: <20041201213547.GA5745@openbios.org>

Hi there,

the error disclosure of the config tool is a little bit mystic.
Building the sandpoint configuration says the following:

Creating directory motorola_sandpoint/only
Creating motorola_sandpoint/only/static.c
Traceback (most recent call last):
  File "motorola_sandpoint/config.py", line 2732, in ?
    writecode(image)
  File "motorola_sandpoint/config.py", line 2649, in writecode
    gencode(image.getroot(), file, 1)
  File "motorola_sandpoint/config.py", line 2654, in gencode
    part.gencode(file, pass_num)
  File "motorola_sandpoint/config.py", line 804, in gencode
    file.write("struct device **last_dev_p = &%s.next;\n" %
(self.image.last_dev
ice.instance_name))
AttributeError: 'int' object has no attribute 'instance_name'

This looks like an error in the config tool, while it is a mistake in the
config file. Is there any easy way to point the user/developer to the
place in the config file that is wrong (rather than printing a python
traceback)?  This could make it a lot easier for newbies to create fresh
linuxbios ports to motherboards whose hardware is basically already
supported and it could safe the regulars quite some time comparing
config files between the ports...

Stefan





From ebiederman at lnxi.com  Wed Dec  1 11:32:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed Dec  1 11:32:00 2004
Subject: error disclosure
In-Reply-To: <20041201213547.GA5745@openbios.org>
References: <20041201213547.GA5745@openbios.org>
Message-ID: <m3653lk7wu.fsf@maxwell.lnxi.com>

Stefan Reinauer <stepan at openbios.org> writes:

> Hi there,
> 
> the error disclosure of the config tool is a little bit mystic.
> Building the sandpoint configuration says the following:

 
> This looks like an error in the config tool, while it is a mistake in the
> config file. Is there any easy way to point the user/developer to the
> place in the config file that is wrong (rather than printing a python
> traceback)?  This could make it a lot easier for newbies to create fresh
> linuxbios ports to motherboards whose hardware is basically already
> supported and it could safe the regulars quite some time comparing
> config files between the ports...

Last I looked a lot of the problem is design issues with the python parser
generator the code is using.  It does not do a very good job at remember 
making it possible to print good error messages.

The case you mention does not look like the typical failure there so it may
allow for a simple fix.

Eric




From ebiederman at lnxi.com  Wed Dec  1 11:33:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed Dec  1 11:33:00 2004
Subject: print_smbus_regs_all
In-Reply-To: <3174569B9743D511922F00A0C943142306BA3576@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA3576@TYANWEB>
Message-ID: <m31xe9k7u2.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> I add some code to debug_device to dump smbus for S4882.
>  
> Please let me know if you need me to commit it.

I don't know about need but I think it could be handy to have.
Especially as we don't have many users of i2c code in the tree at the present
time.

Eric


From rminnich at lanl.gov  Wed Dec  1 11:43:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Dec  1 11:43:01 2004
Subject: error disclosure
In-Reply-To: <m3653lk7wu.fsf@maxwell.lnxi.com>
References: <20041201213547.GA5745@openbios.org> <m3653lk7wu.fsf@maxwell.lnxi.com>
Message-ID: <Pine.LNX.4.58.0412011458440.25082@linux.site>


On Wed, 1 Dec 2004, Eric W. Biederman wrote:

> Last I looked a lot of the problem is design issues with the python
> parser generator the code is using.  It does not do a very good job at
> remember making it possible to print good error messages.

yeah, that parser generator is disappointing in the error recovery.

Fixes gratefully accepted.

ron


From YhLu at tyan.com  Wed Dec  1 11:54:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec  1 11:54:01 2004
Subject: print_smbus_regs_all
Message-ID: <3174569B9743D511922F00A0C943142306BA357A@TYANWEB>

Please check the code.

I add set_link member to switch link on i2mux.

Regards

YH

-----Original Message-----
From: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
Sent: Wednesday, December 01, 2004 1:49 PM
To: YhLu
Cc: linuxbios at clustermatic.org
Subject: Re: print_smbus_regs_all

YhLu <YhLu at tyan.com> writes:

> I add some code to debug_device to dump smbus for S4882.
>  
> Please let me know if you need me to commit it.

I don't know about need but I think it could be handy to have.
Especially as we don't have many users of i2c code in the tree at the
present
time.

Eric

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fb2_tyan_i2muxdump.zip
Type: application/octet-stream
Size: 3593 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041201/4255faf0/attachment.obj>

From ginlin at nexcom.com.tw  Wed Dec  1 16:53:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec  1 16:53:01 2004
Subject: jump to boot code
Message-ID: <000001c4d81c$527e0150$4f01060a@nexcom.com.tw>

This is the message I got in the end. Linuxbios tries to load the ELF
image. 
It seems that there are 2 segments in the ELF. In the end, linuxbios
jumps to an entry that looks like the in the middle of the first
segment. 
Does it look right?
The FILO.elf doesn't seem to load succeffully.
 
Gin
============================================================
 
Found ELF candiate at offset 0
 
 (cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0
filesize 0xd068
 (cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 filesize
0x48
Dropping non PT_LOAD segment
 
Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0
filesz: 0x00 0000000000d068
Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048
filesz: 0x00 00000000000048
 
Jumping to boot code at 0x1092e4
 
entry    = 0x001092e4
lb_start = 0x00004000
lb_size  = 0x00024000
adjust   = 0xfe5d8400
buffer   = 0xfe5b8400
elf_boot_notes = 0x00015680
adjusted_boot_notes = 0xfe5eda80
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041201/dd738e68/attachment.html>

From ginlin at nexcom.com.tw  Wed Dec  1 17:17:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec  1 17:17:01 2004
Subject: irq routing table
Message-ID: <000001c4d81f$a3c096b0$4f01060a@nexcom.com.tw>

If I have a wrong checksum for my irq routing table, would that stops me
from booting successfully?
The question should be, does the irq_routing table matter at all?
Linuxbios runs through till it jumps to the entry of payload. I am just
trying to figure out why.
 
Gin
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041201/202d8c46/attachment.html>

From rminnich at lanl.gov  Wed Dec  1 18:57:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Dec  1 18:57:00 2004
Subject: irq routing table
In-Reply-To: <000001c4d81f$a3c096b0$4f01060a@nexcom.com.tw>
References: <000001c4d81f$a3c096b0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412012212200.25898@linux.site>


On Thu, 2 Dec 2004, Gin wrote:

> The question should be, does the irq_routing table matter at all?
> Linuxbios runs through till it jumps to the entry of payload. I am just
> trying to figure out why.

that's not irq table related, let's get our payload fixed first.

ron


From ginlin at nexcom.com.tw  Wed Dec  1 20:01:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec  1 20:01:01 2004
Subject: jump to boot code
In-Reply-To: <000001c4d81c$527e0150$4f01060a@nexcom.com.tw>
Message-ID: <000201c4d836$98c334e0$4f01060a@nexcom.com.tw>

I tested my payload(FILO.elf) with linux loader Grub. It has no problem
at all. So something must go wrong when linuxbios jumps to the payload.
FILO doesn't seem to run at all. No debug message over the console.
 
Don't' know if there is anyone familiar with ELF.
This is the message over the console at the end.
It seems that there are 2 segments in the ELF. In the end, linuxbios
jumps to an entry that looks like the in the middle of the first
segment. 
Does it look right?
 
 
============================================================
 
Found ELF candiate at offset 0
 
 (cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0
filesize 0xd068
 (cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 filesize
0x48
Dropping non PT_LOAD segment
 
Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0
filesz: 0x00 0000000000d068
Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048
filesz: 0x00 00000000000048
 
Jumping to boot code at 0x1092e4
 
entry    = 0x001092e4
lb_start = 0x00004000
lb_size  = 0x00024000
adjust   = 0xfe5d8400
buffer   = 0xfe5b8400
elf_boot_notes = 0x00015680
adjusted_boot_notes = 0xfe5eda80
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041201/c0d915ff/attachment.html>

From mark.wilkinson at 2pmtech.com  Thu Dec  2 00:09:01 2004
From: mark.wilkinson at 2pmtech.com (mark.wilkinson at 2pmtech.com)
Date: Thu Dec  2 00:09:01 2004
Subject: devices/pci_devices.c
Message-ID: <20041202104345.fj6ok84c4kokg8o0@2pmtechnologies.com>

Hi Eric, Ron,
    I noticed what might be a slight problem with some error messages in the
pci_level_irq routine. When it reports the new settings, it masks off the lower
nibble of intBits to compare against the byte read. If an interrupt line is set
in the upper nibble of the byte, then the error message will always be
displayed even if the setting was successful.

I've included a diff that should fix the masks.

Regards
Mark Wilkinson.

----------------------------------------------------------------
This message was sent using ISPMailNow.com
-------------- next part --------------
Index: freebios2/src/devices/pci_device.c
===================================================================
RCS file: /cvsroot/freebios/freebios2/src/devices/pci_device.c,v
retrieving revision 1.29
diff -u -r1.29 pci_device.c
--- freebios2/src/devices/pci_device.c	21 Oct 2004 10:43:55 -0000	1.29
+++ freebios2/src/devices/pci_device.c	2 Dec 2004 10:15:11 -0000
@@ -924,13 +924,13 @@
 
 	/* this seems like an error but is not ... */
 #if 1
-	if (inb(0x4d0) != (intBits & 0xf)) {
+	if (inb(0x4d0) != (intBits & 0xff)) {
 	  printk_err("%s: lower order bits are wrong: want 0x%x, got 0x%x\n",
-		     __func__, intBits &0xf, inb(0x4d0));
+		     __func__, intBits &0xff, inb(0x4d0));
 	}
-	if (inb(0x4d1) != ((intBits >> 8) & 0xf)) {
-	  printk_err("%s: lower order bits are wrong: want 0x%x, got 0x%x\n",
-		     __func__, (intBits>>8) &0xf, inb(0x4d1));
+	if (inb(0x4d1) != ((intBits >> 8) & 0xff)) {
+	  printk_err("%s: high order bits are wrong: want 0x%x, got 0x%x\n",
+		     __func__, (intBits>>8) &0xff, inb(0x4d1));
 	}
 #endif
 }

From ginlin at nexcom.com.tw  Thu Dec  2 03:09:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Thu Dec  2 03:09:00 2004
Subject: elfboot
In-Reply-To: <000201c4d836$98c334e0$4f01060a@nexcom.com.tw>
Message-ID: <000001c4d872$4f54ded0$4f01060a@nexcom.com.tw>

I am not able to get linuxbios to load my payload(FILO.elf). Linuxbios
went through and jumps to the entry of the payload. 
 
1.      Is the elfboot code robust enough(I checked most of the code, it
seems good)?
2.      Can you suggest any direction for debugging? (everything looks
good to me but it won't boot)?
3.      would change the boot loader(rather than elfboot) help?
 
 
Thanks,
Gin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041202/ca03090d/attachment.html>

From gwatson at lanl.gov  Thu Dec  2 04:42:01 2004
From: gwatson at lanl.gov (Greg Watson)
Date: Thu Dec  2 04:42:01 2004
Subject: jump to boot code
In-Reply-To: <000201c4d836$98c334e0$4f01060a@nexcom.com.tw>
References: <000201c4d836$98c334e0$4f01060a@nexcom.com.tw>
Message-ID: <789281B6-4472-11D9-B97F-000D932F4B4A@lanl.gov>

If you do an 'objdump -f' on the executable, what does it say is the 
start address? 0x1092e4 seems a bit strange.

Greg

On Dec 1, 2004, at 11:17 PM, Gin wrote:

> I tested my payload(FILO.elf) with linux loader Grub. It has no 
> problem at all. So something must go wrong when linuxbios jumps to the 
> payload. FILO doesn't seem to run at all. No debug message over the 
> console.
>
> ?
>
> Don?t? know if there is anyone familiar with ELF.
>
> This is the message over the console at the end.
>
> It seems that there are 2 segments in the ELF. In the end, linuxbios 
> jumps to an entry that looks like the in the middle of the first 
> segment.
>
>  Does it look right?
>
> ?
>
> ?
>
> ============================================================
>
> ?
>
> Found ELF candiate at offset 0
>
> ?
>
> ?(cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0 
> filesize 0xd068
>
> ?(cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 
> filesize 0x48
>
> Dropping non PT_LOAD segment
>
> ?
>
> Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0 
> filesz: 0x00 0000000000d068
>
> Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048 
> filesz: 0x00 00000000000048
>
> ?
>
> Jumping to boot code at 0x1092e4
>
> ?
>
> entry??? = 0x001092e4
>
> lb_start = 0x00004000
>
> lb_size? = 0x00024000
>
> adjust?? = 0xfe5d8400
>
> buffer?? = 0xfe5b8400
>
> elf_boot_notes = 0x00015680
>
> adjusted_boot_notes = 0xfe5eda80
>
> ?
>
> ?



From rminnich at lanl.gov  Thu Dec  2 05:13:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  2 05:13:01 2004
Subject: jump to boot code
In-Reply-To: <000201c4d836$98c334e0$4f01060a@nexcom.com.tw>
References: <000201c4d836$98c334e0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412020829090.27809@linux.site>

the problem is that your error messages are kind of ok. Did you build a 
filo with serial port only console?

ron



From ollie at lanl.gov  Thu Dec  2 07:14:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu Dec  2 07:14:00 2004
Subject: Allocating Resource for Legacy VGA Buffer
Message-ID: <1102008601.25042.7.camel@exponential.lanl.gov>

Eric,

I tried to allocate a MEM resource for legacy VGA framebuffer (0xA0000 -
0xBFFFF) on AMDK8 NB Fun 1. I find a new mem_pair and assigned base 
and size of the resource as the code show in the bottom. But at the run 
time the resrouce allocation code still try to allocate that resource
to  0xA0000 to 0x002ffffff. Why it does not care about the 
resource->size field nor the FIXED flag ?

Ollie

static void amdk8_create_vga_resource(device_t dev, unsigned nodeid)
{
	struct resource *resource;
	unsigned link;
	for (link = 0; link < dev->links; link++) {
		if (dev->link[link].bridge_ctrl & PCI_BRIDGE_CTL_VGA) {
			printk_info("%s: bridge on link %d has VGA device\n",
				    dev_path(dev), link);
			printk_info("creating MEM pair for VGA memory\n");
			/* Initialize the io space constraints on the current bus */
			resource =  amdk8_find_mempair(dev, nodeid, link);
			printk_info("MEM pair register %x\n", resource->index - 0x100);
			resource->base = 0xa0000;
			resource->size = 0x20000;
			resource->gran = 16;
			resource->align = 16;
			resource->flags = IORESOURCE_PREFETCH | IORESOURCE_MEM |
IORESOURCE_FIXED | IORESOURCE_ASSIGNED;
		}
	}
}
static void amdk8_set_resources(device_t dev)
{
	unsigned nodeid, link;
	int i;

	/* Find the nodeid */
	nodeid = amdk8_nodeid(dev);	

	amdk8_create_vga_resource(dev, nodeid);
	
	/* Set each resource we have found */
	for (i = 0; i < dev->resources; i++) {
		amdk8_set_resource(dev, &dev->resource[i], nodeid);
	}
	
	for(link = 0; link < dev->links; link++) {
		struct bus *bus;
		bus = &dev->link[link];
		if (bus->children) {
			assign_resources(bus);
		}
	}
}




From ollie at lanl.gov  Thu Dec  2 07:20:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu Dec  2 07:20:00 2004
Subject: Substractive Resource
Message-ID: <1102008952.25042.11.camel@exponential.lanl.gov>

Eric,

You explained substractive decoding to me long time ago but I really 
forgot what it is. Could you tell me again ? Hoe do you determine if
some resource of some device is substractive ? Form the data sheet ?

Ollie




From ginlin at nexcom.com.tw  Thu Dec  2 15:17:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Thu Dec  2 15:17:00 2004
Subject: jump to boot code
In-Reply-To: <Pine.LNX.4.58.0412020829090.27809@linux.site>
Message-ID: <000501c4d8d7$fc126a10$4f01060a@nexcom.com.tw>

Yes, when I tested the filo with Grub. I could see the messages over the
serial console..... 

gin 

-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: Thursday, December 02, 2004 11:29 PM
To: Gin
Cc: 'LinuxBIOS'
Subject: Re: jump to boot code

the problem is that your error messages are kind of ok. Did you build a 
filo with serial port only console?

ron



From ginlin at nexcom.com.tw  Thu Dec  2 15:25:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Thu Dec  2 15:25:01 2004
Subject: jump to boot code
In-Reply-To: <789281B6-4472-11D9-B97F-000D932F4B4A@lanl.gov>
Message-ID: <000601c4d8d9$201c3980$4f01060a@nexcom.com.tw>

This is the header of my payload Filo.elf. it does have the starting
address.


=================================================
start address 0x001092e4

Program Header:
    LOAD off    0x000000a0 vaddr 0x00100000 paddr 0x00100000 align 2**5
         filesz 0x0000d048 memsz 0x000270d0 flags rwx
    LOAD off    0x0000d100 vaddr 0x001270e0 paddr 0x001270e0 align 2**5
         filesz 0x00000048 memsz 0x00000048 flags rw-
    NOTE off    0x000000c0 vaddr 0x00100020 paddr 0x00100020 align 2**5
         filesz 0x00000088 memsz 0x00000088 flags r--
======================================================


-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Greg Watson
Sent: Thursday, December 02, 2004 10:57 PM
To: Gin
Cc: 'LinuxBIOS'
Subject: Re: jump to boot code

If you do an 'objdump -f' on the executable, what does it say is the 
start address? 0x1092e4 seems a bit strange.

Greg

On Dec 1, 2004, at 11:17 PM, Gin wrote:

> I tested my payload(FILO.elf) with linux loader Grub. It has no 
> problem at all. So something must go wrong when linuxbios jumps to the

> payload. FILO doesn't seem to run at all. No debug message over the 
> console.
>
> ?
>
> Don?t? know if there is anyone familiar with ELF.
>
> This is the message over the console at the end.
>
> It seems that there are 2 segments in the ELF. In the end, linuxbios 
> jumps to an entry that looks like the in the middle of the first 
> segment.
>
>  Does it look right?
>
> ?
>
> ?
>
> ============================================================
>
> ?
>
> Found ELF candiate at offset 0
>
> ?
>
> ?(cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0 
> filesize 0xd068
>
> ?(cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 
> filesize 0x48
>
> Dropping non PT_LOAD segment
>
> ?
>
> Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0 
> filesz: 0x00 0000000000d068
>
> Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048 
> filesz: 0x00 00000000000048
>
> ?
>
> Jumping to boot code at 0x1092e4
>
> ?
>
> entry??? = 0x001092e4
>
> lb_start = 0x00004000
>
> lb_size? = 0x00024000
>
> adjust?? = 0xfe5d8400
>
> buffer?? = 0xfe5b8400
>
> elf_boot_notes = 0x00015680
>
> adjusted_boot_notes = 0xfe5eda80
>
> ?
>
> ?

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From yangzonghui at KONKA.COM  Thu Dec  2 15:50:01 2004
From: yangzonghui at KONKA.COM (yangzonghui at KONKA.COM)
Date: Thu Dec  2 15:50:01 2004
Subject: (no subject)
Message-ID: <OF82A19D56.17BF79E0-ON48256F5F.000ADE7F-48256F5F.000BAD01@konka.com>




hi,all:
      please tell me whether freebios can be installed on the machine of
694X-686A chipset, and anything special to do
as the document included in project directory.
      thanks !
yang



From yangzonghui at KONKA.COM  Thu Dec  2 15:50:24 2004
From: yangzonghui at KONKA.COM (yangzonghui at KONKA.COM)
Date: Thu Dec  2 15:50:24 2004
Subject: to 694X-686A chipset
Message-ID: <OF82A19D56.17BF79E0-ON48256F5F.000ADE7F-48256F5F.000BC164@konka.com>




hi,all:
      please tell me whether freebios can be installed on the machine of
694X-686A chipset, and anything special to do
as the document included in project directory.
      thanks !
yang



From YhLu at tyan.com  Thu Dec  2 17:26:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu Dec  2 17:26:01 2004
Subject: print_smbus_regs_all
Message-ID: <3174569B9743D511922F00A0C943142306BA3684@TYANWEB>

Just committed.

i2c mux support
CVS: ----------------------------------------------------------------------
CVS: Enter Log.  Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS:    devices/Config.lb drivers/generic/debug/debug_dev.c
CVS:    include/device/device.h include/device/smbus.h
CVS:    mainboard/tyan/s2885/Config.lb mainboard/tyan/s2885/auto.c
CVS:    mainboard/tyan/s2885/irq_tables.c
CVS:    mainboard/tyan/s4882/Config.lb northbridge/amd/amdk8/debug.c
CVS:    southbridge/amd/amd8111/amd8111_acpi.c
CVS: Added Files:
CVS:    devices/smbus_ops.c drivers/i2c/adm1026/Config.lb
CVS:    drivers/i2c/adm1026/adm1026.c drivers/i2c/adm1026/chip.h
CVS:    drivers/i2c/adm1027/Config.lb drivers/i2c/adm1027/adm1027.c
CVS:    drivers/i2c/adm1027/chip.h drivers/i2c/i2cmux/Config.lb
CVS:    drivers/i2c/i2cmux/chip.h drivers/i2c/i2cmux/i2cmux.c
CVS:    drivers/i2c/lm63/Config.lb drivers/i2c/lm63/chip.h
CVS:    drivers/i2c/lm63/lm63.c
CVS: ----------------------------------------------------------------------

-----Original Message-----
From: YhLu 
Sent: Wednesday, December 01, 2004 2:18 PM
To: ebiederman at lnxi.com
Cc: linuxbios at clustermatic.org
Subject: RE: print_smbus_regs_all

Please check the code.

I add set_link member to switch link on i2mux.

Regards

YH

-----Original Message-----
From: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
Sent: Wednesday, December 01, 2004 1:49 PM
To: YhLu
Cc: linuxbios at clustermatic.org
Subject: Re: print_smbus_regs_all

YhLu <YhLu at tyan.com> writes:

> I add some code to debug_device to dump smbus for S4882.
>  
> Please let me know if you need me to commit it.

I don't know about need but I think it could be handy to have.
Especially as we don't have many users of i2c code in the tree at the
present
time.

Eric



From ts1 at tsn.or.jp  Thu Dec  2 17:31:01 2004
From: ts1 at tsn.or.jp (Takeshi Sone)
Date: Thu Dec  2 17:31:01 2004
Subject: jump to boot code
In-Reply-To: <000501c4d8d7$fc126a10$4f01060a@nexcom.com.tw>
References: <Pine.LNX.4.58.0412020829090.27809@linux.site> <000501c4d8d7$fc126a10$4f01060a@nexcom.com.tw>
Message-ID: <20041203034654.GA4352@tsn.or.jp>

On Fri, Dec 03, 2004 at 09:32:31AM +0800, Gin wrote:
> Yes, when I tested the filo with Grub. I could see the messages over the
> serial console..... 

Did you try memtest86 as payload?

Given that filo runs ok under grub, I think the memory configuration
of LinuxBIOS is not working properly.
Especially the memory size that LB reports might be wrong, I guess.


From luc at bigdata.nb.ca  Thu Dec  2 18:02:01 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Thu Dec  2 18:02:01 2004
Subject: epia problem
Message-ID: <41AFE91C.9010104@bigdata.nb.ca>

I compiled from freebios2 from cvs, when I boot all I get back from the 
serial port is:

LinuxBIOS-1.1.7.0Normal <date> starting..
vt8601 init starting
Slot 00 is SDRAM 04000000 bytes x2
Slot 01 is empty
Slot 02 is empty
Slot 03 is empty
vt8601 is done
0

that's it.  I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I do 
that the resulting rom stops at Slot 00 is SDRAM 04000000 bytes x2.

I can't add uses DEFAULT_CONSOLE_LOGLEVEL or option 
DEFAULT_CONSOLE_LOGLEVEL in the Config.lb file either, the buildtarget 
scripts shuns it.

I'm using FILO as the payload, with no vga bios yet.

Could it be a FILO problem?  I've never seen linuxBIOS before yesterday 
so I don't know what should be appearing on the terminal..

Any assistance would be appreciated :)

Luc


From ginlin at nexcom.com.tw  Thu Dec  2 18:19:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Thu Dec  2 18:19:00 2004
Subject: jump to boot code
In-Reply-To: <20041203034654.GA4352@tsn.or.jp>
Message-ID: <000001c4d8f1$7cf893c0$4f01060a@nexcom.com.tw>

>Did you try memtest86 as payload?
No, do you know where I can get it? Thanks.


>Given that filo runs ok under grub, I think the memory configuration
>of LinuxBIOS is not working properly.
>Especially the memory size that LB reports might be wrong, I guess.

But the LB size was set during the link time according to the linker
script. How does it have to do with my mem configuration? 

gin



From liutao at safe-mail.net  Thu Dec  2 18:29:00 2004
From: liutao at safe-mail.net (Liu Tao)
Date: Thu Dec  2 18:29:00 2004
Subject: amd8111_nic fix
Message-ID: <41AFEFD0.3050305@safe-mail.net>

Hello,

On my board I have amd8111 nic + realtek 8201 PHY,
but 8111nic use active high reset signal to reset PHY
while RTL8201 accepts active low reset signal. However
amd8111 nic provides PHY_RESET_POLARITY bit in CMD3 register,
so I add the "phy_lowreset" register to handle this.
attached is the patch.

Regards,
Liu Tao



-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8111_nic.patch
Type: text/x-patch
Size: 3208 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041202/567a0e43/attachment.patch>

From ts1 at tsn.or.jp  Thu Dec  2 20:47:01 2004
From: ts1 at tsn.or.jp (Takeshi Sone)
Date: Thu Dec  2 20:47:01 2004
Subject: jump to boot code
In-Reply-To: <000001c4d8f1$7cf893c0$4f01060a@nexcom.com.tw>
References: <20041203034654.GA4352@tsn.or.jp> <000001c4d8f1$7cf893c0$4f01060a@nexcom.com.tw>
Message-ID: <20041203070315.GA11449@tsn.or.jp>

On Fri, Dec 03, 2004 at 12:35:01PM +0800, Gin wrote:
> >Did you try memtest86 as payload?
> No, do you know where I can get it? Thanks.

http://www.memtest86.com/

> >Given that filo runs ok under grub, I think the memory configuration
> >of LinuxBIOS is not working properly.
> >Especially the memory size that LB reports might be wrong, I guess.
> 
> But the LB size was set during the link time according to the linker
> script. How does it have to do with my mem configuration? 

I meant the size of RAM installed to your board. It is detected by LB at
runtime.

-- 
Takeshi


From mark.wilkinson at 2pmtech.com  Thu Dec  2 22:58:01 2004
From: mark.wilkinson at 2pmtech.com (mark.wilkinson at 2pmtech.com)
Date: Thu Dec  2 22:58:01 2004
Subject: epia problem
In-Reply-To: <41AFE91C.9010104@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca>
Message-ID: <20041203093248.fdmgww0owoo88k4s@2pmtechnologies.com>

Hi Luc,
       Can you check that you have the following lines in
mainboard/via/epia/Options.lb

use CONFIG_CONSOLE_SERIAL8250

default CONFIG_CONSOLE_SERIAL8250=1

I had a similar problem until I added these.

You should see LB getting a little further.

Regards
Mark Wilkinson

Quoting Luc Belliveau <luc at bigdata.nb.ca>:

> I compiled from freebios2 from cvs, when I boot all I get back from the
> serial port is:
>
> LinuxBIOS-1.1.7.0Normal <date> starting..
> vt8601 init starting
> Slot 00 is SDRAM 04000000 bytes x2
> Slot 01 is empty
> Slot 02 is empty
> Slot 03 is empty
> vt8601 is done
>
>
> that's it.  I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I do
> that the resulting rom stops at Slot 00 is SDRAM 04000000 bytes x2.
>
> I can't add uses DEFAULT_CONSOLE_LOGLEVEL or option
> DEFAULT_CONSOLE_LOGLEVEL in the Config.lb file either, the buildtarget
> scripts shuns it.
>
> I'm using FILO as the payload, with no vga bios yet.
>
> Could it be a FILO problem?  I've never seen linuxBIOS before yesterday
> so I don't know what should be appearing on the terminal..
>
> Any assistance would be appreciated :)
>
> Luc
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios



----------------------------------------------------------------
This message was sent using ISPMailNow.com



From rminnich at lanl.gov  Fri Dec  3 05:15:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec  3 05:15:00 2004
Subject: jump to boot code
In-Reply-To: <000501c4d8d7$fc126a10$4f01060a@nexcom.com.tw>
References: <000501c4d8d7$fc126a10$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412030830360.28557@linux.site>


On Fri, 3 Dec 2004, Gin wrote:

> Yes, when I tested the filo with Grub. I could see the messages over the
> serial console..... 

and nothing over vga, right? your filo is not trying to use vga.

ron


From rminnich at lanl.gov  Fri Dec  3 05:26:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec  3 05:26:00 2004
Subject: epia problem
In-Reply-To: <41AFE91C.9010104@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412030841520.28557@linux.site>


On Fri, 3 Dec 2004, Luc Belliveau wrote:

> I compiled from freebios2 from cvs, when I boot all I get back from the serial
> port is:
> 
> LinuxBIOS-1.1.7.0Normal <date> starting..
> vt8601 init starting
> Slot 00 is SDRAM 04000000 bytes x2
> Slot 01 is empty
> Slot 02 is empty
> Slot 03 is empty
> vt8601 is done
> 0
> 
> that's it.  I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I do that
> the resulting rom stops at Slot 00 is SDRAM 04000000 bytes x2.

well we need to ping mark wilkinson, as he just committed a bunch of fixes 
... 

Mark?

ron


From mark.wilkinson at 2pmtech.com  Fri Dec  3 06:04:00 2004
From: mark.wilkinson at 2pmtech.com (mark.wilkinson at 2pmtech.com)
Date: Fri Dec  3 06:04:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412030841520.28557@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca>
	<Pine.LNX.4.58.0412030841520.28557@linux.site>
Message-ID: <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>

Ron,
    Consider me Pre-Pinged !

I've already e-mailed Luc and the list, I guess you haven't caught up 
with your
e-mail yet :-)

There is definately a need to add the following 2 lines to
mainboard/via/epia/Options.lb

use CONFIG_CONSOLE_SERIAL8250
default CONFIG_CONSOLE_SERIAL8250=1

Current status of my epia code is as follows :-
     It's booted ! All the way though LB, loaded a kernel via filo from 
the hard
disk and let me login. There are issues with the speed, the boot sequence
seemed painfully slow. This could be for any number of mis-configured settings
at my end.

I also seem to have some spurious output before getting to the following line
LinuxBIOS-1.1.7.0Normal (date) starting...

which seems to be part of the northbridge debug lines.... I haven't 
tracked down
whats going on here yet.

At present, I'm trying to clean up the southbridge code.

Regards
Mark.


Quoting "Ronald G. Minnich" <rminnich at lanl.gov>:

> On Fri, 3 Dec 2004, Luc Belliveau wrote:
>
>> I compiled from freebios2 from cvs, when I boot all I get back from 
>> the serial
>> port is:
>>
>> LinuxBIOS-1.1.7.0Normal <date> starting..
>> vt8601 init starting
>> Slot 00 is SDRAM 04000000 bytes x2
>> Slot 01 is empty
>> Slot 02 is empty
>> Slot 03 is empty
>> vt8601 is done
>>
>>
>> that's it.  I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I do that
>> the resulting rom stops at Slot 00 is SDRAM 04000000 bytes x2.
>
> well we need to ping mark wilkinson, as he just committed a bunch of fixes
> ...
>
> Mark?
>
> ron
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios



----------------------------------------------------------------
This message was sent using ISPMailNow.com



From luc at bigdata.nb.ca  Fri Dec  3 09:18:01 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Fri Dec  3 09:18:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
References: <41AFE91C.9010104@bigdata.nb.ca>	<Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
Message-ID: <41B0BFDC.2060505@bigdata.nb.ca>

Thanks for the feedback, those lines helped.  Now I get as far as:

Welcome to elfboot, the open sourced starter.
January 2002, Eric Bierderman.
Version 1.3

And it sits there... should it be doing something else before it loads 
up FILO, or does this mean LinuxBIOS has finished it's job and now I 
need to play with the payload?

Thanks,

Luc

mark.wilkinson at 2pmtech.com wrote:

> Ron,
>    Consider me Pre-Pinged !
>
> I've already e-mailed Luc and the list, I guess you haven't caught up 
> with your
> e-mail yet :-)
>
> There is definately a need to add the following 2 lines to
> mainboard/via/epia/Options.lb
>
> use CONFIG_CONSOLE_SERIAL8250
> default CONFIG_CONSOLE_SERIAL8250=1
>
> Current status of my epia code is as follows :-
>     It's booted ! All the way though LB, loaded a kernel via filo from 
> the hard
> disk and let me login. There are issues with the speed, the boot sequence
> seemed painfully slow. This could be for any number of mis-configured 
> settings
> at my end.
>
> I also seem to have some spurious output before getting to the 
> following line
> LinuxBIOS-1.1.7.0Normal (date) starting...
>
> which seems to be part of the northbridge debug lines.... I haven't 
> tracked down
> whats going on here yet.
>
> At present, I'm trying to clean up the southbridge code.
>
> Regards
> Mark.
>
>
> Quoting "Ronald G. Minnich" <rminnich at lanl.gov>:
>
>> On Fri, 3 Dec 2004, Luc Belliveau wrote:
>>
>>> I compiled from freebios2 from cvs, when I boot all I get back from 
>>> the serial
>>> port is:
>>>
>>> LinuxBIOS-1.1.7.0Normal <date> starting..
>>> vt8601 init starting
>>> Slot 00 is SDRAM 04000000 bytes x2
>>> Slot 01 is empty
>>> Slot 02 is empty
>>> Slot 03 is empty
>>> vt8601 is done
>>>
>>>
>>> that's it.  I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I 
>>> do that
>>> the resulting rom stops at Slot 00 is SDRAM 04000000 bytes x2.
>>
>>
>> well we need to ping mark wilkinson, as he just committed a bunch of 
>> fixes
>> ...
>>
>> Mark?
>>
>> ron
>> _______________________________________________
>> Linuxbios mailing list
>> Linuxbios at clustermatic.org
>> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using ISPMailNow.com
>



From luc at bigdata.nb.ca  Fri Dec  3 11:03:01 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Fri Dec  3 11:03:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B0BFDC.2060505@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca>	<Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
Message-ID: <41B0D869.7070001@bigdata.nb.ca>

Oh, ok.  I just tried an etherboot payload, and that loads.  So it must 
be my FILO config.  .. I don't even get the boot: prompt.. 

I'm going to try the etherboot ide_disk maybe and and see what that does.

Any ideas what's going on with FILO?

Luc Belliveau wrote:

>
> Thanks for the feedback, those lines helped.  Now I get as far as:
>
> Welcome to elfboot, the open sourced starter.
> January 2002, Eric Bierderman.
> Version 1.3
>
> And it sits there... should it be doing something else before it loads 
> up FILO, or does this mean LinuxBIOS has finished it's job and now I 
> need to play with the payload?
>
> Thanks,
>
> Luc
>
> mark.wilkinson at 2pmtech.com wrote:
>
>> Ron,
>>    Consider me Pre-Pinged !
>>
>> I've already e-mailed Luc and the list, I guess you haven't caught up 
>> with your
>> e-mail yet :-)
>>
>> There is definately a need to add the following 2 lines to
>> mainboard/via/epia/Options.lb
>>
>> use CONFIG_CONSOLE_SERIAL8250
>> default CONFIG_CONSOLE_SERIAL8250=1
>>
>> Current status of my epia code is as follows :-
>>     It's booted ! All the way though LB, loaded a kernel via filo 
>> from the hard
>> disk and let me login. There are issues with the speed, the boot 
>> sequence
>> seemed painfully slow. This could be for any number of mis-configured 
>> settings
>> at my end.
>>
>> I also seem to have some spurious output before getting to the 
>> following line
>> LinuxBIOS-1.1.7.0Normal (date) starting...
>>
>> which seems to be part of the northbridge debug lines.... I haven't 
>> tracked down
>> whats going on here yet.
>>
>> At present, I'm trying to clean up the southbridge code.
>>
>> Regards
>> Mark.
>>
>>
>> Quoting "Ronald G. Minnich" <rminnich at lanl.gov>:
>>
>>> On Fri, 3 Dec 2004, Luc Belliveau wrote:
>>>
>>>> I compiled from freebios2 from cvs, when I boot all I get back from 
>>>> the serial
>>>> port is:
>>>>
>>>> LinuxBIOS-1.1.7.0Normal <date> starting..
>>>> vt8601 init starting
>>>> Slot 00 is SDRAM 04000000 bytes x2
>>>> Slot 01 is empty
>>>> Slot 02 is empty
>>>> Slot 03 is empty
>>>> vt8601 is done
>>>>
>>>>
>>>> that's it.  I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when 
>>>> I do that
>>>> the resulting rom stops at Slot 00 is SDRAM 04000000 bytes x2.
>>>
>>>
>>>
>>> well we need to ping mark wilkinson, as he just committed a bunch of 
>>> fixes
>>> ...
>>>
>>> Mark?
>>>
>>> ron
>>> _______________________________________________
>>> Linuxbios mailing list
>>> Linuxbios at clustermatic.org
>>> http://www.clustermatic.org/mailman/listinfo/linuxbios
>>
>>
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using ISPMailNow.com
>>
>
>



From rminnich at lanl.gov  Fri Dec  3 11:07:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec  3 11:07:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B0D869.7070001@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
 <41B0D869.7070001@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412031422500.31144@linux.site>


On Fri, 3 Dec 2004, Luc Belliveau wrote:

> 
> Oh, ok.  I just tried an etherboot payload, and that loads.  So it must be my
> FILO config.  .. I don't even get the boot: prompt.. I'm going to try the
> etherboot ide_disk maybe and and see what that does.

wow. Usually here it's always etherboot that won't work. 

I can send you a working filo.elf if you want.

ron


From luc at bigdata.nb.ca  Fri Dec  3 11:09:00 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Fri Dec  3 11:09:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412031422500.31144@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca> <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
Message-ID: <41B0D9DA.2090704@bigdata.nb.ca>

yes, that could help.

Thanks

Luc

Ronald G. Minnich wrote:

>On Fri, 3 Dec 2004, Luc Belliveau wrote:
>
>  
>
>>Oh, ok.  I just tried an etherboot payload, and that loads.  So it must be my
>>FILO config.  .. I don't even get the boot: prompt.. I'm going to try the
>>etherboot ide_disk maybe and and see what that does.
>>    
>>
>
>wow. Usually here it's always etherboot that won't work. 
>
>I can send you a working filo.elf if you want.
>
>ron
>  
>



From luc at bigdata.nb.ca  Fri Dec  3 11:21:01 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Fri Dec  3 11:21:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412031422500.31144@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca> <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
Message-ID: <41B0DC84.1040105@bigdata.nb.ca>

umm.. ok now FILO loads, but I get "IDE channel 0 not found"

Ronald G. Minnich wrote:

>On Fri, 3 Dec 2004, Luc Belliveau wrote:
>
>  
>
>>Oh, ok.  I just tried an etherboot payload, and that loads.  So it must be my
>>FILO config.  .. I don't even get the boot: prompt.. I'm going to try the
>>etherboot ide_disk maybe and and see what that does.
>>    
>>
>
>wow. Usually here it's always etherboot that won't work. 
>
>I can send you a working filo.elf if you want.
>
>ron
>  
>



From YhLu at tyan.com  Fri Dec  3 12:00:02 2004
From: YhLu at tyan.com (YhLu)
Date: Fri Dec  3 12:00:02 2004
Subject: k8 cpu rev
Message-ID: <3174569B9743D511922F00A0C943142306BA36D3@TYANWEB>

northbridge/amd/amdk8/cpu_rev.c

static int is_cpu_pre_c0(void)
{
        return (cpuid_eax(1) & 0xffef) < 0x0f48;
}

Why need to and 0xffef?

YH


From rminnich at lanl.gov  Fri Dec  3 12:39:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec  3 12:39:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B0DC84.1040105@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
 <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
 <41B0DC84.1040105@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412031555170.31548@linux.site>


On Fri, 3 Dec 2004, Luc Belliveau wrote:

> 
> umm.. ok now FILO loads, but I get "IDE channel 0 not found"


This is a good sign. trust me. 

I'll try to build you a better one :-)

ron


From rminnich at lanl.gov  Fri Dec  3 12:43:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec  3 12:43:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B0DC84.1040105@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
 <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
 <41B0DC84.1040105@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412031555460.31548@linux.site>


On Fri, 3 Dec 2004, Luc Belliveau wrote:

> 
> umm.. ok now FILO loads, but I get "IDE channel 0 not found"

this means your filo build is broken. 

send me your defconfig for filo.

ron


From YhLu at tyan.com  Fri Dec  3 13:27:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri Dec  3 13:27:01 2004
Subject: K8 D0 support
Message-ID: <3174569B9743D511922F00A0C943142306BA36F2@TYANWEB>

Eric,

Are you working on Opteron D0 support? There are some memory initialization
changes to support D0...

YH



From ebiederman at lnxi.com  Fri Dec  3 16:01:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Dec  3 16:01:01 2004
Subject: Substractive Resource
In-Reply-To: <1102008952.25042.11.camel@exponential.lanl.gov>
References: <1102008952.25042.11.camel@exponential.lanl.gov>
Message-ID: <m37jnykdsv.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> Eric,
> 
> You explained substractive decoding to me long time ago but I really 
> forgot what it is. Could you tell me again ? Hoe do you determine if
> some resource of some device is substractive ? Form the data sheet ?


A subtractive bridge resource is a bridge resource that picks
up the unclaimed transactions and forwards them on.  In networking
the equivalent concept the default route.  A subtractive resource
is what picks up all of the traffic on a bus that does not have a
specific route to somewhere else.

Eric


From ebiederman at lnxi.com  Fri Dec  3 16:05:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Dec  3 16:05:01 2004
Subject: Allocating Resource for Legacy VGA Buffer
In-Reply-To: <1102008601.25042.7.camel@exponential.lanl.gov>
References: <1102008601.25042.7.camel@exponential.lanl.gov>
Message-ID: <m33bymkdmk.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> Eric,
> 
> I tried to allocate a MEM resource for legacy VGA framebuffer (0xA0000 -
> 0xBFFFF) on AMDK8 NB Fun 1. I find a new mem_pair and assigned base 
> and size of the resource as the code show in the bottom. But at the run 
> time the resrouce allocation code still try to allocate that resource
> to  0xA0000 to 0x002ffffff. Why it does not care about the 
> resource->size field nor the FIXED flag ?

The resource allocator should and it does in other cases.

Hmm.  You don't even allocate this resource in read_resources
so the resource allocator might should not even see it.  

The IORESOURCE_PREFETCH is not correct for that area though.
Setting up write-combining MSRs would be a very bad thing
to have happen.  Which is what IORESOURCE_PREFETCH implies is
legal.

Eric


> static void amdk8_create_vga_resource(device_t dev, unsigned nodeid)
> {
> 	struct resource *resource;
> 	unsigned link;
> 	for (link = 0; link < dev->links; link++) {
> 		if (dev->link[link].bridge_ctrl & PCI_BRIDGE_CTL_VGA) {
> 			printk_info("%s: bridge on link %d has VGA device\n",
> 				    dev_path(dev), link);
> 			printk_info("creating MEM pair for VGA memory\n");
> 			/* Initialize the io space constraints on the current
> bus */
> 
> 			resource =  amdk8_find_mempair(dev, nodeid, link);
> 			printk_info("MEM pair register %x\n", resource->index -
> 0x100);
> 
> 			resource->base = 0xa0000;
> 			resource->size = 0x20000;
> 			resource->gran = 16;
> 			resource->align = 16;
> 			resource->flags = IORESOURCE_PREFETCH | IORESOURCE_MEM |
> 
> IORESOURCE_FIXED | IORESOURCE_ASSIGNED;
> 		}
> 	}
> }
> static void amdk8_set_resources(device_t dev)
> {
> 	unsigned nodeid, link;
> 	int i;
> 
> 	/* Find the nodeid */
> 	nodeid = amdk8_nodeid(dev);	
> 
> 	amdk8_create_vga_resource(dev, nodeid);
> 	
> 	/* Set each resource we have found */
> 	for (i = 0; i < dev->resources; i++) {
> 		amdk8_set_resource(dev, &dev->resource[i], nodeid);
> 	}
> 	
> 	for(link = 0; link < dev->links; link++) {
> 		struct bus *bus;
> 		bus = &dev->link[link];
> 		if (bus->children) {
> 			assign_resources(bus);
> 		}
> 	}
> }


From ebiederman at lnxi.com  Fri Dec  3 16:06:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Dec  3 16:06:01 2004
Subject: k8 cpu rev
In-Reply-To: <3174569B9743D511922F00A0C943142306BA36D3@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA36D3@TYANWEB>
Message-ID: <m3wtvyiyzj.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> northbridge/amd/amdk8/cpu_rev.c
> 
> static int is_cpu_pre_c0(void)
> {
>         return (cpuid_eax(1) & 0xffef) < 0x0f48;
> }
> 
> Why need to and 0xffef?

Look at the various cpuid values that happen to be c0 stepping
processors.

Eric


From ebiederman at lnxi.com  Fri Dec  3 16:08:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Dec  3 16:08:01 2004
Subject: K8 D0 support
In-Reply-To: <3174569B9743D511922F00A0C943142306BA36F2@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA36F2@TYANWEB>
Message-ID: <m3sm6miyws.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> Eric,
> 
> Are you working on Opteron D0 support? There are some memory initialization
> changes to support D0...

It is on the near term TODO list, as are way to many other
things.  I need to make certain I have some so I can test with them.
My impression the biggest change was the E0 stepping processors.

In any event until the information goes into the public datasheet
I can't publish anything.

Eric


From etorres at tux.uis.edu.co  Fri Dec  3 17:33:01 2004
From: etorres at tux.uis.edu.co (Edmanuel Torres)
Date: Fri Dec  3 17:33:01 2004
Subject: How I can start a cluster with M825G VIA KM266-8235,
Message-ID: <4342.192.168.41.39.1102132155.squirrel@tux.uis.edu.co>

I want to build a cluster based in the M825G with chipset VIA KM266-8235
mainboard from PCCHIPS, but I have found that this is not supported by the
available configuration files in the mainboards folder. I wonder is
somebody can help me in to find the way to make this board work with
LinuxBios?. below is the output of the -lspci -vvv command. Thanks in
advance, Edmanuel

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host
Bridge
	Subsystem: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort+ >SERR- <PERR-
	Latency: 8
	Region 0: Memory at ea000000 (32-bit, prefetchable) [size=4M]
	Capabilities: [a0] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW-
AGP3- Rate=x1,x2,x4
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x2,x4
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
(prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort+ >SERR- <PERR+
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: e8000000-e9ffffff
	Prefetchable memory behind bridge: e0000000-e7ffffff
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
	Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if
8a [Master SecP PriP])
	Subsystem: VIA Technologies, Inc.
VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 32
	Interrupt: pin A routed to IRQ 20
	Region 4: I/O ports at dc00 [size=16]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 74)
	Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet
Controller on VT8235
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 32 (750ns min, 2000ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 23
	Region 0: I/O ports at e000 [size=256]
	Region 1: Memory at ea401000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8
KM266/KL266] (prog-if 00 [VGA])
	Subsystem: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 32 (1000ns min, 63750ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e9000000 (32-bit, non-prefetchable) [size=512K]
	Region 1: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bi


=================================================
Edmanuel Torres
MSc. in Physics (Student)
Mobile: 3008207876 - 3112022606
Phone: +57 (7)632 3477 - +57 (7)634 4000 Ext 2402
Fax:   +57 (7)634 6149 - +57 (7)632 3477
Physics and Technology Plasma Group
Physics School,
Universidad Industrial de Santander,
Bucaramanga, Colombia
AA 678


From YhLu at tyan.com  Fri Dec  3 19:55:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri Dec  3 19:55:01 2004
Subject: K8 D0 support
Message-ID: <3174569B9743D511922F00A0C943142306BA371B@TYANWEB>

Opteron Rev D0 support done.

So I need to wait for AMD put the updated Bios porting guide including
Opteron Rev D0 info. Only after that, I can commit the patch?
Or ask the AMD to review the code?

Regards

YH

-----Original Message-----
From: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
Sent: Friday, December 03, 2004 6:24 PM
To: YhLu
Cc: Stefan Reinauer; linuxbios at clustermatic.org
Subject: Re: K8 D0 support

YhLu <YhLu at tyan.com> writes:

> Eric,
> 
> Are you working on Opteron D0 support? There are some memory
initialization
> changes to support D0...

It is on the near term TODO list, as are way to many other
things.  I need to make certain I have some so I can test with them.
My impression the biggest change was the E0 stepping processors.

In any event until the information goes into the public datasheet
I can't publish anything.

Eric


From zhushisongzhu at yahoo.com  Fri Dec  3 20:36:01 2004
From: zhushisongzhu at yahoo.com (zhu shi song)
Date: Fri Dec  3 20:36:01 2004
Subject: about power on
In-Reply-To: <191978113.20041202124029@amelkin.msk.ru>
Message-ID: <20041204065214.92160.qmail@web13203.mail.yahoo.com>

Who know the software solution?
tks
zhu


--- Alexander Amelkin <alexander at amelkin.msk.ru>
wrote:

> Hi!
> 
> zss>    I hope when power is on, my MB can boot
> without
> zss> press the switch. How can I do that?
> 
> Browse the archive of the list for the answer.
> Keyword is M789.
> 
> The main idea is to put a small (~~20uF) capacitor
> between the two pins
> of the power switch header on the motherboard.
> 
> You must only do that if your motherboard does not
> have a "Power Loss
> Restart" or similar option in the BIOS Setup.
> 
> LinuxBIOS as far as I know, does not allow to set
> the power loss restart
> option.
> 
> -- 
> WBR, Alexander                         
> mailto:spirit at reactor.ru
> 
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 



From zhushisongzhu at yahoo.com  Sat Dec  4 04:28:00 2004
From: zhushisongzhu at yahoo.com (zhu shi song)
Date: Sat Dec  4 04:28:00 2004
Subject: about MAINBOARD_POWER_ON_AFTER_POWER_FAIL
Message-ID: <20041204144458.89131.qmail@web13201.mail.yahoo.com>

I'm using i845gv based MB. The superio is w83627hf . 
I have set
MAINBOARD_POWER_ON_AFTER_POWER_FAIL=MAINBOARD_POWER_ON.Before
linux booting up, I turn off power switch, when turn
on power swith again, MB can boot again.  But when I
have booted linux successfully, I can see the console
and can login linux, at this time I turn off the power
switch and after 10secs then turn on it, MB can't boot
again.
Who have such experience to make mainboard power on
again after power fail using software solution?
tks
zhu


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250


From rminnich at lanl.gov  Sat Dec  4 05:53:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Dec  4 05:53:01 2004
Subject: about MAINBOARD_POWER_ON_AFTER_POWER_FAIL
In-Reply-To: <20041204144458.89131.qmail@web13201.mail.yahoo.com>
References: <20041204144458.89131.qmail@web13201.mail.yahoo.com>
Message-ID: <Pine.LNX.4.58.0412040908510.1344@linux.site>

you can take a look at that the arima hdama code does for this. It is all 
motherboard-specific, I guess ... not sure in all cases.

ron



From luc at bigdata.nb.ca  Sat Dec  4 06:19:00 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Sat Dec  4 06:19:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412040904550.1344@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca> <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site> <41B0DC84.1040105@bigdata.nb.ca> <Pine.LNX.4.58.0412031555460.31548@linux.site> <41B124AC.5000301@bigdata.nb.ca> <Pine.LNX.4.58.0412040904550.1344@linux.site>
Message-ID: <41B1E740.5030505@bigdata.nb.ca>

Same thing, with one small difference... I turned debugging on and this 
is what I get :

find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8f
find_ide_controller: primary channel: native PCI mode
find_ide_controller: cmd_base=0x0 ctrl_base=0x0
ide_software_reset: Waiting for ide0 to become ready for reset.. ok
init_drive: Testing for hda
init_drive: Probing for hda
Invalid IDE Configuration: 7ed8  <-- this line used to be 3ed8 with my 
previous conf
init_drive: Testing for hda
init_drive: Probing for hda
print_status: IDE: status=0xa1, err=0x0
Drive 0 does not exist

boot:

Also the first time I compiled filo and the rom, it halted at the 
elfboot screen, then I recompiled with the same settings, and filo 
loaded.. strange..

Luc


Ronald G. Minnich wrote:

>try this one
>
>ron
>p.s. make sure you do the make config or whatever it is to remake all the 
>files that depend on defconf
>
>
># !!! NOTE !!!
># Do NOT add spaces or comments at the end of option lines.
># It confuses some versions of make.
>
># Image filename for automatic boot and optional command line parameter
>AUTOBOOT_FILE = "hda1:/vmlinuz-normal initrd=hda1:/initrd-normal.gz  root=/dev/ram0 console=ttyS0,115200"
>
># Time in second before booting AUTOBOOT_FILE
>AUTOBOOT_DELAY = 2
>
># Driver for hard disk, CompactFlash, and CD-ROM on IDE bus
>IDE_DISK = 1
>
># VGA text console
>VGA_CONSOLE = 1
>PC_KEYBOARD = 1
>
># Serial console
>SERIAL_CONSOLE = 1
>SERIAL_IOBASE = 0x3f8
>SERIAL_SPEED = 115200
>
># Filesystems
>FSYS_EXT2FS = 1
>FSYS_FAT = 0
>FSYS_JFS = 0
>FSYS_MINIX = 0
>FSYS_REISERFS = 0
>FSYS_XFS = 0
>FSYS_ISO9660 = 0
>
># Support for boot disk image in bootable CD-ROM (El Torito)
>ELTORITO = 0
>
># PCI support
>SUPPORT_PCI = 1
>
># Enable this if not all PCI buses are scanned (you can see it with DEBUG_PCI)
># K8-based boards may need it
>PCI_BRUTE_SCAN = 1
>PCI_BRUTE_SCAN_LIMIT = 2
>PCI_BRUTE_SCAN_START = 1
>IDE_HINT_BUS=1
>IDE_HINT_DEV=4
>IDE_HINT_FUNC=1
>
># Sound support (needs SUPPORT_PCI)
>#SUPPORT_SOUND = 1
>
># Sound drivers
>#VIA_SOUND = 1
>
># Debugging
>#DEBUG_ALL = 1
>#DEBUG_ELFBOOT = 1
>#DEBUG_ELFNOTE = 1
>#DEBUG_LINUXBIOS = 1
>#DEBUG_MALLOC = 1
>#DEBUG_MULTIBOOT = 1
>#DEBUG_SEGMENT = 1
>#DEBUG_SYS_INFO = 1
>#DEBUG_TIMER = 1
>#DEBUG_BLOCKDEV = 1
>#DEBUG_PCI = 1
>#DEBUG_VIA_SOUND = 1
>#DEBUG_LINUXLOAD = 1
>#DEBUG_IDE = 1
>#DEBUG_ELTORITO = 1
>
>
>  
>



From rminnich at lanl.gov  Sat Dec  4 06:21:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Dec  4 06:21:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B1E740.5030505@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
 <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
 <41B0DC84.1040105@bigdata.nb.ca> <Pine.LNX.4.58.0412031555460.31548@linux.site>
 <41B124AC.5000301@bigdata.nb.ca> <Pine.LNX.4.58.0412040904550.1344@linux.site>
 <41B1E740.5030505@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412040937030.1344@linux.site>


On Sat, 4 Dec 2004, Luc Belliveau wrote:

> 
> Same thing, with one small difference... I turned debugging on and this is
> what I get :

hmm. 
> 
> find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8f
> find_ide_controller: primary channel: native PCI mode
> find_ide_controller: cmd_base=0x0 ctrl_base=0x0

well that is odd, actually. 

make this one change:
> > # K8-based boards may need it
> > PCI_BRUTE_SCAN = 1
> > PCI_BRUTE_SCAN_LIMIT = 2

> > PCI_BRUTE_SCAN_START = 1


> > PCI_BRUTE_SCAN_START = 1
                           0

ron


From luc at bigdata.nb.ca  Sat Dec  4 07:05:01 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Sat Dec  4 07:05:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412040937030.1344@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca> <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site> <41B0DC84.1040105@bigdata.nb.ca> <Pine.LNX.4.58.0412031555460.31548@linux.site> <41B124AC.5000301@bigdata.nb.ca> <Pine.LNX.4.58.0412040904550.1344@linux.site> <41B1E740.5030505@bigdata.nb.ca> <Pine.LNX.4.58.0412040937030.1344@linux.site>
Message-ID: <41B1F235.1050301@bigdata.nb.ca>


No effect.  Here  is the output when I boot:


LinuxBIOS-1.1.7.0Normal Sat Dec  4 10:16:38 AST 2004 starting...

87 is the comm register

SMBus controller enabled

vt8601 init starting

00000000 is the north

                     1106 0601

0120d4 is the computed timing

                             NOP

PRECHARGE

DUMMY READS

CBR

MRS

NORMAL

set ref. rate

enable multi-page open

Slot 00 is SDRAM 04000000 bytes x2

0040 is the chip size

0008 is the MA type

Slot 01 is empty

Slot 02 is empty

Slot 03 is empty

vt8601 done

Copying LinuxBIOS to ram.

Jumping to LinuxBIOS.

LinuxBIOS-1.1.7.0Normal Sat Dec  4 10:16:38 AST 2004 booting...

Enumerating buses...

scan_static_bus for Root Device

Finding PCI configuration type.

PCI: Using configuration type 1

PCI_DOMAIN: 0000 enabled

PCI_DOMAIN: 0000 scanning...

PCI: pci_scan_bus for bus 0

PCI: 00:00.0 [1106/0601] ops

PCI: 00:00.0 [1106/0601] enabled

malloc Enter, size 564, free_mem_ptr 00016000

malloc 0x00016000

PCI: 00:01.0 [1106/8601] enabled

PCI: devfn 0x10, bad id 0xffffffff

PCI: devfn 0x18, bad id 0xffffffff

PCI: devfn 0x20, bad id 0xffffffff

PCI: devfn 0x28, bad id 0xffffffff

PCI: devfn 0x30, bad id 0xffffffff

PCI: devfn 0x38, bad id 0xffffffff

PCI: devfn 0x40, bad id 0xffffffff

PCI: devfn 0x48, bad id 0xffffffff

PCI: devfn 0x50, bad id 0xffffffff

PCI: devfn 0x58, bad id 0xffffffff

PCI: devfn 0x60, bad id 0xffffffff

PCI: devfn 0x68, bad id 0xffffffff

PCI: devfn 0x70, bad id 0xffffffff

PCI: devfn 0x78, bad id 0xffffffff

PCI: devfn 0x80, bad id 0xffffffff

malloc Enter, size 564, free_mem_ptr 00016234

malloc 0x00016234

PCI: 00:11.0 [1106/8231] enabled

malloc Enter, size 564, free_mem_ptr 00016468

malloc 0x00016468

PCI: 00:11.1 [1106/0571] enabled

malloc Enter, size 564, free_mem_ptr 0001669c

malloc 0x0001669c

PCI: 00:11.2 [1106/3038] enabled

malloc Enter, size 564, free_mem_ptr 000168d0

malloc 0x000168d0

PCI: 00:11.3 [1106/3038] enabled

malloc Enter, size 564, free_mem_ptr 00016b04

malloc 0x00016b04

PCI: 00:11.4 [1106/8235] enabled

malloc Enter, size 564, free_mem_ptr 00016d38

malloc 0x00016d38

PCI: 00:11.5 [1106/3058] enabled

malloc Enter, size 564, free_mem_ptr 00016f6c

malloc 0x00016f6c

PCI: 00:11.6 [1106/3068] enabled

PCI: devfn 0x8f, bad id 0xffffffff

malloc Enter, size 564, free_mem_ptr 000171a0

malloc 0x000171a0

PCI: 00:12.0 [1106/3065] enabled

PCI: devfn 0x98, bad id 0xffffffff

PCI: devfn 0xa0, bad id 0xffffffff

PCI: devfn 0xa8, bad id 0xffffffff

PCI: devfn 0xb0, bad id 0xffffffff

PCI: devfn 0xb8, bad id 0xffffffff

PCI: devfn 0xc0, bad id 0xffffffff

PCI: devfn 0xc8, bad id 0xffffffff

PCI: devfn 0xd0, bad id 0xffffffff

PCI: devfn 0xd8, bad id 0xffffffff

PCI: devfn 0xe0, bad id 0xffffffff

PCI: devfn 0xe8, bad id 0xffffffff

PCI: devfn 0xf0, bad id 0xffffffff

PCI: devfn 0xf8, bad id 0xffffffff

PCI: pci_scan_bus for bus 1

PCI: devfn 0x0, bad id 0xffffffff

PCI: devfn 0x8, bad id 0xffffffff

PCI: devfn 0x10, bad id 0xffffffff

PCI: devfn 0x18, bad id 0xffffffff

PCI: devfn 0x20, bad id 0xffffffff

PCI: devfn 0x28, bad id 0xffffffff

PCI: devfn 0x30, bad id 0xffffffff

PCI: devfn 0x38, bad id 0xffffffff

PCI: devfn 0x40, bad id 0xffffffff

PCI: devfn 0x48, bad id 0xffffffff

PCI: devfn 0x50, bad id 0xffffffff

PCI: devfn 0x58, bad id 0xffffffff

PCI: devfn 0x60, bad id 0xffffffff

PCI: devfn 0x68, bad id 0xffffffff

PCI: devfn 0x70, bad id 0xffffffff

PCI: devfn 0x78, bad id 0xffffffff

PCI: devfn 0x80, bad id 0xffffffff

PCI: devfn 0x88, bad id 0xffffffff

PCI: devfn 0x90, bad id 0xffffffff

PCI: devfn 0x98, bad id 0xffffffff

PCI: devfn 0xa0, bad id 0xffffffff

PCI: devfn 0xa8, bad id 0xffffffff

PCI: devfn 0xb0, bad id 0xffffffff

PCI: devfn 0xb8, bad id 0xffffffff

PCI: devfn 0xc0, bad id 0xffffffff

PCI: devfn 0xc8, bad id 0xffffffff

PCI: devfn 0xd0, bad id 0xffffffff

PCI: devfn 0xd8, bad id 0xffffffff

PCI: devfn 0xe0, bad id 0xffffffff

PCI: devfn 0xe8, bad id 0xffffffff

PCI: devfn 0xf0, bad id 0xffffffff

PCI: devfn 0xf8, bad id 0xffffffff

PCI: pci_scan_bus returning with max=01

pci_scan_bridge returns max 1

PCI: pci_scan_bus returning with max=01

scan_static_bus for  Root Device done

done

Allocating resources...

Reading resources...

Root Device compute_allocate_io: base: 00000400 size: 00000000 align: 0 
gran: 0

Root Device read_resources bus 0 link: 0

PCI_DOMAIN: 0000 read_resources bus 0 link: 0

PCI: 00:00.0 register 10(00000008), read-only ignoring it

PCI: 00:01.0 compute_allocate_io: base: 00000000 size: 00000000 align: 
12 gran:

12

PCI: 00:01.0 read_resources bus 1 link: 0

PCI: 00:01.0 read_resources bus 1 link: 0 done

PCI: 00:01.0 compute_allocate_io: base: 00000000 size: 00000000 align: 
12 gran:

12 done

PCI: 00:01.0 compute_allocate_io: base: 0000f000 size: 00000000 align: 
12 gran:

12

PCI: 00:01.0 read_resources bus 1 link: 0

PCI: 00:01.0 read_resources bus 1 link: 0 done

PCI: 00:01.0 compute_allocate_io: base: 0000f000 size: 00000000 align: 
12 gran:

12 done

PCI: 00:01.0 1c <- [0x000000f000 - 0x000000efff] bus 1 io

PCI: 00:01.0 compute_allocate_prefmem: base: 00000000 size: 00000000 
align: 20 g

ran: 20

PCI: 00:01.0 read_resources bus 1 link: 0

PCI: 00:01.0 read_resources bus 1 link: 0 done

PCI: 00:01.0 compute_allocate_prefmem: base: 00000000 size: 00000000 
align: 20 g

ran: 20 done

PCI: 00:01.0 compute_allocate_prefmem: base: fff00000 size: 00000000 
align: 20 g

ran: 20

PCI: 00:01.0 read_resources bus 1 link: 0

PCI: 00:01.0 read_resources bus 1 link: 0 done

PCI: 00:01.0 compute_allocate_prefmem: base: fff00000 size: 00000000 
align: 20 g

ran: 20 done

PCI: 00:01.0 24 <- [0x00fff00000 - 0x00ffefffff] bus 1 prefmem

PCI: 00:01.0 compute_allocate_mem: base: 00000000 size: 00000000 align: 
20 gran:

 20

PCI: 00:01.0 read_resources bus 1 link: 0

PCI: 00:01.0 read_resources bus 1 link: 0 done

PCI: 00:01.0 compute_allocate_mem: base: 00000000 size: 00000000 align: 
20 gran:

 20 done

PCI: 00:01.0 compute_allocate_mem: base: fff00000 size: 00000000 align: 
20 gran:

 20

PCI: 00:01.0 read_resources bus 1 link: 0

PCI: 00:01.0 read_resources bus 1 link: 0 done

PCI: 00:01.0 compute_allocate_mem: base: fff00000 size: 00000000 align: 
20 gran:

 20 done

PCI: 00:01.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 1 mem

PCI_DOMAIN: 0000 read_resources bus 0 link: 0 done

Root Device read_resources bus 0 link: 0 done

PCI: 00:11.5 10 *  [0x00000400 - 0x000004ff] io

PCI: 00:11.6 10 *  [0x00000800 - 0x000008ff] io

PCI: 00:12.0 10 *  [0x00000c00 - 0x00000cff] io

PCI: 00:11.2 20 *  [0x00001000 - 0x0000101f] io

PCI: 00:11.3 20 *  [0x00001020 - 0x0000103f] io

PCI: 00:11.1 20 *  [0x00001040 - 0x0000104f] io

PCI: 00:11.5 14 *  [0x00001050 - 0x00001053] io

PCI: 00:11.5 18 *  [0x00001060 - 0x00001063] io

Root Device compute_allocate_io: base: 00001064 size: 00000c64 align: 8 
gran: 0

done

Root Device compute_allocate_mem: base: 00000000 size: 00000000 align: 0 
gran: 0



Root Device read_resources bus 0 link: 0

Root Device read_resources bus 0 link: 0 done

PCI: 00:12.0 14 *  [0x00000000 - 0x000000ff] mem

Root Device compute_allocate_mem: base: 00000100 size: 00000100 align: 8 
gran: 0

 done

Done

Setting resources...

Root Device compute_allocate_io: base: 00001000 size: 00000c64 align: 8 
gran: 0

Root Device read_resources bus 0 link: 0

Root Device read_resources bus 0 link: 0 done

PCI: 00:11.5 10 *  [0x00001000 - 0x000010ff] io

PCI: 00:11.6 10 *  [0x00001400 - 0x000014ff] io

PCI: 00:12.0 10 *  [0x00001800 - 0x000018ff] io

PCI: 00:11.2 20 *  [0x00001c00 - 0x00001c1f] io

PCI: 00:11.3 20 *  [0x00001c20 - 0x00001c3f] io

PCI: 00:11.1 20 *  [0x00001c40 - 0x00001c4f] io

PCI: 00:11.5 14 *  [0x00001c50 - 0x00001c53] io

PCI: 00:11.5 18 *  [0x00001c60 - 0x00001c63] io

Root Device compute_allocate_io: base: 00001c64 size: 00000c64 align: 8 
gran: 0

done

Root Device compute_allocate_mem: base: febfff00 size: 00000100 align: 8 
gran: 0



Root Device read_resources bus 0 link: 0

Root Device read_resources bus 0 link: 0 done

PCI: 00:12.0 14 *  [0xfec00000 - 0xfec000ff] mem

Root Device compute_allocate_mem: base: fec00100 size: 00000200 align: 8 
gran: 0

 done

Root Device assign_resources, bus 0 link: 0

I would set ram size to 0x20000 Kbytes

PCI_DOMAIN: 0000 assign_resources, bus 0 link: 0

PCI: 00:11.1 20 <- [0x0000001c40 - 0x0000001c4f] io

PCI: 00:11.2 20 <- [0x0000001c00 - 0x0000001c1f] io

PCI: 00:11.3 20 <- [0x0000001c20 - 0x0000001c3f] io

PCI: 00:11.5 10 <- [0x0000001000 - 0x00000010ff] io

PCI: 00:11.5 14 <- [0x0000001c50 - 0x0000001c53] io

PCI: 00:11.5 18 <- [0x0000001c60 - 0x0000001c63] io

PCI: 00:11.6 10 <- [0x0000001400 - 0x00000014ff] io

PCI: 00:12.0 10 <- [0x0000001800 - 0x00000018ff] io

PCI: 00:12.0 14 <- [0x00fec00000 - 0x00fec000ff] mem

PCI_DOMAIN: 0000 assign_resources, bus 0 link: 0

Root Device assign_resources, bus 0 link: 0

Done

done.

Enabling resourcess...

PCI: 00:00.0 cmd <- 146

PCI: 00:01.0 bridge ctrl <- 0003

PCI: 00:01.0 cmd <- 147

PCI: 00:11.0 cmd <- 1c7

PCI: 00:11.1 cmd <- 1c1

PCI: 00:11.2 cmd <- 141

PCI: 00:11.3 cmd <- 141

PCI: 00:11.4 cmd <- 140

PCI: 00:11.5 cmd <- 141

PCI: 00:11.6 cmd <- 141

PCI: 00:12.0 cmd <- 1c3

done.

Initializing devices...

Root Device init

PCI: 00:00.0 init

VT8601 random fixup ...

Devices initialized

Copying IRQ routing tables to 0xf0000...done.

Verifing copy of IRQ routing tables at 0xf0000...done

Checking IRQ routing table consistency...

/home/belliveaul/bios/src/arch/i386/boot/pirq_routing.c:    
28:check_pirq_routin

g_table() - irq_routing_table located at: 0x000f0000

done.

Wrote linuxbios table at: 00000500 - 00000b04  checksum ccba



Welcome to elfboot, the open sourced starter.

January 2002, Eric Biederman.

Version 1.3



    23:stream_init() - rom_stream: 0xfffc0000 - 0xfffcffff

Found ELF candiate at offset 0

header_offset is 0

Try to load at offset 0x0

malloc Enter, size 32, free_mem_ptr 000173d4

malloc 0x000173d4

New segment addr 0x100000 size 0x20e00 offset 0xc0 filesize 0x6e68

(cleaned up) New segment addr 0x100000 size 0x20e00 offset 0xc0 filesize 
0x6e68

lb: [0x0000000000004000, 0x000000000001a000)

malloc Enter, size 32, free_mem_ptr 000173f4

malloc 0x000173f4

New segment addr 0x120e00 size 0x48 offset 0x6f40 filesize 0x48

(cleaned up) New segment addr 0x120e00 size 0x48 offset 0x6f40 filesize 0x48

lb: [0x0000000000004000, 0x000000000001a000)

Dropping non PT_LOAD segment

Dropping non PT_LOAD segment

Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000020e00 
filesz: 0x00

00000000006e68

[ 0x0000000000100000, 0000000000106e68, 0x0000000000120e00) <- 
00000000000000c0

Clearing Segment: addr: 0x0000000000106e68 memsz: 0x0000000000019f98

Loading Segment: addr: 0x0000000000120e00 memsz: 0x0000000000000048 
filesz: 0x00

00000000000048

[ 0x0000000000120e00, 0000000000120e48, 0x0000000000120e48) <- 
0000000000006f40

Loaded segments

verified segments

closed down stream

Jumping to boot code at 0x104cac

entry    = 0x00104cac

lb_start = 0x00004000

lb_size  = 0x00016000

adjust   = 0x07fe6000

buffer   = 0x07fd4000

     elf_boot_notes = 0x0000f980

adjusted_boot_notes = 0x07ff5980

FILO version 0.4.2 (root at neon) Sat Dec  4 09:43:58 AST 2004

collect_linuxbios_info: Searching for LinuxBIOS tables...

find_lb_table: Found canidate at: 00000500

find_lb_table: header checksum o.k.

find_lb_table: table checksum o.k.

find_lb_table: record count o.k.

collect_linuxbios_info: Found LinuxBIOS table at: 00000500

convert_memmap: 0x00000000000000 0x00000000000b70 16

convert_memmap: 0x00000000000b70 0x000000000ef490 1

convert_memmap: 0x000000000f0000 0x00000000000400 16

convert_memmap: 0x000000000f0400 0x00000007f0fc00 1

pci_init: Scanning PCI: found 10 devices

pci_init: 00:00.0 1106:0601 0600 00

pci_init: 00:01.0 1106:8601 0604 00

pci_init: 00:11.0 1106:8231 0601 00

pci_init: 00:11.1 1106:0571 0101 8f

pci_init: 00:11.2 1106:3038 0c03 00

pci_init: 00:11.3 1106:3038 0c03 00

pci_init: 00:11.4 1106:8235 0000 00

pci_init: 00:11.5 1106:3058 0401 00

pci_init: 00:11.6 1106:3068 0780 00

pci_init: 00:12.0 1106:3065 0200 00

Press <Enter> for default boot, or <Esc> for boot prompt... timed out

boot: hda1:/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200

find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8f

find_ide_controller: primary channel: native PCI mode

find_ide_controller: cmd_base=0x0 ctrl_base=0x0

Detected floating bus

No drive detected on IDE channel 0


-------------------------------------------------------



Ronald G. Minnich wrote:

>On Sat, 4 Dec 2004, Luc Belliveau wrote:
>
>  
>
>>Same thing, with one small difference... I turned debugging on and this is
>>what I get :
>>    
>>
>
>hmm. 
>  
>
>>find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8f
>>find_ide_controller: primary channel: native PCI mode
>>find_ide_controller: cmd_base=0x0 ctrl_base=0x0
>>    
>>
>
>well that is odd, actually. 
>
>make this one change:
>  
>
>>># K8-based boards may need it
>>>PCI_BRUTE_SCAN = 1
>>>PCI_BRUTE_SCAN_LIMIT = 2
>>>      
>>>
>
>  
>
>>>PCI_BRUTE_SCAN_START = 1
>>>      
>>>
>
>
>  
>
>>>PCI_BRUTE_SCAN_START = 1
>>>      
>>>
>                           0
>
>ron
>  
>



From rminnich at lanl.gov  Sat Dec  4 07:11:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Dec  4 07:11:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B1F235.1050301@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
 <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
 <41B0DC84.1040105@bigdata.nb.ca> <Pine.LNX.4.58.0412031555460.31548@linux.site>
 <41B124AC.5000301@bigdata.nb.ca> <Pine.LNX.4.58.0412040904550.1344@linux.site>
 <41B1E740.5030505@bigdata.nb.ca> <Pine.LNX.4.58.0412040937030.1344@linux.site>
 <41B1F235.1050301@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412041027190.1344@linux.site>

ok, just double check that your ide is right, and can somebody send me an 
lspci for these boards? I don't have one handy. 

Finally, I do know that native ide mode was always buggy on this part. Is 
that a possibility here?

ron



From luc at bigdata.nb.ca  Sat Dec  4 07:15:01 2004
From: luc at bigdata.nb.ca (Luc Belliveau)
Date: Sat Dec  4 07:15:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412041027190.1344@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site> <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca> <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site> <41B0DC84.1040105@bigdata.nb.ca> <Pine.LNX.4.58.0412031555460.31548@linux.site> <41B124AC.5000301@bigdata.nb.ca> <Pine.LNX.4.58.0412040904550.1344@linux.site> <41B1E740.5030505@bigdata.nb.ca> <Pine.LNX.4.58.0412040937030.1344@linux.site> <41B1F235.1050301@bigdata.nb.ca> <Pine.LNX.4.58.0412041027190.1344@linux.site>
Message-ID: <41B1F488.4020300@bigdata.nb.ca>

Here is the output from lspci on my board

*00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] 
(rev 05)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] 
(rev 10)
00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 1e)
00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 1e)
00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 
AC97 Audio Controller (rev 40)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] 
(rev 51)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 
(rev 6a)
*
What did you want me to double check about my IDE exactly?  I haven't 
changed any of the defaults in LinuxBIOS with the exception of the 
CONFIG_CONSOLE_SERIAL8250 and the loglevels.

Luc

Ronald G. Minnich wrote:

>ok, just double check that your ide is right, and can somebody send me an 
>lspci for these boards? I don't have one handy. 
>
>Finally, I do know that native ide mode was always buggy on this part. Is 
>that a possibility here?
>
>ron
>
>  
>



From zhushisongzhu at yahoo.com  Sat Dec  4 07:23:01 2004
From: zhushisongzhu at yahoo.com (zhu shi song)
Date: Sat Dec  4 07:23:01 2004
Subject: about MAINBOARD_POWER_ON_AFTER_POWER_FAIL
In-Reply-To: <Pine.LNX.4.58.0412040908510.1344@linux.site>
Message-ID: <20041204173948.71961.qmail@web13203.mail.yahoo.com>

The factory bios of my MB has "power fail restore"
option and I set it to enable.  The MB has the same
problem as linuxbios does.  When linux is booting
without console prompt, unplug power supply and plug
again, MB will boot automatically without press power
button.  But if linux has console prompt and I can
login the system, at this time I unplug power supply
and plug again, MB will not boot. I must press the
power button.  It seems that linux has done something
to disable the function.  
tks
zhu

--- "Ronald G. Minnich" <rminnich at lanl.gov> wrote:

> you can take a look at that the arima hdama code
> does for this. It is all 
> motherboard-specific, I guess ... not sure in all
> cases.
> 
> ron
> 
> 



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail


From rminnich at lanl.gov  Sat Dec  4 07:34:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Dec  4 07:34:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B1F488.4020300@bigdata.nb.ca>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com> <41B0BFDC.2060505@bigdata.nb.ca>
 <41B0D869.7070001@bigdata.nb.ca> <Pine.LNX.4.58.0412031422500.31144@linux.site>
 <41B0DC84.1040105@bigdata.nb.ca> <Pine.LNX.4.58.0412031555460.31548@linux.site>
 <41B124AC.5000301@bigdata.nb.ca> <Pine.LNX.4.58.0412040904550.1344@linux.site>
 <41B1E740.5030505@bigdata.nb.ca> <Pine.LNX.4.58.0412040937030.1344@linux.site>
 <41B1F235.1050301@bigdata.nb.ca> <Pine.LNX.4.58.0412041027190.1344@linux.site>
 <41B1F488.4020300@bigdata.nb.ca>
Message-ID: <Pine.LNX.4.58.0412041049220.1344@linux.site>


On Sat, 4 Dec 2004, Luc Belliveau wrote:

> 
> Here is the output from lspci on my board
> 
> *00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10)
> 00:11.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> 00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 1e)
> 00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 1e)
> 00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
> 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97
> Audio Controller (rev 40)
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51)
> 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a)
> *
> What did you want me to double check about my IDE exactly?  I haven't changed
> any of the defaults in LinuxBIOS with the exception of the
> CONFIG_CONSOLE_SERIAL8250 and the loglevels.

I don't know how to set IDE back into non-native PCI and I'm not sure what 
Mark has done. FILO is finding the IDE controller just fine. We need to 
start looking at settings on the 8231 to make sure the IDE is in 
non-native mode. I'm on travel and can't help until next week but I hope 
Mark can.

ron


From adam at cfar.umd.edu  Sat Dec  4 08:30:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Sat Dec  4 08:30:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
Message-ID: <Pine.BSF.4.61.0412041359300.86155@www.missl.cs.umd.edu>

with all this talk on the list about epia.. does anyone knwo off hand how 
to change this "wait 4 seconds reboot" to instantenous reboot when I press 
the on button?

sh-2.05b# cat /proc/cpuinfo
vendor_id       : CentaurHauls
model name      : VIA Samuel 2

sh-2.05b# /sbin/lspci
pcilib: Cannot open /sys/bus/pci/devices
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia]
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] 
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8)
0000:00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1e)
0000:00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1e)
0000:00:11.4 Non-VGA unclassified device: VIA Technologies, Inc. VT8235 ACPI (r)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 )
0000:00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 M)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev)


From rminnich at lanl.gov  Sat Dec  4 08:35:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Dec  4 08:35:00 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.BSF.4.61.0412041359300.86155@www.missl.cs.umd.edu>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
 <Pine.BSF.4.61.0412041359300.86155@www.missl.cs.umd.edu>
Message-ID: <Pine.LNX.4.58.0412041150140.1344@linux.site>


On Sat, 4 Dec 2004, Adam Sulmicki wrote:

> 
> with all this talk on the list about epia.. does anyone knwo off hand how to
> change this "wait 4 seconds reboot" to instantenous reboot when I press the on
> button?

you mean machine is on, and you want it to cycle real fast? 

we need to figure out how to trap the power button even to linux. Normally 
it is caught by the fuctory bios, but we don't have one in there. It makes 
most sense to have the OS catch that sort of thing anyway.

ron


From yhlu at tyan.com  Sat Dec  4 09:07:01 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sat Dec  4 09:07:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <41B1F488.4020300@bigdata.nb.ca>
Message-ID: <200412041406.iB4E63L02959@nwn.definitive.org>

You can enable debug in filo. Also add some printf in ide_disk.c

YH

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Luc Belliveau
Sent: Saturday, December 04, 2004 9:32 AM
To: Ronald G. Minnich
Cc: linuxbios at clustermatic.org
Subject: Re: epia problem/Epia status update


Here is the output from lspci on my board

*00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] 
(rev 05)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] 
(rev 10)
00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 1e)
00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 1e)
00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 
AC97 Audio Controller (rev 40)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] 
(rev 51)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 
(rev 6a)
*
What did you want me to double check about my IDE exactly?  I haven't 
changed any of the defaults in LinuxBIOS with the exception of the 
CONFIG_CONSOLE_SERIAL8250 and the loglevels.

Luc

Ronald G. Minnich wrote:

>ok, just double check that your ide is right, and can somebody send me an 
>lspci for these boards? I don't have one handy. 
>
>Finally, I do know that native ide mode was always buggy on this part. Is 
>that a possibility here?
>
>ron
>
>  
>

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From yhlu at tyan.com  Sat Dec  4 09:07:12 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sat Dec  4 09:07:12 2004
Subject: about MAINBOARD_POWER_ON_AFTER_POWER_FAIL
In-Reply-To: <20041204173948.71961.qmail@web13203.mail.yahoo.com>
Message-ID: <200412041406.iB4E63L02958@nwn.definitive.org>

Are you going to post the patch? Then we can check that for you.

YH

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of zhu shi song
Sent: Saturday, December 04, 2004 9:40 AM
To: Ronald G. Minnich
Cc: linuxbios at clustermatic.org
Subject: Re: about MAINBOARD_POWER_ON_AFTER_POWER_FAIL

The factory bios of my MB has "power fail restore"
option and I set it to enable.  The MB has the same
problem as linuxbios does.  When linux is booting
without console prompt, unplug power supply and plug
again, MB will boot automatically without press power
button.  But if linux has console prompt and I can
login the system, at this time I unplug power supply
and plug again, MB will not boot. I must press the
power button.  It seems that linux has done something
to disable the function.  
tks
zhu

--- "Ronald G. Minnich" <rminnich at lanl.gov> wrote:

> you can take a look at that the arima hdama code
> does for this. It is all 
> motherboard-specific, I guess ... not sure in all
> cases.
> 
> ron
> 
> 



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From ollie at lanl.gov  Sat Dec  4 10:34:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Sat Dec  4 10:34:00 2004
Subject: Allocating Resource for Legacy VGA Buffer
In-Reply-To: <m33bymkdmk.fsf@maxwell.lnxi.com>
References: <1102008601.25042.7.camel@exponential.lanl.gov>
	 <m33bymkdmk.fsf@maxwell.lnxi.com>
Message-ID: <1102193454.3059.5.camel@logarithm.lanl.gov>

On Fri, 2004-12-03 at 19:20, Eric W. Biederman wrote:
> Li-Ta Lo <ollie at lanl.gov> writes:
> 
> > Eric,
> > 
> > I tried to allocate a MEM resource for legacy VGA framebuffer (0xA0000 -
> > 0xBFFFF) on AMDK8 NB Fun 1. I find a new mem_pair and assigned base 
> > and size of the resource as the code show in the bottom. But at the run 
> > time the resrouce allocation code still try to allocate that resource
> > to  0xA0000 to 0x002ffffff. Why it does not care about the 
> > resource->size field nor the FIXED flag ?
> 
> The resource allocator should and it does in other cases.
> 
> Hmm.  You don't even allocate this resource in read_resources
> so the resource allocator might should not even see it.  
> 
> The IORESOURCE_PREFETCH is not correct for that area though.
> Setting up write-combining MSRs would be a very bad thing
> to have happen.  Which is what IORESOURCE_PREFETCH implies is
> legal.
> 

The problem is I have no way to know which node/link the
VGA connects to at the read_resources time. So I can not
return a correct resource which these info embedded.

I tried to extend the pci_read_resources() to include the
memory resource 0xa0000-0xbfffff as the read_resources()
method of the VGA device. It does not work neither. The
read_resources() does return one more resource but the
bridges ignore it. Did I miss something ?

Ollie




From ebiederman at lnxi.com  Sat Dec  4 13:55:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Sat Dec  4 13:55:00 2004
Subject: K8 D0 support
In-Reply-To: <3174569B9743D511922F00A0C943142306BA371B@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA371B@TYANWEB>
Message-ID: <m3pt1phadl.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> Opteron Rev D0 support done.
> 
> So I need to wait for AMD put the updated Bios porting guide including
> Opteron Rev D0 info. Only after that, I can commit the patch?
> Or ask the AMD to review the code?

Essentially.

It all depends on your relationship.  But as a general rule if you have
knowledge under an NDA that is not public knowledge it is impolite
to publish it with out the vendors approval.

This is courtesy, and in the case of AMD not a large imposition, as we
know the information will be publicly available in time.  Having the work done
sooner and published would not hurt my feelings though.

Eric


From brewskie at brewskie.org  Sat Dec  4 16:20:01 2004
From: brewskie at brewskie.org (Brian Abreu)
Date: Sat Dec  4 16:20:01 2004
Subject: EPIA-MII v2 Config
Message-ID: <72540010-4666-11D9-91DC-000A957E8B7E@brewskie.org>

Hello,

	I am having trouble getting freebios2 to build for a EPIA-MII board.  
I cannot find any information anywhere on how to build the v2 bios for 
EPIA-M based boards.  Can someone please explain how you do this?

Thanx,

Brian Abreu



From yhlu at tyan.com  Sun Dec  5 11:32:00 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sun Dec  5 11:32:00 2004
Subject: K8 D0 support
In-Reply-To: <m3pt1phadl.fsf@maxwell.lnxi.com>
Message-ID: <200412051631.iB5GV6L14095@nwn.definitive.org>

The D0 is released last week. And Normal BIOS support it already.

Thanks for your great job in raminit.c of K8 and others, and I add several
lines to reflect the new mapping of memory bank.

Regards

Yinghai Lu

-----Original Message-----
From: Eric W. Biederman [mailto:eric at lnxi.com] On Behalf Of Eric W.
Biederman
Sent: Saturday, December 04, 2004 4:12 PM
To: YhLu
Cc: linuxbios at clustermatic.org
Subject: Re: K8 D0 support

YhLu <YhLu at tyan.com> writes:

> Opteron Rev D0 support done.
> 
> So I need to wait for AMD put the updated Bios porting guide including
> Opteron Rev D0 info. Only after that, I can commit the patch?
> Or ask the AMD to review the code?

Essentially.

It all depends on your relationship.  But as a general rule if you have
knowledge under an NDA that is not public knowledge it is impolite
to publish it with out the vendors approval.

This is courtesy, and in the case of AMD not a large imposition, as we
know the information will be publicly available in time.  Having the work
done
sooner and published would not hurt my feelings though.

Eric



From ginlin at nexcom.com.tw  Sun Dec  5 17:50:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Sun Dec  5 17:50:00 2004
Subject: Jump to boot code
In-Reply-To: <Pine.LNX.4.58.0412030830360.28557@linux.site>
Message-ID: <000001c4db48$f8abe680$4f01060a@nexcom.com.tw>

Linuxbios choked when it jumps to the payload. I put a post code in the
beginning of the FILO. It doesn't seem to be executed. 
I think it might have a hard time jumping to the payload entry. Looks
like the payload image was loaded into the memory ok.
Does anyone have similar experience?

gin  	



From mark.wilkinson at 2pmtech.com  Sun Dec  5 23:03:01 2004
From: mark.wilkinson at 2pmtech.com (mark.wilkinson at 2pmtech.com)
Date: Sun Dec  5 23:03:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412041049220.1344@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca>
	<Pine.LNX.4.58.0412030841520.28557@linux.site>
	<20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
	<41B0BFDC.2060505@bigdata.nb.ca> <41B0D869.7070001@bigdata.nb.ca>
	<Pine.LNX.4.58.0412031422500.31144@linux.site>
	<41B0DC84.1040105@bigdata.nb.ca>
	<Pine.LNX.4.58.0412031555460.31548@linux.site>
	<41B124AC.5000301@bigdata.nb.ca>
	<Pine.LNX.4.58.0412040904550.1344@linux.site>
	<41B1E740.5030505@bigdata.nb.ca>
	<Pine.LNX.4.58.0412040937030.1344@linux.site>
	<41B1F235.1050301@bigdata.nb.ca>
	<Pine.LNX.4.58.0412041027190.1344@linux.site>
	<41B1F488.4020300@bigdata.nb.ca>
	<Pine.LNX.4.58.0412041049220.1344@linux.site>
Message-ID: <20041206093846.caw4k44g4sg40owg@2pmtechnologies.com>

Hi Ron, Luc,

Quoting "Ronald G. Minnich" <rminnich at lanl.gov>:

> On Sat, 4 Dec 2004, Luc Belliveau wrote:
>
>>
>> Here is the output from lspci on my board
>>
>> *00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo 
>> ProMedia] (rev 05)
>> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
>> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA 
>> Bridge] (rev 10)
>> 00:11.1 IDE interface: VIA Technologies, Inc.
>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
>> 00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
>> Controller (rev 1e)
>> 00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
>> Controller (rev 1e)
>> 00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
>> 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97
>> Audio Controller (rev 40)
>> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 
>> [Rhine-II] (rev 51)
>> 01:00.0 VGA compatible controller: Trident Microsystems 
>> CyberBlade/i1 (rev 6a)
>> *
>> What did you want me to double check about my IDE exactly?  I 
>> haven't changed
>> any of the defaults in LinuxBIOS with the exception of the
>> CONFIG_CONSOLE_SERIAL8250 and the loglevels.
>
> I don't know how to set IDE back into non-native PCI and I'm not sure what
> Mark has done. FILO is finding the IDE controller just fine. We need to
> start looking at settings on the 8231 to make sure the IDE is in
> non-native mode. I'm on travel and can't help until next week but I hope
> Mark can.

I've not touched the southbridge code that set's up the ide in CVS yet, so it
should be as it was before the big code cleanup. I'm working on seperating it
out in my private copy, so I'm not sure what's happening here.

It sound's like the vt8231_init routine in vt8231.c is either not running, or
that enable_native_ide is set to 1 somewhere, check the latter first.



>
> ron
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios


Mark.

----------------------------------------------------------------
This message was sent using ISPMailNow.com



From rminnich at lanl.gov  Mon Dec  6 07:09:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Dec  6 07:09:01 2004
Subject: Jump to boot code
In-Reply-To: <000001c4db48$f8abe680$4f01060a@nexcom.com.tw>
References: <000001c4db48$f8abe680$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412061025260.7209@linux.site>


On Mon, 6 Dec 2004, Gin wrote:

> Linuxbios choked when it jumps to the payload. I put a post code in the
> beginning of the FILO. It doesn't seem to be executed. 
> I think it might have a hard time jumping to the payload entry. Looks
> like the payload image was loaded into the memory ok.

put printk's into linuxbios itself to hexdump the payload once loaded. 
What is your platform again? I think you still have some memory issues.

ron


From adam at cfar.umd.edu  Mon Dec  6 08:42:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Mon Dec  6 08:42:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.LNX.4.58.0412041150140.1344@linux.site>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
 <Pine.BSF.4.61.0412041359300.86155@www.missl.cs.umd.edu>
 <Pine.LNX.4.58.0412041150140.1344@linux.site>
Message-ID: <Pine.BSF.4.61.0412061413250.98230@www.missl.cs.umd.edu>

>> with all this talk on the list about epia.. does anyone knwo off hand how to
>> change this "wait 4 seconds reboot" to instantenous reboot when I press the on
>> button?
>
> you mean machine is on, and you want it to cycle real fast?

yeah. When I was looking over sis chipset docs I saw that you could setup 
a pci register to toggle this setting between AT-style press-reset and 
ATX-style 4 second delay reset

however, lokoing over vt82c686 docs seems like there's no corresponding 
capability :-(

> we need to figure out how to trap the power button even to linux. Normally
> it is caught by the fuctory bios, but we don't have one in there. It makes
> most sense to have the OS catch that sort of thing anyway.

it was just meant to be quick hack... beats holding button for 4 seconds 
when board crashes, or pulling the power plug..



From rminnich at lanl.gov  Mon Dec  6 12:34:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Dec  6 12:34:01 2004
Subject: epia problem/Epia status update
In-Reply-To: <Pine.BSF.4.61.0412061413250.98230@www.missl.cs.umd.edu>
References: <41AFE91C.9010104@bigdata.nb.ca> <Pine.LNX.4.58.0412030841520.28557@linux.site>
 <20041203163913.637s40gg8c8kk8gs@2pmtechnologies.com>
 <Pine.BSF.4.61.0412041359300.86155@www.missl.cs.umd.edu>
 <Pine.LNX.4.58.0412041150140.1344@linux.site> <Pine.BSF.4.61.0412061413250.98230@www.missl.cs.umd.edu>
Message-ID: <Pine.LNX.4.58.0412061550250.32581@pinkish.lanl.gov>


On Mon, 6 Dec 2004, Adam Sulmicki wrote:

> however, lokoing over vt82c686 docs seems like there's no corresponding
> capability :-(

don't give up. 

If VIA has wired a GPIO pin to power control, then it might still be 
possible. Not sure.

ron


From arun at rassit.com  Tue Dec  7 00:22:01 2004
From: arun at rassit.com (Arun)
Date: Tue Dec  7 00:22:01 2004
Subject: Booting dos from freebios ?
Message-ID: <opsimvwncg1ujopx@192.168.10.2>

Hi all,

We have downloaded freebios 1.0 and we are trying to boot freebios on  
National Geode GX1 processor based system. We were successful enough to 
create a new target in freebios and boot freebios on the board with bios 
output on serial port .
Also we tried to boot linux image minimal from freebios, but we are 
getting error saying error gunzip.

My board freebios log is as follows
--------------------------------------
LinuxBIOS-1.0.0 Mon Dec 6 13:40:00 IST 2004 starting...
Setting up default parameters for memory
Sizing memory
Probing for DIMM0
     Found DIMM0
     Page Size:       00001000
     Component Banks: 4
     Module Banks:    1
     DIMM size:       04000000
Probing for DIMM1
Memory sizing done, MC_BANK_CFG = 0x00701420
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.0.0 Mon Dec 6 13:40:00 IST 2004 booting...
Finding PCI configuration type.
PCI: Using configuration type 1
Scanning PCI bus...PCI: pci_scan_bus for bus 0
PCI: 00:00.0 [1078/0001]
PCI: 00:0f.0 [10ec/8139]
PCI: 00:12.0 [1078/0100]
PCI: 00:12.1 [1078/0101]
PCI: 00:12.2 [1078/0102]
PCI: 00:12.3 [1078/0103]
PCI: 00:12.4 [1078/0104]
PCI: 00:13.0 [0e11/a0f8]
PCI: pci_scan_bus returning with max=00
done
Allocating PCI resources...
ASSIGN RESOURCES, bus 0
PCI: 00:0f.0 10 <- [0x00001000 - 0x000010ff] io
PCI: 00:0f.0 14 <- [0xfebfd000 - 0xfebfd0ff] mem
PCI: 00:12.1 10 <- [0xfebfe000 - 0xfebfe0ff] mem
PCI: 00:12.2 20 <- [0x00001400 - 0x0000147f] io
PCI: 00:12.3 10 <- [0xfebff000 - 0xfebff07f] mem
PCI: 00:12.4 10 <- [0xfebfb000 - 0xfebfbfff] mem
PCI: 00:13.0 10 <- [0xfebfc000 - 0xfebfcfff] mem
ASSIGNED RESOURCES, bus 0
Allocating VGA resource
done.
Enabling PCI resourcess...PCI: 00:00.0 cmd <- 07
PCI: 00:0f.0 cmd <- 03
PCI: 00:12.0 cmd <- 0f
PCI: 00:12.1 cmd <- 02
PCI: 00:12.2 cmd <- 01
PCI: 00:12.3 cmd <- 02
PCI: 00:12.4 cmd <- 03
PCI: 00:13.0 cmd <- 02
done.
Initializing PCI devices...
PCI devices initialized
DIMM0: 64MB (4kB page size, 4 component banks, 1 module banks)
DIMM1: empty
Reserving 4096kB for video memory
BC_DRAM_TOP = 0x03bfffff
MC_GBASE_ADD = 0x00000078
totalram: 60M
Initializing CPU #0
Enabling cache...done.

Max cpuid index    : 2
Vendor ID          : Geode by NSC
Processor Type     : 0x00
Processor Family   : 0x05
Processor Model    : 0x04
Processor Mask     : 0x00
Processor Stepping : 0x00
Feature flags      : 0x00808131

Cache/TLB descriptor values: 1 reads required
Desc 0x70 : UNKNOWN
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null
Desc 0x80 : UNKNOWN
Desc 0x00 : null
Desc 0x00 : null
Desc 0x00 : null


done.
CPU #0 Initialized
Enable FLASH
Set F0/0x52 to 0xee
cs5530: Enabling Primary IDE Controller
cs5530: Enabling Secondary IDE Controller
Set F0/0x5b to |= 1 << 5(0x38)
Final southbridge fixup
F0/5c: 0x0000
cs5530: PCI INTA=9, INTB=10, INTC=11, INTD=15
F0/5c: 0xfba9
4d0: 0x00
4d1: 0x00
4d0: 0x00
4d1: 0x8e
F0/5b = 0x38
cs5530: Enabling Primary IDE Controller
F0/5b = 0x38
cs5530: USB is on INTA, IRQ 9
Final mainboard fixup
Wrote linuxbios table at: 00000500 - 00000668  checksum 7862
Jumping to linuxbiosmain()...

Welcome to start32, the open sourced starter.
This space will eventually hold more diagnostic information.

January 2000, James Hendricks, Dale Webster, and Ron Minnich.
Version 0.1

     34:init_bytes() - zkernel_start:0xc0000200  zkernel_mask:0x0000ffff
Gunzip setup
gunzip_setup
output data is 0x00100000
Gunzipping boot code
bad gzip magic numbers

--------------------------------------
Now My board has a DOC M-Sys 16MB, which consists of freedos in it's 
primary partition.
Can we boot freedos from the freebios ?

Bye
R Arun Kumar



From talbotx at comcast.net  Tue Dec  7 05:12:01 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Tue Dec  7 05:12:01 2004
Subject: VIA Northbridge's vt8601 and vt8604
Message-ID: <004301c4dc71$6d5e0570$9901a8c0@newflame>

Can any one give the the difference between the VIA Northbridge's vt8601 and vt8604. Will the code from the vt8601 be able to boot the vt8604?
-Adam Talbot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041207/a25fdbc8/attachment.html>

From adam at cfar.umd.edu  Tue Dec  7 07:43:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Tue Dec  7 07:43:01 2004
Subject: Booting dos from freebios ?
In-Reply-To: <opsimvwncg1ujopx@192.168.10.2>
References: <opsimvwncg1ujopx@192.168.10.2>
Message-ID: <Pine.BSF.4.61.0412071314550.7482@www.missl.cs.umd.edu>

On Tue, 7 Dec 2004, Arun wrote:

> Can we boot freedos from the freebios ?

if you use ADLO, then yeah.. somewhat. I think I had limited success 
booting Win95 (read : got as far as that flying win95 flag). I think the 
IDE driver in ADLO needs most of the work.. (or at least that was the most 
obvious problem).



From ebiederman at lnxi.com  Tue Dec  7 18:57:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Tue Dec  7 18:57:01 2004
Subject: K8 D0 support
In-Reply-To: <20041205214835.BAD1DD037358@spam.llix.net>
References: <20041205214835.BAD1DD037358@spam.llix.net>
Message-ID: <m3pt1lwevs.fsf@maxwell.lnxi.com>

"Yinghai Lu" <yhlu at tyan.com> writes:

> The D0 is released last week. And Normal BIOS support it already.
> 
> Thanks for your great job in raminit.c of K8 and others, and I add several
> lines to reflect the new mapping of memory bank.

Cool.

I am confused about what the current situation is.  All I know for
certain is that AMD has not updated their public documentation yet.  So it does
not appear as if these processors have been released to the public.

Long term I wish we had a better way to handle development before the official
product launch.

Eric


From talbotx at comcast.net  Tue Dec  7 19:50:00 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Tue Dec  7 19:50:00 2004
Subject: AWWWW Crap!
Message-ID: <001c01c4dcec$2a32c760$9901a8c0@newflame>

OK, I have a bios chip that my flash ROM programmer cant program... The chip is a Amic A290021TL-70.  OK, I would like to buy a new chip from a different manufacture. What do I need to keep in mind when I buy a replacement chip?
Here is the data sheet from the off brand chip.
http://www.amictechnology.com/pdf/A29002.pdf
-Adam Talbot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041207/7f47623f/attachment.html>

From YhLu at tyan.com  Wed Dec  8 07:44:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec  8 07:44:00 2004
Subject: K8 D0 support
Message-ID: <3174569B9743D511922F00A0C943142306BA3898@TYANWEB>

>Long term I wish we had a better way to handle development before the
official
>product launch.

I think if I can keep pace with normal bios development, I can get updated
detail info from vendor and our BIOS engineers. Otherwise they may forget
some detail info and also some vendors may fail to update their datasheet.
Then it may take some time to make Linuxbios work.

YH


From rminnich at lanl.gov  Wed Dec  8 19:14:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Dec  8 19:14:01 2004
Subject: AWWWW Crap!
In-Reply-To: <001c01c4dcec$2a32c760$9901a8c0@newflame>
References: <001c01c4dcec$2a32c760$9901a8c0@newflame>
Message-ID: <Pine.LNX.4.58.0412082231270.14074@linux.site>

send me the output from flash_rom first, to make sure you are enabling 
flash write.

ron



From talbotx at comcast.net  Wed Dec  8 20:06:01 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Wed Dec  8 20:06:01 2004
Subject: AWWWW Crap!
References: <001c01c4dcec$2a32c760$9901a8c0@newflame> <Pine.LNX.4.58.0412082231270.14074@linux.site>
Message-ID: <001801c4ddb7$9daab2e0$9901a8c0@newflame>

No, I have a hardware programmer...
I am/was trying to find out if I could use a different chip on my
motherboard.  My programmer does not support the Amic bios chip that was on
the mother board.  I found a sst39sf020, its the same speed 70ns and took a
flash and works great. By any chance do you no what spec's I need to keep in
mind when replacing a bios chip??  I no better then to mix 5v and 3v chips,
what else is there??
-Adam Talbot

----- Original Message ----- 
From: "Ronald G. Minnich" <rminnich at lanl.gov>
To: "Adam Talbot" <talbotx at comcast.net>
Cc: <Linuxbios at clustermatic.org>
Sent: Wednesday, December 08, 2004 9:31 PM
Subject: Re: AWWWW Crap!


> send me the output from flash_rom first, to make sure you are enabling
> flash write.
>
> ron
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>




From ginlin at nexcom.com.tw  Wed Dec  8 23:03:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec  8 23:03:01 2004
Subject: Linux kernel hangs
Message-ID: <001501c4ddd0$5c607d60$4f01060a@nexcom.com.tw>

Linuxbios writes to the beginning of the Memory for MP tables. Shouldn't
those addresses be interrupt vector table? It doesn't look it contains
any pointers to an interrupt handler. Who is the table for? Will Linux
kernel reference it?
Linuxbios successfully loads the payload FILO which brings up Linux
kernel. But the kernel hangs while waiting for a timer interrupt. See
below. I guess the interrupt table is not correct.
==========================================================
Linux version 2.4.20-8 (bhcompile at porky.devel.redhat.com) (gcc version
3.2.2 200
30222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000c88 - 00000000000a0000 (usable)
 BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
128MB HIGHMEM available.
896MB LOWMEM available.
hm, page 00000000 reserved twice.
On node 0 totalpages: 262144
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 32768 pages.
Kernel command line: ro root=/dev/hda2 console=ttyS0,57600
Initializing CPU#0
Detected 1597.358 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop...
 
====================================================================
 
 The MP table is specific to Tyan/s2735 not my board. I should change
it. We use intel E7501/ICHs-3. But s2735 is ICH5. Don't know if it
matters. 
 
 
 
gin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041208/79dca075/attachment.html>

From stepan at openbios.org  Wed Dec  8 23:56:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed Dec  8 23:56:01 2004
Subject: Linux kernel hangs
In-Reply-To: <001501c4ddd0$5c607d60$4f01060a@nexcom.com.tw>
References: <001501c4ddd0$5c607d60$4f01060a@nexcom.com.tw>
Message-ID: <20041209101312.GA13108@openbios.org>

* Gin <ginlin at nexcom.com.tw> [041209 10:20]:
> Linuxbios writes to the beginning of the Memory for MP tables. Shouldn't
> those addresses be interrupt vector table? It doesn't look it contains
> any pointers to an interrupt handler. Who is the table for? Will Linux
> kernel reference it?

Linux uses the MP-Table for assigning interrupts to devices if it is
there. It is basically a variant of describing a device tree to the
system. It has nothing to do with the IVT, not directly at least.
The IVT is set up by Linux. (And by LinuxBIOS for exception handling and
gdb stub support)

> Linuxbios successfully loads the payload FILO which brings up Linux
> kernel. But the kernel hangs while waiting for a timer interrupt. See
> below. I guess the interrupt table is not correct.
> ==========================================================
> Initializing CPU#0
> Detected 1597.358 MHz processor.
> Console: colour dummy device 80x25
> Calibrating delay loop...
 
Your interrupts are not set up correctly. 

Stefan
 


From ginlin at nexcom.com.tw  Thu Dec  9 02:21:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Thu Dec  9 02:21:01 2004
Subject: keyboard jammed
In-Reply-To: <001501c4ddd0$5c607d60$4f01060a@nexcom.com.tw>
Message-ID: <001c01c4ddeb$e5faf9e0$4f01060a@nexcom.com.tw>

Forget about the previous email. Actually I solved the problem of
Calibrating delay loop. The problem is that I used the device list in
static.c as my onboard devices and it was missing apic cluster. 
 
In the board specific config file(under src/...), I noticed there is a
tree-like device list. See below. Should I make it exactly the same as
my board? Would it stop me from booting into linux kernel? Now I am
getting another error. It prints out keyboard controller jammed..
:
:gin
:=======================================================
# sample config for tyan/s2735
chip northbridge/intel/e7501
        device pci_domain 0 on
                device pci 0.0 on end
                device pci 0.1 on end
                device pci 2.0 on
                        chip southbridge/intel/i82870
                                device pci 1c.0 on end
                                device pci 1d.0 on end
                                device pci 1e.0 on end
                                device pci 1f.0 on end
                        end
                end
                device pci 6.0 on end
                chip southbridge/intel/i82801er
                        device pci 1d.0 on end
                        device pci 1d.1 on end
                        device pci 1d.2 on end
                        device pci 1d.3 on end
                        device pci 1d.7 on end
                        device pci 1e.0 on end
                        device pci 1f.0 on
                                # device pci 8.0 end
                                chip superio/winbond/w83627hf
                                        device pnp 2e.0 on     #  Floppy
                                                 io 0x60 = 0x3f0
                                                irq 0x70 = 6
                                                drq 0x74 = 2
                                        end
                                        device pnp 2e.1 off     #
Parallel Port
                                                 io 0x60 = 0x378
                                                irq 0x70 = 7
                                        end
                                        device pnp 2e.2 on      #  Com1
:
:
:
===================================================================
 
 Linux version 2.4.20-8 (bhcompile at porky.devel.redhat.com) (gcc version
3.2.2 200
30222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000c88 - 00000000000a0000 (usable)
 BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
128MB HIGHMEM available.
896MB LOWMEM available.
hm, page 00000000 reserved twice.
On node 0 totalpages: 262144
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 32768 pages.
Kernel command line: ro root=/dev/hda2 console=ttyS0,57600
Initializing CPU#0
Detected 1597.322 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 3185.04 BogoMIPS
Memory: 1027480k/1048576k available (1347k kernel code, 17508k reserved,
999k da
ta, 132k init, 131072k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Xeon(TM) CPU 1.60GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch at atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
PCI: Unable to handle 64-bit address space for
PCI: Unable to handle 64-bit address space for
Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge
PCI: Using IRQ router PIIX [8086/2480] at 00:1f.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS not found.
Starting kswapd
allocated 32 pages and 32 bhs reserved for the highmem bounces
VFS: Disk quotas vdquot_6.5.1
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041209/eef506d6/attachment.html>

From bari at onelabs.com  Thu Dec  9 04:14:00 2004
From: bari at onelabs.com (Bari Ari)
Date: Thu Dec  9 04:14:00 2004
Subject: AWWWW Crap!
In-Reply-To: <001801c4ddb7$9daab2e0$9901a8c0@newflame>
References: <001c01c4dcec$2a32c760$9901a8c0@newflame> <Pine.LNX.4.58.0412082231270.14074@linux.site> <001801c4ddb7$9daab2e0$9901a8c0@newflame>
Message-ID: <41B86236.3080609@onelabs.com>

Adam Talbot wrote:

  I found a sst39sf020, its the same speed 70ns and took a
> flash and works great. By any chance do you no what spec's I need to keep in
> mind when replacing a bios chip??  I no better then to mix 5v and 3v chips,
> what else is there??

How much time do you have? Take a look at a few flash vendors product 
sites for more info:

http://www.amd.com/us-en/FlashMemory/ProductInformation/0,,37_1447,00.html

http://developer.intel.com/design/flash/index.htm?iid=embnav1+flash&

http://www.sst.com/products/

http://sharp-world.com/products/device/lineup/ic/flashmemory/index.html

-Bari



From etorres at tux.uis.edu.co  Thu Dec  9 05:30:01 2004
From: etorres at tux.uis.edu.co (Edmanuel Torres)
Date: Thu Dec  9 05:30:01 2004
Subject: How to port PcChips M825G,
Message-ID: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>

Dear LinuxBios people,

first at all, I am new in this staff and I am working in to port a PcChips
M825G mainboard, I have found that the chip set vt8235 is already in the
folder:

/freebios/src/southbrige/via/vt8235

I have been looking for information about how to add the new mainboard and
how to build the files mainbord.c, irq_tables.c and Config, but I have not
found the necessary information about. I wonder is somebody can help me.

Thanks for any help in advance,

Edmanuel


From rminnich at lanl.gov  Thu Dec  9 05:38:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 05:38:00 2004
Subject: AWWWW Crap!
In-Reply-To: <001801c4ddb7$9daab2e0$9901a8c0@newflame>
References: <001c01c4dcec$2a32c760$9901a8c0@newflame>
 <Pine.LNX.4.58.0412082231270.14074@linux.site> <001801c4ddb7$9daab2e0$9901a8c0@newflame>
Message-ID: <Pine.LNX.4.58.0412090855070.15514@linux.site>


On Wed, 8 Dec 2004, Adam Talbot wrote:

> I am/was trying to find out if I could use a different chip on my
> motherboard.  My programmer does not support the Amic bios chip that was on
> the mother board.  I found a sst39sf020, its the same speed 70ns and took a
> flash and works great. By any chance do you no what spec's I need to keep in
> mind when replacing a bios chip??  I no better then to mix 5v and 3v chips,
> what else is there??

28, 39, and esp. 49 are very different, of course. 

speed matters, we have found, which is not surprising.

ron


From rminnich at lanl.gov  Thu Dec  9 05:54:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 05:54:00 2004
Subject: Linux kernel hangs
In-Reply-To: <001501c4ddd0$5c607d60$4f01060a@nexcom.com.tw>
References: <001501c4ddd0$5c607d60$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412090911090.15514@linux.site>


On Thu, 9 Dec 2004, Gin wrote:

> Linuxbios successfully loads the payload FILO which brings up Linux
> kernel. But the kernel hangs while waiting for a timer interrupt. See
> below. I guess the interrupt table is not correct.

yes, it's a bad IRQ or MP table or both.

We have tools to extract them from the standard bios, see the util tree. 

ron


From rminnich at lanl.gov  Thu Dec  9 05:59:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 05:59:00 2004
Subject: keyboard jammed
In-Reply-To: <001c01c4ddeb$e5faf9e0$4f01060a@nexcom.com.tw>
References: <001c01c4ddeb$e5faf9e0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412090914390.15514@linux.site>


On Thu, 9 Dec 2004, Gin wrote:

> Forget about the previous email. Actually I solved the problem of
> Calibrating delay loop. The problem is that I used the device list in
> static.c as my onboard devices and it was missing apic cluster. 

I hope you did not modify static.c?

> In the board specific config file(under src/...), I noticed there is a
> tree-like device list. See below. Should I make it exactly the same as
> my board? 

yes.

ron


From rminnich at lanl.gov  Thu Dec  9 06:04:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 06:04:00 2004
Subject: How to port PcChips M825G, [PMX:#]
In-Reply-To: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>
References: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>
Message-ID: <Pine.LNX.4.58.0412090919360.15514@linux.site>

what northbridge is on that board?

ron



From etorres at tux.uis.edu.co  Thu Dec  9 09:11:01 2004
From: etorres at tux.uis.edu.co (Edmanuel Torres)
Date: Thu Dec  9 09:11:01 2004
Subject: How to port PcChips M825G,
In-Reply-To: <Pine.LNX.4.58.0412090919360.15514@linux.site>
References: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>
    <Pine.LNX.4.58.0412090919360.15514@linux.site>
Message-ID: <1330.192.168.41.45.1102620500.squirrel@tux.uis.edu.co>

Dear Minnich,

Tahnks for your help, the main information is below, I hope it is enough
but if you need something more just ask me, I will be very pleased to sent
it to you.

Processor: AMD Athlon/Duron CPU on board, support 266/200MHz FSB

Chipset

 northbridge: KM266
 southbridge: 8235
 Embedded ProSavage8 3D Graphics w/ 32M share memory
 LAN - VIA VT6103 10/100Mbps Fast Ethernet PHY
 Audio - VIA VT1612A 2-channel audio Codec
 -Compliant with AC97 2.2 specification

System BIOS

 AMI 2Mb Flash ROM
 Supports Plug and Play 1.0A, APM 1.2, Multi Boot, DMI
 Full support for ACPI revision 1.0 specification

Memory

 2 x 184-pin DIMM sockets support two 2.5V DDR SDRAMs (DDR266/200)
 2 x 168-pin DIMM sockets support two 3.3V SDRAMs (PC133/100)
 Maximum memory : 2GB

Best regards,

Edmanuel Torres

> what northbridge is on that board?
>
> ron
>

Edmanuel Torres


From stephen.kimball at bench.com  Thu Dec  9 10:10:01 2004
From: stephen.kimball at bench.com (Steve Kimball)
Date: Thu Dec  9 10:10:01 2004
Subject: buildtarget creates bogus default
Message-ID: <1102623852.13400.30.camel@localhost.localdomain>

How can buildtarget say PAYLOAD_SIZE is 0x-20000?

===> NOTE: Option FALLBACK_SIZE using default value 0x20000
===> NOTE: Option ROM_SECTION_SIZE using default value 0x20000
===> NOTE: Option ROM_SIZE using default value 0x100000
===> NOTE: Option ROM_SECTION_OFFSET using default value 0x0
===> NOTE: Option PAYLOAD_SIZE using default value 0x-20000

Options.lb has
default ROM_IMAGE_SIZE = 131072 (0x20000)

Can someone help me with a high-level view of these sizes?

      _     _      _
     |     |      | ROM Section Size?
     |     |      |
     |     |      --
     |     | Normal
     |     |        _
     |     |       | Payload
     |     |       |
     |     --      --
ROM  |     |       | Rom Section Size?
SIZE |     |       |
     |     |       ---
     |     |  Fallback
     |     |       --
     |     |       | Payload
     |     |       |
     --    --      --

Thanks for the help,
Steve


From rminnich at lanl.gov  Thu Dec  9 12:24:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 12:24:00 2004
Subject: How to port PcChips M825G,
In-Reply-To: <1330.192.168.41.45.1102620500.squirrel@tux.uis.edu.co>
References: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>   
 <Pine.LNX.4.58.0412090919360.15514@linux.site>
 <1330.192.168.41.45.1102620500.squirrel@tux.uis.edu.co>
Message-ID: <Pine.LNX.4.58.0412091541270.16114@linux.site>


On Thu, 9 Dec 2004, Edmanuel Torres wrote:

>  northbridge: KM266

This is via, right? This will be trouble I am afraid. We do not support it 
now.

ron


From ebiederman at lnxi.com  Thu Dec  9 13:53:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Dec  9 13:53:01 2004
Subject: RFC: linuxbios table fix
Message-ID: <m3k6rrrp1e.fsf@maxwell.lnxi.com>

Stefan I believe I have a better fix for the LinuxBIOS table
bug then __attribute__((packed)).

How does this look?

I am still worried about ppc, and big endian architectures in general.
But I don't think we currently have any users there.

I don't know what is the best long term strategy for handling 64bit
numbers but for this instance where we need a better definition for
the current structure simply using a structure with 2 32bit ints
looks like a sane way to go.

Eric

--- checkin/freebios2/src/include/boot/linuxbios_tables.h       Tue Apr 22 13:01:45 2003
+++ linuxbios/freebios2/src/include/boot/linuxbios_tables.h     Thu Dec  9 16:55:18 2004
@@ -57,14 +57,17 @@
 
 #define LB_TAG_MEMORY  0x0001
 
+struct lb_uint64 {
+       uint32_t lo;
+       uint32_t hi;
+};
 struct lb_memory_range {
-       uint64_t start;
-       uint64_t size;
+       struct lb_uint64 start;
+       struct lb_uint64 size;
        uint32_t type;
 #define LB_MEM_RAM       1     /* Memory anyone can use */
 #define LB_MEM_RESERVED  2     /* Don't use this memory region */
 #define LB_MEM_TABLE     16    /* Ram configuration tables are kept in */
-       
 };
 
 struct lb_memory {


From rminnich at lanl.gov  Thu Dec  9 17:01:02 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 17:01:02 2004
Subject: RFC: linuxbios table fix
In-Reply-To: <m3k6rrrp1e.fsf@maxwell.lnxi.com>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>
Message-ID: <Pine.LNX.4.58.0412092017320.16831@linux.site>


On Thu, 9 Dec 2004, Eric W. Biederman wrote:

> I am still worried about ppc, and big endian architectures in general.
> But I don't think we currently have any users there.

we do. I think I'd like to hear Greg Watson's take on this as he is 
working with the PPC 970 guys and this will impact him.

ron


From etorres at tux.uis.edu.co  Thu Dec  9 18:05:01 2004
From: etorres at tux.uis.edu.co (Edmanuel Torres)
Date: Thu Dec  9 18:05:01 2004
Subject: How to port PcChips M825G,
In-Reply-To: <Pine.LNX.4.58.0412091541270.16114@linux.site>
References: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>  
    <Pine.LNX.4.58.0412090919360.15514@linux.site><1330.192.168.41.45.1102620500.squirrel@tux.uis.edu.co>
    <Pine.LNX.4.58.0412091541270.16114@linux.site>
Message-ID: <1838.192.168.41.45.1102652561.squirrel@tux.uis.edu.co>

I have found something about and I think is the same

VT8375 =  KM266
VT8375 [KM266/KL266] Host Bridge

any sugesstion, what I can do about???

Edmanuel


>
>
> On Thu, 9 Dec 2004, Edmanuel Torres wrote:
>
>>  northbridge: KM266
>
> This is via, right? This will be trouble I am afraid. We do not support it
> now.
>
> ron
>


-- 
Edmanuel Torres
MSc. in Physics (Student)
Mobile: 3008207876 - 3112022606
Phone: +57 (7)632 3477 - +57 (7)634 4000 Ext 2402
Fax:   +57 (7)634 6149 - +57 (7)632 3477
Physics and Technology Plasma Group
Physics School,
Universidad Industrial de Santander,
Bucaramanga, Colombia
AA 678


From rminnich at lanl.gov  Thu Dec  9 19:21:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec  9 19:21:01 2004
Subject: How to port PcChips M825G,
In-Reply-To: <1838.192.168.41.45.1102652561.squirrel@tux.uis.edu.co>
References: <1171.192.168.41.45.1102607239.squirrel@tux.uis.edu.co>     
 <Pine.LNX.4.58.0412090919360.15514@linux.site><1330.192.168.41.45.1102620500.squirrel@tux.uis.edu.co>
    <Pine.LNX.4.58.0412091541270.16114@linux.site>
 <1838.192.168.41.45.1102652561.squirrel@tux.uis.edu.co>
Message-ID: <Pine.LNX.4.58.0412092238240.17098@linux.site>


On Thu, 9 Dec 2004, Edmanuel Torres wrote:

> I have found something about and I think is the same
> 
> VT8375 =  KM266
> VT8375 [KM266/KL266] Host Bridge
> 
> any sugesstion, what I can do about???

you're going to have to get those docs.

ron


From ebiederman at lnxi.com  Thu Dec  9 19:32:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Dec  9 19:32:01 2004
Subject: RFC: linuxbios table fix
In-Reply-To: <Pine.LNX.4.58.0412092017320.16831@linux.site>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>
	<Pine.LNX.4.58.0412092017320.16831@linux.site>
Message-ID: <m33byeg0sa.fsf@maxwell.lnxi.com>

"Ronald G. Minnich" <rminnich at lanl.gov> writes:

> On Thu, 9 Dec 2004, Eric W. Biederman wrote:
> 
> > I am still worried about ppc, and big endian architectures in general.
> > But I don't think we currently have any users there.
> 
> we do. I think I'd like to hear Greg Watson's take on this as he is 
> working with the PPC 970 guys and this will impact him.

Ron we have users of the LinxuBIOS table on PPC?  It was my impression that we
did not.

I would be happy to hear what Greg has to say.  If nothing uses this entry
I will be happy to change this.    Otherwise we need to know what the test
program below reports on ppc.

If I can modify the definition to an equivalent one without breaking anything
that is my intention.  We have just enough users on x86 that anything else
involves pain.

cat > test.c << EOF
#include <stdint.h>
#include <stdio.h>
struct lb_memory_range {
	uint64_t start;
	uint64_t size;
	uint32_t type;
};

int main(int argc, char **argv)
{
	printf("sizeof(lb_memory_range): %d\n", sizeof(struct lb_memory_range));
	return 0;
}
EOF

gcc -o ./test ./test.c
./test

Eric


From talbotx at comcast.net  Thu Dec  9 20:19:00 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Thu Dec  9 20:19:00 2004
Subject: need a linux floppy
Message-ID: <008901c4de82$9b9a9350$9901a8c0@newflame>

Any one no of a good Linux distro that fits onto a floppy.  I have a old laptop that I would like to use as a dumb terminal.  So all i need is minicom.
Thx
-Adam Talbot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041209/73d40325/attachment.html>

From talbotx at comcast.net  Thu Dec  9 21:26:00 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Thu Dec  9 21:26:00 2004
Subject: need a linux floppy
References: <008901c4de82$9b9a9350$9901a8c0@newflame> <e8d4677404120922547bbe23c1@mail.gmail.com>
Message-ID: <00a901c4de8b$f221d360$9901a8c0@newflame>

Hummm.  Got both tomsrtbt and coyote Linux running.  coyote Linux is very
nice and I have other apps for it.  But none of those had minicom on them.
Any other ideas?
-Adam
----- Original Message ----- 
From: "David H. Barr" <dhbarr at gmail.com>
To: "Adam Talbot" <talbotx at comcast.net>
Sent: Thursday, December 09, 2004 10:54 PM
Subject: Re: need a linux floppy


> tomsrtbt, the ltsp boot disk, coyote linux... they may not be what
> you're looking for, but those're the three floppy linux distros I use
> on a regular basis.
>
> -dhbarr.
>
>
> On Thu, 9 Dec 2004 22:36:40 -0800, Adam Talbot <talbotx at comcast.net>
wrote:
> >
> > Any one no of a good Linux distro that fits onto a floppy.  I have a old
> > laptop that I would like to use as a dumb terminal.  So all i need is
> > minicom.
> > Thx
> > -Adam Talbot
>




From ebiederman at lnxi.com  Thu Dec  9 21:45:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Dec  9 21:45:01 2004
Subject: need a linux floppy
In-Reply-To: <00a901c4de8b$f221d360$9901a8c0@newflame>
References: <008901c4de82$9b9a9350$9901a8c0@newflame>
	<e8d4677404120922547bbe23c1@mail.gmail.com>
	<00a901c4de8b$f221d360$9901a8c0@newflame>
Message-ID: <m3d5xiy405.fsf@maxwell.lnxi.com>

"Adam Talbot" <talbotx at comcast.net> writes:

> Hummm.  Got both tomsrtbt and coyote Linux running.  coyote Linux is very
> nice and I have other apps for it.  But none of those had minicom on them.
> Any other ideas?

cat /dev/ttyS0 
cat > /dev/ttyS0

Should just about do it.

Or for something a little more complete.

Eric

/* To compile run: gcc -g -O -Wall serial_echo.c -o serial_echo */
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/poll.h>
#include <fcntl.h>
#include <unistd.h>
#include <termios.h>
#include <errno.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>

#define BUFFER_SIZE (1024)
#define BUFFER_RESERVE 8


speed_t get_baud(int wanted)
{
	speed_t result = B0;
	switch(wanted) {
	case 50: result = B50; break;
	case 75: result = B75; break;
	case 110: result = B110; break;
	case 134: result = B134; break;
	case 150: result = B150; break;
	case 200: result = B200; break;
	case 300: result = B300; break;
	case 600: result = B600; break;
	case 1200: result = B1200; break;
	case 1800: result = B1800; break;
	case 2400: result = B2400; break;
	case 4800: result = B4800; break;
	case 9600: result = B9600; break;
	case 19200: result = B19200; break;
	case 38400: result = B38400; break;
	case 57600: result = B57600; break;
	case 115200: result = B115200; break;
	case 230400: result = B230400; break;
	case 460800: result = B460800; break;
	case 500000: result = B500000; break;
	case 576000: result = B576000; break;
	case 921600: result = B921600; break;
	case 1000000: result = B1000000; break;
	case 1152000: result = B1152000; break;
	case 1500000: result = B1500000; break;
	case 2000000: result = B2000000; break;
	case 2500000: result = B2500000; break;
	case 3000000: result = B3000000; break;
	case 3500000: result = B3500000; break;
	case 4000000: result = B4000000; break;
	}
	return result;
}


#define ESC_CHAR '\x1e'
int do_inbuf_actions(char *in_buff,  int len, int fd_serial, 
	char *input_file, int *fd_input_file)
{
	static int in_esc = 0;
	int i;
	for(i = 0; i < len ;) {
		if (!in_esc) {
			if (in_buff[i] == ESC_CHAR) {
				in_esc = 1;
				memmove(in_buff, in_buff +1, len - i -1);
				len--;
				continue;
			}
		}
		if (in_esc) {
			if (in_buff[i] == ESC_CHAR) {
				in_esc = 0;
				i++;
				continue;
			}
			else if (in_buff[i] == '\x3') {
				exit(0);
			}
			else if (in_buff[i] == 'b') {
				tcsendbreak(fd_serial, 0);
			}
			else if (in_buff[i] == 'f') {
				int fd;
				fd = open(input_file, O_RDONLY | O_NONBLOCK);
				if (fd < 0) {
					*fd_input_file = -1;
					fprintf(stderr, "Cannot open %s %s\n",
						input_file, strerror(errno));
				}
				else {
					*fd_input_file = fd;
				}
#if 0
				do_transmit_file(fd_serial, input_file);
#endif
			}
			memmove(in_buff, in_buff +1, len -i -1);
			len--;
			in_esc = 0;
			continue;
		}
		i++;
	}
	return len;
}

static struct termios initial_term_options;
void do_terminal_cleanup(void)
{
	int result;
	result = tcsetattr(STDOUT_FILENO, TCSANOW, &initial_term_options);
	fprintf(stderr, "Exiting due to error %d -> %s\n",
		errno, strerror(errno));
}
void usage(int argc, char **argv)
{
	fprintf(stderr, "Usage: %s [[[[[device] speed] none|hard|soft] ro|rw]\n",
		argv[0]);
	exit(1);
}

int main(int argc, char *argv[])
{
	int fd_serial;
	char serial_port[] = "/dev/ttyS0";
	char *port;
	speed_t speed;
	struct pollfd fds_wait[3], fds_data_wait[3], *fds;
	int result;
	char out_buff[BUFFER_SIZE], in_buff[BUFFER_SIZE];
	int out_buff_fill, in_buff_fill;
	struct termios serial_options, term_options;
	char *input_file;
	int fd_input_file;
	int hard_flow_control;
	int soft_flow_control;
	int read_only;

	port = serial_port;
	speed = B115200;
	input_file = 0;
	hard_flow_control = 0;
	soft_flow_control = 0;
	read_only = 1;
	fd_input_file = -1;
	if (argc >= 2) {
		port = argv[1];
	}
	if (argc >= 3) {
		speed = get_baud(atoi(argv[2]));
	}
	if (argc >= 4) {
		if (strcmp(argv[3], "none") == 0) {
			hard_flow_control = 0;
			soft_flow_control = 0;
		}
		else if (strcmp(argv[3], "hard") == 0) {
			hard_flow_control = 1;
		}
		else if (strcmp(argv[3], "soft") == 0) {
			soft_flow_control = 1;
		}
		else {
			usage(argc, argv);
		}
	}
	if (argc >= 5) {
		if (strcmp(argv[4], "ro") == 0) {
			read_only = 1;
		}
		else if (strcmp(argv[4], "rw")  == 0) {
			read_only = 0;
		}
		else {
			usage(argc, argv);
		}
	}
	if (argc >= 6) {
		input_file = argv[5];
	}
	       
	fd_serial = open(port, O_RDWR | O_NONBLOCK);
	if (fd_serial < 0) {
		fprintf(stderr, "Can't open %s\n", port);
		exit(1);
	}
	
	result = tcgetattr(STDOUT_FILENO, &initial_term_options);
	if (result < 0) {
		fprintf(stderr, "result < 0 errno = %d -> %s\n",
			errno, strerror(errno));
		exit(1);
	}
	atexit(do_terminal_cleanup);
	term_options = initial_term_options;
	term_options.c_iflag &= (ISTRIP | IGNBRK );
	term_options.c_cflag &= ~(CSIZE | PARENB | IXON | IXOFF | IXANY);
	term_options.c_cflag |= (CS8 |CREAD) | 
		((soft_flow_control)?(IXON|IXOFF|IXANY): 0);
	term_options.c_lflag &= 0;
	term_options.c_cc[VMIN] = 1;
	term_options.c_cc[VTIME] = 0;
	result = tcsetattr(STDOUT_FILENO, TCSANOW, &term_options);
	if (result < 0) {
		fprintf(stderr, "result < 0 errno = %d -> %s\n",
			errno, strerror(errno));
		exit(1);
	}
	

	result = tcsetattr(STDIN_FILENO, TCSANOW, &term_options);
	if (result < 0) {
		fprintf(stderr, "result < 0 errno = %d -> %s\n",
			errno, strerror(errno));
		exit(1);
	}
	
	
	result = tcgetattr(fd_serial, &serial_options);
	if (result < 0) {
		fprintf(stderr, "result < 0 errno = %d -> %s\n",
			errno, strerror(errno));
		exit(1);
	}

	serial_options.c_iflag = 0;
	serial_options.c_oflag = 0;
	serial_options.c_cflag = CS8 | CREAD | ((hard_flow_control)?CRTSCTS:0);
	serial_options.c_lflag = 0;
	cfsetispeed(&serial_options, speed);
	cfsetospeed(&serial_options, speed);

	result = tcsetattr(fd_serial, TCSANOW, &serial_options);
	if (result < 0) {
		fprintf(stderr, "result < 0 errno = %d -> %s\n",
			errno, strerror(errno));
		exit(1);
	}

	fds_wait[0].fd = fd_serial;
	fds_wait[0].events = POLLIN;
	fds_wait[0].revents = 0;
	fds_wait[1].fd = STDIN_FILENO;
	fds_wait[1].events = POLLIN;
	fds_wait[1].revents = 0;
	fds_wait[2].fd = -1;
	fds_wait[2].events = 0;
	fds_wait[2].revents = 0;
	
	fds_data_wait[0].fd = fd_serial;
	fds_data_wait[0].events = POLLIN | POLLOUT;
	fds_data_wait[0].revents = 0;
	fds_data_wait[1].fd = STDIN_FILENO;
	fds_data_wait[1].events = POLLIN;
	fds_data_wait[1].revents = 0;
	fds_data_wait[2].fd = STDOUT_FILENO;
	fds_data_wait[2].events = POLLOUT;
	fds_data_wait[2].revents = 0;

	
	out_buff_fill = 0;
	in_buff_fill = 0;
	fds = fds_wait;
	
	for (;;) {
		result = poll(fds, 3, -1);
		if (result < 0) {
			break;
		}
		if ((fds[0].revents & POLLIN) && (sizeof(out_buff) > out_buff_fill)){
			result = read(fd_serial, out_buff + out_buff_fill, 
				sizeof(out_buff) - out_buff_fill);
			if (result > 0) {
				out_buff_fill += result;
			}
		}
		if ((fds[1].revents & POLLIN) && (sizeof(in_buff) > in_buff_fill)) {
			result = read(STDIN_FILENO, in_buff + in_buff_fill,
				sizeof(in_buff) - in_buff_fill);
			if (result > 0) {
				int bytes;
				bytes = do_inbuf_actions(in_buff + in_buff_fill, result, fd_serial, input_file, &fd_input_file);
				if (read_only) 
					bytes = 0;
				in_buff_fill += bytes;
			}
		}
		if ((fd_input_file >= 0) 
			&& ((sizeof(in_buff) - BUFFER_RESERVE) > in_buff_fill)) {
			result = read(fd_input_file, in_buff + in_buff_fill,
				(sizeof(in_buff) - BUFFER_RESERVE) - in_buff_fill);
			if (result > 0) {
				in_buff_fill += result;
			}
			else if (result == 0) {
				close(fd_input_file);
				fd_input_file = -1;
			}
		}
		if ((fds[2].revents & POLLOUT) && out_buff_fill) {
			result = write(STDOUT_FILENO, out_buff, out_buff_fill);
			if (result > 0) {
				out_buff_fill -= result;
				if (out_buff_fill) {
					memmove(out_buff, out_buff + result, out_buff_fill);
				}
			}
		}
		if ((fds[0].revents & POLLOUT) && in_buff_fill) {
			result = write(fd_serial, in_buff, in_buff_fill);
			if (result > 0) {
				in_buff_fill -= result;
				if (in_buff_fill) {
					memmove(in_buff, in_buff + result, in_buff_fill);
				}
			}
		}
		fds = (in_buff_fill || out_buff_fill || (fd_input_file >= 0))? 
			fds_data_wait : fds_wait;
	}
	return 0;
}


From ginlin at nexcom.com.tw  Fri Dec 10 01:29:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Fri Dec 10 01:29:01 2004
Subject: keyboard controller jammed
In-Reply-To: <Pine.LNX.4.58.0412090914390.15514@linux.site>
Message-ID: <000101c4dead$c3a8e1f0$4f01060a@nexcom.com.tw>

>I hope you did not modify static.c?
I did. I did change the dev_root chip_op to 0 otherwise it won't execute
the default root op.  
 
I don't know if the error is related to my superio. The superio on board
is not winbond w83627hf, which is the code is based on. So the pnp
devices are never enabled.  


In file /devices/root_device.c, scan_static_bus supposes to walk through
the device tree and enable the PNP devices. I put a printk message. I
don't think the PNP devices ever get initialized.


gin






From ginlin at nexcom.com.tw  Fri Dec 10 01:33:28 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Fri Dec 10 01:33:28 2004
Subject: keyboard controller jammed
In-Reply-To: <Pine.LNX.4.58.0412090914390.15514@linux.site>
Message-ID: <000201c4dead$c47f6bd0$4f01060a@nexcom.com.tw>

>I hope you did not modify static.c?
I did. I did change the dev_root chip_op to 0 otherwise it won't execute
the default root op.  
 
I don't know if the error is related to my superio. The superio on board
is not winbond w83627hf, which is the code is based on. So the pnp
devices are never enabled.  


In file /devices/root_device.c, scan_static_bus supposes to walk through
the device tree and enable the PNP devices. I put a printk message. I
don't think the PNP devices ever get initialized.


gin






From gwatson at lanl.gov  Fri Dec 10 04:37:01 2004
From: gwatson at lanl.gov (Greg Watson)
Date: Fri Dec 10 04:37:01 2004
Subject: RFC: linuxbios table fix
In-Reply-To: <m33byeg0sa.fsf@maxwell.lnxi.com>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com> <Pine.LNX.4.58.0412092017320.16831@linux.site> <m33byeg0sa.fsf@maxwell.lnxi.com>
Message-ID: <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>

On Dec 9, 2004, at 10:49 PM, Eric W. Biederman wrote:

> "Ronald G. Minnich" <rminnich at lanl.gov> writes:
>
>> On Thu, 9 Dec 2004, Eric W. Biederman wrote:
>>
>>> I am still worried about ppc, and big endian architectures in 
>>> general.
>>> But I don't think we currently have any users there.
>>
>> we do. I think I'd like to hear Greg Watson's take on this as he is
>> working with the PPC 970 guys and this will impact him.
>
> Ron we have users of the LinxuBIOS table on PPC?  It was my impression 
> that we
> did not.
>
> I would be happy to hear what Greg has to say.  If nothing uses this 
> entry
> I will be happy to change this.    Otherwise we need to know what the 
> test
> program below reports on ppc.

Nothing uses this currently, but I will be providing support to pass 
the entire device tree to a payload in the near future. Whether this 
will be using linuxbios tables, s-expressions or XML depends on the 
results of the current discussion.

On ppc32, gcc-3.2.2 I get a size of 24. I'll try ppc64 later today.

Greg



From stephen.kimball at bench.com  Fri Dec 10 05:12:01 2004
From: stephen.kimball at bench.com (Steve Kimball)
Date: Fri Dec 10 05:12:01 2004
Subject: Linux kernel hangs
In-Reply-To: <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>
	 <Pine.LNX.4.58.0412092017320.16831@linux.site>
	 <m33byeg0sa.fsf@maxwell.lnxi.com>
	 <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
Message-ID: <1102692535.2811.5.camel@localhost.localdomain>

> On Thu, 9 Dec 2004, Gin wrote:
>
> > Linuxbios successfully loads the payload FILO which brings up Linux> kernel. But the kernel hangs while waiting for a timer interrupt. See> below. I guess the interrupt table is not correct.
> yes, it's a bad IRQ or MP table or both.
> 
> We have tools to extract them from the standard bios, see the util tree. 
>
> ron

src/util/getpir builds the IRQ table from the $PIR in memory, 
but which util extracts the MP table?

Steve 


From rminnich at lanl.gov  Fri Dec 10 05:52:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 10 05:52:00 2004
Subject: keyboard controller jammed
In-Reply-To: <000201c4dead$c47f6bd0$4f01060a@nexcom.com.tw>
References: <000201c4dead$c47f6bd0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412100908400.18498@linux.site>


On Fri, 10 Dec 2004, Gin wrote:

> I did. I did change the dev_root chip_op to 0 otherwise it won't execute
> the default root op.  

you should never modify that file. Need to modify it indicates a 
configuraiton error. 

> I don't know if the error is related to my superio. The superio on board
> is not winbond w83627hf, which is the code is based on. So the pnp
> devices are never enabled.  

you need to modify the mainboard spec, then. You're going at this from the 
wrong direction. 

ron


From rminnich at lanl.gov  Fri Dec 10 06:02:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 10 06:02:00 2004
Subject: Linux kernel hangs
In-Reply-To: <1102692535.2811.5.camel@localhost.localdomain>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>  <Pine.LNX.4.58.0412092017320.16831@linux.site>
  <m33byeg0sa.fsf@maxwell.lnxi.com>  <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
 <1102692535.2811.5.camel@localhost.localdomain>
Message-ID: <Pine.LNX.4.58.0412100918540.18498@linux.site>


On Fri, 10 Dec 2004, Steve Kimball wrote:

> src/util/getpir builds the IRQ table from the $PIR in memory, 
> but which util extracts the MP table?

I've just added the mptable tool from freebios1 to freebios2. It is in 
util.

I am sending you a private copy in case you are 'cvs delay mode'

ron


From ollie at lanl.gov  Fri Dec 10 06:56:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Fri Dec 10 06:56:01 2004
Subject: Linux kernel hangs
In-Reply-To: <Pine.LNX.4.58.0412100918540.18498@linux.site>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>
	 <Pine.LNX.4.58.0412092017320.16831@linux.site>
	 <m33byeg0sa.fsf@maxwell.lnxi.com>
	 <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
	 <1102692535.2811.5.camel@localhost.localdomain>
	 <Pine.LNX.4.58.0412100918540.18498@linux.site>
Message-ID: <1102698813.9509.2.camel@exponential.lanl.gov>

On Fri, 2004-12-10 at 09:19, Ronald G. Minnich wrote:
> On Fri, 10 Dec 2004, Steve Kimball wrote:
> 
> > src/util/getpir builds the IRQ table from the $PIR in memory, 
> > but which util extracts the MP table?
> 
> I've just added the mptable tool from freebios1 to freebios2. It is in 
> util.
> 
> I am sending you a private copy in case you are 'cvs delay mode'
> 

Ron,

the mptable utility in freebios v1 has serious bugs. It does not
work in 64 bit mode. 

Ollie




From ollie at lanl.gov  Fri Dec 10 06:59:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Fri Dec 10 06:59:01 2004
Subject: keyboard controller jammed
In-Reply-To: <000101c4dead$c3a8e1f0$4f01060a@nexcom.com.tw>
References: <000101c4dead$c3a8e1f0$4f01060a@nexcom.com.tw>
Message-ID: <1102699006.9509.5.camel@exponential.lanl.gov>

On Fri, 2004-12-10 at 04:45, Gin wrote:
> In file /devices/root_device.c, scan_static_bus supposes to walk through
> the device tree and enable the PNP devices. I put a printk message. I
> don't think the PNP devices ever get initialized.
> 
> 

What is your southbridge (LPC) again ? I guess you
LPC bridge does not have scan_static_bus is its
device:scan_bus() method. The other possiblitiy
is you did not list those PNP devices as 'sub' devices
of the LPC bridge.





From rminnich at lanl.gov  Fri Dec 10 07:00:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 10 07:00:00 2004
Subject: Linux kernel hangs
In-Reply-To: <1102698813.9509.2.camel@exponential.lanl.gov>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>  <Pine.LNX.4.58.0412092017320.16831@linux.site>
  <m33byeg0sa.fsf@maxwell.lnxi.com>  <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
  <1102692535.2811.5.camel@localhost.localdomain>  <Pine.LNX.4.58.0412100918540.18498@linux.site>
 <1102698813.9509.2.camel@exponential.lanl.gov>
Message-ID: <Pine.LNX.4.58.0412101017020.18498@linux.site>


On Fri, 10 Dec 2004, Li-Ta Lo wrote:

> the mptable utility in freebios v1 has serious bugs. It does not
> work in 64 bit mode. 

yes, it needs work, that's for sure. 

It may be better than nothing, but I'm not sure. I did use it for several 
boards so far, however.

ron


From rminnich at lanl.gov  Fri Dec 10 07:01:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 10 07:01:01 2004
Subject: keyboard controller jammed
In-Reply-To: <1102699006.9509.5.camel@exponential.lanl.gov>
References: <000101c4dead$c3a8e1f0$4f01060a@nexcom.com.tw>
 <1102699006.9509.5.camel@exponential.lanl.gov>
Message-ID: <Pine.LNX.4.58.0412101017570.18498@linux.site>


On Fri, 10 Dec 2004, Li-Ta Lo wrote:

> What is your southbridge (LPC) again ? I guess you
> LPC bridge does not have scan_static_bus is its
> device:scan_bus() method. The other possiblitiy
> is you did not list those PNP devices as 'sub' devices
> of the LPC bridge.

Ollie, it is worse than that, Gin needs to rewrite his mainboard config 
file. I am not sure what mainboard he has any more.

ron


From YhLu at tyan.com  Fri Dec 10 07:50:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri Dec 10 07:50:00 2004
Subject: keyboard controller jammed
Message-ID: <3174569B9743D511922F00A0C943142306BA3A01@TYANWEB>

He has smsc superio.

I made one for smsc for one tyan pci-e opteron MB, and I will put that into
the tree in the public tree after I get approval from vendor.

YH

-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: Friday, December 10, 2004 9:18 AM
To: Li-Ta Lo
Cc: Gin; 'LinuxBIOS'
Subject: RE: keyboard controller jammed



On Fri, 10 Dec 2004, Li-Ta Lo wrote:

> What is your southbridge (LPC) again ? I guess you
> LPC bridge does not have scan_static_bus is its
> device:scan_bus() method. The other possiblitiy
> is you did not list those PNP devices as 'sub' devices
> of the LPC bridge.

Ollie, it is worse than that, Gin needs to rewrite his mainboard config 
file. I am not sure what mainboard he has any more.

ron
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From Stephen.Kimball at bench.com  Fri Dec 10 09:40:01 2004
From: Stephen.Kimball at bench.com (Stephen.Kimball at bench.com)
Date: Fri Dec 10 09:40:01 2004
Subject: mptable
Message-ID: <9B124F08B3EFDA4F8813B05102DC7195029058BC@nh-ex01.nh.bench.com>

Ron,
I'd suggest changing busses[20] to busses[200] on line 290.
My motherboard has a bus 128.  It seems to run in 32-bit mode.

Steve

-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: Friday, December 10, 2004 11:19 AM
To: Kimball, Stephen
Cc: LinuxBIOS
Subject: Re: Linux kernel hangs



On Fri, 10 Dec 2004, Steve Kimball wrote:

> src/util/getpir builds the IRQ table from the $PIR in memory, 
> but which util extracts the MP table?

I've just added the mptable tool from freebios1 to freebios2. It is in 
util.

I am sending you a private copy in case you are 'cvs delay mode'

ron


From rminnich at lanl.gov  Fri Dec 10 09:44:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 10 09:44:00 2004
Subject: mptable
In-Reply-To: <9B124F08B3EFDA4F8813B05102DC7195029058BC@nh-ex01.nh.bench.com>
References: <9B124F08B3EFDA4F8813B05102DC7195029058BC@nh-ex01.nh.bench.com>
Message-ID: <Pine.LNX.4.58.0412101259010.19149@linux.site>


On Fri, 10 Dec 2004 Stephen.Kimball at bench.com wrote:

> I'd suggest changing busses[20] to busses[200] on line 290.
> My motherboard has a bus 128.  It seems to run in 32-bit mode.

if you would like to make other fixes send me a patch and I'll apply it.

ron


From ebiederman at lnxi.com  Fri Dec 10 10:09:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Dec 10 10:09:00 2004
Subject: RFC: linuxbios table fix
In-Reply-To: <759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
References: <m3k6rrrp1e.fsf@maxwell.lnxi.com>
	<Pine.LNX.4.58.0412092017320.16831@linux.site>
	<m33byeg0sa.fsf@maxwell.lnxi.com>
	<759EADC6-4ABB-11D9-97BA-000D932F4B4A@lanl.gov>
Message-ID: <m3ekhxvqzr.fsf@maxwell.lnxi.com>

Greg Watson <gwatson at lanl.gov> writes:

> On Dec 9, 2004, at 10:49 PM, Eric W. Biederman wrote:
> 
> > "Ronald G. Minnich" <rminnich at lanl.gov> writes:
> >
> >> On Thu, 9 Dec 2004, Eric W. Biederman wrote:
> >>
> >>> I am still worried about ppc, and big endian architectures in general.
> >>> But I don't think we currently have any users there.
> >>
> >> we do. I think I'd like to hear Greg Watson's take on this as he is
> >> working with the PPC 970 guys and this will impact him.
> >
> > Ron we have users of the LinxuBIOS table on PPC?  It was my impression that we
> > did not.
> >
> > I would be happy to hear what Greg has to say.  If nothing uses this entry
> > I will be happy to change this.    Otherwise we need to know what the test
> > program below reports on ppc.
> 
> Nothing uses this currently, but I will be providing support to pass the entire
> device tree to a payload in the near future. Whether this will be using
> linuxbios tables, s-expressions or XML depends on the results of the current
> discussion.
> 
> On ppc32, gcc-3.2.2 I get a size of 24. I'll try ppc64 later today.

Thanks.  Then I am going to ``fix'' the table definition so it returns
a size of 20 even on ppc.

What we do later is still in the air.  But at least the current situation
can be corrected without a flag day.  

Eric


From ginlin at nexcom.com.tw  Fri Dec 10 22:33:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Fri Dec 10 22:33:01 2004
Subject: keyboard controller jammed
In-Reply-To: <1102699006.9509.5.camel@exponential.lanl.gov>
Message-ID: <000001c4df5e$64d81860$4f01060a@nexcom.com.tw>

>What is your southbridge (LPC) again ? I guess you
>LPC bridge does not have scan_static_bus is its
>device:scan_bus() method. 

I guess you are correct. So the PNP devices are there but didn't get
looped through. But that's in the chip_op of the LPC bridge. It should
be fixed in the code??
   
Ron,
I did change the board config file for my target board. Here is my
platform:
North Bridge: E7501
South Bridge: ICH3 - S
SuperIO: SMSC(LPC47B27x)

The code I am based on right now is ICH5 and Winbond w83627hf.
Some Dev ID of ICH5 and ICH3-s are different. LPC bridge is one of them.
Don't know if it matters?

Is there code for ICH3-s and SMSC superIO that I can use? Otherwise I
will need to modify from the code I have now. 


gin








From stepan at openbios.org  Sat Dec 11 07:01:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat Dec 11 07:01:00 2004
Subject: amd k8: setup_remote_node()?
Message-ID: <20041211171907.GA21490@openbios.org>

Hi,

Looking at northbridge/amd/amdk8/coherent_ht.c:

setup_remote_node() copies the routing table and the resource 
map to the "remote"/freshly setup cpu. 

This function is called for cpu1, but never for cpu2 and cpu3.
This implies we should either drop it for cpu1 as well or add 
it to the cpu2/3 setup..

Stefan




From stepan at openbios.org  Sat Dec 11 07:07:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat Dec 11 07:07:01 2004
Subject: amd k8: setup_remote_node()?
In-Reply-To: <20041211171907.GA21490@openbios.org>
References: <20041211171907.GA21490@openbios.org>
Message-ID: <20041211172439.GA21587@openbios.org>

* Stefan Reinauer <stepan at openbios.org> [041211 18:19]:
> setup_remote_node() copies the routing table and the resource 
> map to the "remote"/freshly setup cpu. 
> 
> This function is called for cpu1, but never for cpu2 and cpu3.
> This implies we should either drop it for cpu1 as well or add 
> it to the cpu2/3 setup..

cpu 2 and 3 use setup_temp_node instead which is basically the same
except that it does not copy the resource map. So we can drop either one
in favour of the other.

Stefan



From stepan at openbios.org  Sat Dec 11 08:39:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat Dec 11 08:39:01 2004
Subject: romcc does not like simple code?
Message-ID: <20041211185702.GA22632@openbios.org>

Hi,

I tried to remove ht_collapse_previous_enumeration from incoherent_ht.c
ht_setup_chainx() for testing. I would have thought that removing the
call to a function of an inner loop would not cause problems with romcc,
but when removing this call romcc runs out of registers. If I put the
call back in, everything compiles fine. 

 Stefan



From stepan at openbios.org  Sat Dec 11 09:54:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat Dec 11 09:54:00 2004
Subject: collapsing devices.
Message-ID: <20041211201222.GA23659@openbios.org>

Hi,

I am desperate, still getting:

LinuxBIOS-1.1.7.0-fallback Sat Dec 11 20:30:55 CET 2004 starting...
setting up resource map....done.
04 nodes initialized.
udev=(0,0x18,0) 0xb4=00030000
Pretending to collapse device 74501022 on bus 00000000
udev=(0,0x19,0) 0xd4=000a0400
Pretending to collapse device 74501022 on bus 00000004

* Why would only bus 0 and 4 be collapsed, but not bus 1,2,3?

Stefan





From stepan at openbios.org  Sat Dec 11 10:24:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat Dec 11 10:24:00 2004
Subject: collapsing devices.
In-Reply-To: <20041211201222.GA23659@openbios.org>
References: <20041211201222.GA23659@openbios.org>
Message-ID: <20041211204140.GB24016@openbios.org>

Hi,

I started stripping down noncht enumeration.

in the beginning i really collapse bus 0. After this I only pretend to
do so, while walking through the devices with a simple dummy loop:

        for(dev = PCI_DEV(bus, 0, 0); dev <= PCI_DEV(bus, 0x1f, 0x7); dev += PCI_DEV(0, 1, 0)) {
                uint32_t id;
                unsigned pos, flags;

                id = pci_read_config32(dev, PCI_VENDOR_ID);
                if ((id == 0xffffffff) || (id == 0x00000000) ||
                        (id == 0x0000ffff) || (id == 0xffff0000))
                {
                        continue;
                }

                print_debug("Pretending to collapse device ");
                print_debug_hex32(dev);
                print_debug(" id ");
                print_debug_hex32(id);
                print_debug(" on bus ");
                print_debug_hex32(bus);
                print_debug("\r\n");
        }
        print_debug("done with bus\n\r");



LinuxBIOS-1.1.7.0-fallback Sat Dec 11 21:33:25 CET 2004 starting...
setting up resource map....done.
04 nodes initialized.
udev=(0,0x18,0) 0xb4=00040000
Pretending to collapse device 00000000 id 74501022 on bus 00000000
Pretending to collapse device 00000800 id 74501022 on bus 00000000
Pretending to collapse device 0000c000 id 11001022 on bus 00000000
Pretending to collapse device 0000c800 id 11001022 on bus 00000000
Pretending to collapse device 0000d000 id 11001022 on bus 00000000
Pretending to collapse device 0000d800 id 11001022 on bus 00000000
done with bus
bus=00 id =74501022
done. next_unitid=00000003
bus=00 id =74601022
done. next_unitid=00000007
udev=(0,0x19,0) 0xd4=000a0500
Pretending to collapse device 00050000 id 74501022 on bus 00000005
Pretending to collapse device 00050800 id 74501022 on bus 00000005
<hang>
I never get to "done with bus" 

Stefan




From felix at allot.com  Sun Dec 12 00:00:01 2004
From: felix at allot.com (Felix Radensky)
Date: Sun Dec 12 00:00:01 2004
Subject: BIOS shadowing
Message-ID: <41BC1277.4040000@allot.com>

Hi, folks

I'm trying to implement BIOS shadowing for Intel 440bx
chipset in freebios v1 code. Shadowing of 0xf0000-0xfffff is
controlled by PAM0 register in the north bridge. Here's
the code.

#define PAM0 0x59
#define CONFIG_CMD(bus, devfn, where)   (0x80000000 | (bus << 16) |
(devfn << 8) | (where & ~3))

extern void cache_disable(void);
extern void cache_enable(void);

extern unsigned long _text, _erodata;
unsigned long *bios_start = &_text;
unsigned long *bios_end = &_erodata;

/* Shadow BIOS text and rodata into RAM */
static inline void bios_shadow(void)
{
        cache_disable();

        /* Set attributes for 0xf0000-0xfffff to write only */
        outl(CONFIG_CMD(0, PCI_DEVFN(0, 0), PAM0), PCI_CONF_REG_INDEX);
        outb(0x20, PCI_CONF_REG_DATA + (PAM0 & 3));

        while (bios_start <= bios_end) {
                volatile unsigned long tmp;
                tmp = *bios_start;
                *bios_start++ = tmp;
        }

        /* Set attributes for 0xf0000-0xfffff to read only */
        outl(CONFIG_CMD(0, PCI_DEVFN(0, 0), PAM0), PCI_CONF_REG_INDEX);
        outb(0x10, PCI_CONF_REG_DATA + (PAM0 & 3));

        cache_enable();
}

This code works for me, however I have a question. When this code is
executed, 0xf0000-0xfffff is configured as uncacheable via the
corresponding MTRRs. However disabling of caching is essential  for
this code to work, and I  don't understand why.
Can someone please shed a light on this ?

Thanks a lot.

Felix.



From sagivy at 3vium.com  Sun Dec 12 02:58:01 2004
From: sagivy at 3vium.com (Sagiv Yefet)
Date: Sun Dec 12 02:58:01 2004
Subject: Running with VGA
Message-ID: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB22D6CC@cronos.trivium>

Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running
with console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041212/a13b8470/attachment.html>

From yhlu at tyan.com  Sun Dec 12 15:27:01 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sun Dec 12 15:27:01 2004
Subject: collapsing devices.
In-Reply-To: <20041211201222.GA23659@openbios.org>
Message-ID: <200412122026.iBCKQJL24283@nwn.definitive.org>

Actually for cpu0 link1, in the auto.c stage, incoherent.c only need to
handle bus 0, because ht device only at bus 0 (8131 and 8111).

For cpu1 link2, in the auto.c stage, incoherent device only need to handle
to bus 4, because we put the device on bus 4 according to setting in 0xe4 of
PCI_dev. 

The purpose of incoherent.c is set the HT-link and width and return
need_reset. Auto.c will according to need_reset from coherent.c and
incoherent.c to reset in auto.c stage. 

So in the northbrige.c of hardwaremain stage will not need to reset and make
ht speed and width effective.

The HT devices in the same HT chain are always in the same bus.

YH

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Stefan Reinauer
Sent: Saturday, December 11, 2004 12:12 PM
To: linuxbios at clustermatic.org
Subject: collapsing devices.

Hi,

I am desperate, still getting:

LinuxBIOS-1.1.7.0-fallback Sat Dec 11 20:30:55 CET 2004 starting...
setting up resource map....done.
04 nodes initialized.
udev=(0,0x18,0) 0xb4=00030000
Pretending to collapse device 74501022 on bus 00000000
udev=(0,0x19,0) 0xd4=000a0400
Pretending to collapse device 74501022 on bus 00000004

* Why would only bus 0 and 4 be collapsed, but not bus 1,2,3?

Stefan



_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From yhlu at tyan.com  Sun Dec 12 15:42:00 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sun Dec 12 15:42:00 2004
Subject: Running with VGA
In-Reply-To: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB22D6CC@cronos.trivium>
Message-ID: <200412122041.iBCKfvL24349@nwn.definitive.org>

You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running with
console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041212/25e35845/attachment.html>

From yhlu at tyan.com  Sun Dec 12 16:36:00 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sun Dec 12 16:36:00 2004
Subject: collapsing devices.
In-Reply-To: <20041211204140.GB24016@openbios.org>
Message-ID: <200412122135.iBCLZEL24548@nwn.definitive.org>

Please try this:
1. Comment out inconherent init in auto.c
2. disable hard_reset in northbridge.c 

So let the ht code in hardwaremain stage to check you ht connection.

YH
-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Stefan Reinauer
Sent: Saturday, December 11, 2004 12:42 PM
To: linuxbios at clustermatic.org
Subject: Re: collapsing devices.

Hi,

I started stripping down noncht enumeration.

in the beginning i really collapse bus 0. After this I only pretend to
do so, while walking through the devices with a simple dummy loop:

        for(dev = PCI_DEV(bus, 0, 0); dev <= PCI_DEV(bus, 0x1f, 0x7); dev +=
PCI_DEV(0, 1, 0)) {
                uint32_t id;
                unsigned pos, flags;

                id = pci_read_config32(dev, PCI_VENDOR_ID);
                if ((id == 0xffffffff) || (id == 0x00000000) ||
                        (id == 0x0000ffff) || (id == 0xffff0000))
                {
                        continue;
                }

                print_debug("Pretending to collapse device ");
                print_debug_hex32(dev);
                print_debug(" id ");
                print_debug_hex32(id);
                print_debug(" on bus ");
                print_debug_hex32(bus);
                print_debug("\r\n");
        }
        print_debug("done with bus\n\r");



LinuxBIOS-1.1.7.0-fallback Sat Dec 11 21:33:25 CET 2004 starting...
setting up resource map....done.
04 nodes initialized.
udev=(0,0x18,0) 0xb4=00040000
Pretending to collapse device 00000000 id 74501022 on bus 00000000
Pretending to collapse device 00000800 id 74501022 on bus 00000000
Pretending to collapse device 0000c000 id 11001022 on bus 00000000
Pretending to collapse device 0000c800 id 11001022 on bus 00000000
Pretending to collapse device 0000d000 id 11001022 on bus 00000000
Pretending to collapse device 0000d800 id 11001022 on bus 00000000
done with bus
bus=00 id =74501022
done. next_unitid=00000003
bus=00 id =74601022
done. next_unitid=00000007
udev=(0,0x19,0) 0xd4=000a0500
Pretending to collapse device 00050000 id 74501022 on bus 00000005
Pretending to collapse device 00050800 id 74501022 on bus 00000005
<hang>
I never get to "done with bus" 

Stefan


_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From jbors at mail.ru  Sun Dec 12 17:27:00 2004
From: jbors at mail.ru (Dmitry Borisov)
Date: Sun Dec 12 17:27:00 2004
Subject: EPIA-M freebios.v1 linux loading problem
Message-ID: <019501c4e0c6$27248df0$0200a8c0@amr.corp.intel.com>

Guys,
I use freebios v1 from CVS and it works smoothly with the filo payload and Dave Ashley's fix for the raminit.
The only caveat is that linux hangs when it is trying to initialize CLE266. Here is the log:

------------------------------------------LOG STARTS --------------------------------
...
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 177M
agpgart: Detected Via CLE266 chipset

That's it. After that Linux just sits there forever. I'll try to see what's causing it today/tomorrow but really appreciate if someone could throw me a hand. 
Appreciate it,
Dmitry/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041212/8ca5ca6e/attachment.html>

From rminnich at lanl.gov  Sun Dec 12 18:39:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun Dec 12 18:39:00 2004
Subject: keyboard controller jammed
In-Reply-To: <000001c4df5e$64d81860$4f01060a@nexcom.com.tw>
References: <000001c4df5e$64d81860$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412122156500.29365@linux.site>


On Sat, 11 Dec 2004, Gin wrote:

> Ron,
> I did change the board config file for my target board. Here is my
> platform:
> North Bridge: E7501
> South Bridge: ICH3 - S
> SuperIO: SMSC(LPC47B27x)
> 
> The code I am based on right now is ICH5 and Winbond w83627hf.
> Some Dev ID of ICH5 and ICH3-s are different. LPC bridge is one of them.
> Don't know if it matters?

I think it matters ...

ron


From ginlin at nexcom.com.tw  Mon Dec 13 00:42:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Mon Dec 13 00:42:00 2004
Subject: booting slow
In-Reply-To: <Pine.LNX.4.58.0412122156500.29365@linux.site>
Message-ID: <000001c4e102$84cdcac0$4f01060a@nexcom.com.tw>

I got the keyboard controller problem fixed by enabling Keyboard
separately (Not through the PNP devices list). Since now the PNP devices
don't get enabled at all. For now it's ok because we need only serial
com port and keyboard. But I will love to have the code for SMSC if you
have one available. Thanks.


Now linux kernel boots fine except for one problem. It is extremely slow
after this line
		"Red Hat nash version 3.4.42 starting"
It displays each character slowly including what I typed from the
keyboard(over serial console). It is very slow all the way to linux
command prompt. I think it might have something to do with the routing
table. I haven't changed much of mptable.c which is specific for another
board. I couldn't think of anything else.

gin
=====================================================
Red Hat nash version 3.4.42 starting
Loading jbd.o module
Loading ext3.o module
Mounting /proc filesystem
Creating block devices
Creating root device
Mounting root filesystem
Freeing unused kernel memory: 132k freed

INIT: version 2.84 booting

		Welcome to RedEntering runlevel: 3
		:
=========================================================
:




From rminnich at lanl.gov  Mon Dec 13 05:16:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Dec 13 05:16:01 2004
Subject: booting slow
In-Reply-To: <000001c4e102$84cdcac0$4f01060a@nexcom.com.tw>
References: <000001c4e102$84cdcac0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412130833500.4816@linux.site>

one possibility is that you are getting no serial interrupts, so the 
serial I/O is happening only very rarely. 

You're going to need to fix your linuxbios burning up so that it is built 
correctly. 

One question, again, as I forget: what mobo is this?

ron



From yhlu at tyan.com  Mon Dec 13 11:16:00 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Mon Dec 13 11:16:00 2004
Subject: collapsing devices.
In-Reply-To: <200412122026.iBCKQJL24283@nwn.definitive.org>
Message-ID: <200412131615.iBDGFtL28843@nwn.definitive.org>

Eric,

I wonder if ht_collapse_previous_enumeration need to the collapse from tail
to head.

For example if

8131(1)-8131-8111
Unit id 1-->3-->5

Then if clear the 8131(1) at first, can left chain still be accessed.....

YH

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Yinghai Lu
Sent: Sunday, December 12, 2004 5:45 PM
To: 'Stefan Reinauer'; linuxbios at clustermatic.org
Subject: RE: collapsing devices.

Actually for cpu0 link1, in the auto.c stage, incoherent.c only need to
handle bus 0, because ht device only at bus 0 (8131 and 8111).

For cpu1 link2, in the auto.c stage, incoherent device only need to handle
to bus 4, because we put the device on bus 4 according to setting in 0xe4 of
PCI_dev. 

The purpose of incoherent.c is set the HT-link and width and return
need_reset. Auto.c will according to need_reset from coherent.c and
incoherent.c to reset in auto.c stage. 

So in the northbrige.c of hardwaremain stage will not need to reset and make
ht speed and width effective.

The HT devices in the same HT chain are always in the same bus.

YH

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Stefan Reinauer
Sent: Saturday, December 11, 2004 12:12 PM
To: linuxbios at clustermatic.org
Subject: collapsing devices.

Hi,

I am desperate, still getting:

LinuxBIOS-1.1.7.0-fallback Sat Dec 11 20:30:55 CET 2004 starting...
setting up resource map....done.
04 nodes initialized.
udev=(0,0x18,0) 0xb4=00030000
Pretending to collapse device 74501022 on bus 00000000
udev=(0,0x19,0) 0xd4=000a0400
Pretending to collapse device 74501022 on bus 00000004

* Why would only bus 0 and 4 be collapsed, but not bus 1,2,3?

Stefan



_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From ginlin at nexcom.com.tw  Mon Dec 13 15:36:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Mon Dec 13 15:36:00 2004
Subject: booting slow
Message-ID: <000101c4e17f$ad624010$4f01060a@nexcom.com.tw>

This is our proprietary mobo. In case you want a quick glance,
http://www.nexcom.com/product/nex/nex7220/

North Bridge: E7501
South Bridge: ICH3 - S
SuperIO: SMSC(LPC47B27x)
I base on the code for tyan/s2735.

If it was the serial interrupt, why didn't it happen earlier? It starts
getting slow at certain point in the linux kernel.  

gin





From YhLu at tyan.com  Mon Dec 13 15:48:01 2004
From: YhLu at tyan.com (YhLu)
Date: Mon Dec 13 15:48:01 2004
Subject: collapsing devices.
Message-ID: <3174569B9743D511922F00A0C943142306BA3B49@TYANWEB>

Stefan,

I add dump_pci_decvies_on_bus in debug.c

Please add calling to dump_pci_devices_on_bus(busn) before
ht_collapse_previous_enumeration(busn). In ht_setup_chains.

Also in auto.c you need to put inconerent_ht.c after debug.c.

I guess you can use if(busn!=0) to skip the ht chain collapse if you can not
dump that ht chain.
Or that's say the ht chain other than the first chain doesn't need collapse.

YH

#if 0
                print_debug("udev=(0,0x");
                print_debug_hex8(devpos);
                print_debug(",0) 0x");
                print_debug_hex8(regpos);
                print_debug("=");
                print_debug_hex32(dword);
#endif

#if 1
                dump_pci_devices_on_bus(busn);
#endif

                /* Make certain the HT bus is not enumerated */
                ht_collapse_previous_enumeration(busn);


output for s2885 is
LinuxBIOS-1.1.72.0_Fallback Mon Dec 13 16:51:50 PST 2004 starting...
02 nodes initialized.
PCI: 00:01.00
00: 22 10 50 74 00 00 30 02 12 00 04 06 00 40 81 00
10: 00 00 00 00 00 00 00 00 00 00 00 40 f1 01 20 02
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: ff ff 00 00 a0 00 00 00 00 00 00 00 ff 00 00 00
40: 05 00 1f 00 00 00 00 00 02 0c 00 00 00 2c 00 00
50: 00 00 03 00 00 00 05 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 07 b8 83 00 08 00 03 00 0e 00 ff ff 02 00 ff ff
b0: 00 00 00 00 00 00 00 00 08 c0 00 80 00 00 00 00
c0: 08 00 41 00 20 00 11 00 20 00 00 00 22 00 35 00
d0: 02 00 35 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 08 08 0d 00 08 08 0f 00 0f 0f 15 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:01.01
00: 22 10 51 74 00 00 00 02 01 10 00 08 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:02.00
00: 22 10 50 74 00 00 30 02 12 00 04 06 00 40 81 00
10: 00 00 00 00 00 00 00 00 00 00 00 40 f1 01 20 02
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: ff ff 00 00 a0 00 00 00 00 00 00 00 ff 00 00 00
40: 05 00 1f 00 00 00 00 00 00 00 00 00 00 2c 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 07 b8 c3 00 10 00 03 00 0e 00 ff ff 02 00 ff ff
b0: 00 00 00 00 00 00 00 00 08 00 00 80 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:02.01
00: 22 10 51 74 00 00 00 02 01 10 00 08 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:03.00
00: 22 10 60 74 00 00 30 02 07 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 f0 00 00 02
20: f0 ff 00 00 f0 ff 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 04 06 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 08 f0 83 00 20 00 00 00 d0 00 00 00 22 00 01 00
d0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 08 00 0e 00 08 00 0f 00 0f 00 19 00 00 00 00 00
f0: 08 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:04.00
00: 22 10 68 74 0f 00 20 02 05 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 10 07 c0 01 00 00 00 ff ff 00 00 00 00 00 c0
50: 00 00 00 00 85 01 00 00 44 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 de 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:04.01
00: 22 10 69 74 00 00 00 02 03 8a 01 01 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 cc 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
40: 00 00 00 00 00 00 00 00 a8 a8 a8 a8 ff 00 ff ff
50: 03 03 03 03 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:04.02
00: 22 10 6a 74 00 00 00 02 02 00 05 0c 00 00 00 00
10: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00
40: 02 00 05 0c 00 00 00 00 06 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:04.03
00: 22 10 6b 74 00 00 80 02 05 00 00 00 00 16 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 51 00 04 00 00 00 00 20 14 10 00 00 00 00 00
50: 00 80 00 00 0f 00 00 00 01 dd 00 00 00 00 00 00
60: 00 00 00 00 13 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: d1 6b 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:04.05
00: 22 10 6d 74 00 00 00 02 03 00 01 04 00 00 00 00
10: 01 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:04.06
00: 22 10 6e 74 00 00 00 02 03 00 03 07 00 00 00 00
10: 01 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:18.00
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00
40: 01 01 05 00 04 04 01 00 01 01 01 00 01 01 01 00
50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00
60: 10 00 01 00 e4 02 00 00 00 c8 00 0f 7c 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 08 a0 01 21 20 00 11 00 22 00 75 80 02 00 00 00
90: 56 04 51 02 00 00 00 00 07 00 00 00 00 00 00 00
a0: 08 c0 01 21 20 00 11 11 22 05 75 80 02 00 00 00
b0: 13 56 13 04 00 00 00 00 03 00 00 00 00 00 00 00
c0: 08 00 01 21 20 00 11 00 22 00 75 80 02 00 00 00
d0: 56 04 51 02 00 00 06 00 07 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:18.01
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00
60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00
70: 00 00 00 00 06 00 00 00 00 00 00 00 07 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 03 00 fc 00 20 ff ff 00
c0: 03 00 00 00 20 f0 ff 01 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 03 02 00 06 03 00 07 08 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:18.02
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 8a 94 f0 b4 00 00 00 00 76 f6 28 30 16 fd 05 9f
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: cb 7a 56 c0 38 87 8c 3a 1e 4d 4a 42 a0 23 08 00
e0: 00 00 00 00 9a 00 62 b1 81 87 0a 05 d4 98 ad 45
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:18.03
00: 22 10 03 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 bd 3f 00 40 03 60 00 36
50: 88 42 0c 44 ac 00 00 00 00 00 00 00 80 97 a7 f5
60: 5c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 11 01 02 51 11 80 00 50 00 38 00 08 1b 22 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 84 15 00 00 20 35 fa 68 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 3e 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 07 07 e2 04 00 00 00 00 00 00 25 00
e0: 00 00 00 00 20 0c 58 10 1f 01 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:19.00
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00
40: 04 04 01 00 01 01 05 00 01 01 01 00 01 01 01 00
50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00
60: 11 00 01 00 e4 00 00 00 00 c8 00 0f 74 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 08 a0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00
90: 13 56 13 04 00 00 00 00 00 00 00 00 00 00 00 00
a0: 08 c0 01 21 20 00 11 11 22 05 75 80 02 00 00 00
b0: 13 56 13 04 00 00 00 00 03 00 00 00 00 00 00 00
c0: 08 00 01 21 d0 00 11 77 22 00 75 80 02 00 00 00
d0: ca 48 76 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:19.01
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00
60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00
70: 00 00 00 00 06 00 00 00 00 00 00 00 07 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 03 00 fc 00 20 ff ff 00
c0: 03 00 00 00 20 f0 ff 01 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 03 02 00 06 03 00 07 08 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:19.02
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 10 6f 17 e8 00 00 00 00 58 85 1b 0b 16 a7 a1 df
c0: 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 09 da fe a2 f4 80 21 d9 17 18 3b 5a 20 63 10 19
e0: 26 8d 04 00 01 14 a7 dd 23 a4 84 e5 0e 03 ee 8d
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 00:19.03
00: 22 10 03 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 0b 0c 06 00 40 00 00 b4
50: 30 b0 31 44 0d 00 00 00 00 00 00 00 00 00 1a 09
60: 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 11 01 02 51 11 80 00 50 00 38 00 08 1b 22 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 2c 00 90 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 2b 00 00 80 f5 8f 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 07 07 e2 04 00 00 00 00 00 25 00 00
e0: 00 00 00 00 20 0d 56 10 1f 01 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 07:00.00
00: 22 10 54 74 00 00 10 02 13 00 00 06 00 00 00 00
10: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
40: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 0c 00 19 00 0b 00 17 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 02 c0 30 00 77 0b 00 1f 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 0f 01 00 00 00 00 00 00 00 00 00
c0: 08 00 60 00 20 00 11 00 50 00 00 77 22 00 35 00
d0: 02 00 35 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 08 08 12 00 08 08 10 00 0f 0f 1f 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PCI: 07:01.00
00: 22 10 55 74 00 00 20 02 13 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 f1 01 20 02
20: f0 ff 00 00 f0 ff 00 00 00 00 00 00 00 00 00 00
30: ff ff 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ht reset -


LinuxBIOS-1.1.72.0_Fallback Mon Dec 13 16:51:50 PST 2004 starting...
02 nodes initialized.


From ben.sommer at berlin.de  Mon Dec 13 19:15:00 2004
From: ben.sommer at berlin.de (Ben Sommer)
Date: Mon Dec 13 19:15:00 2004
Subject: Epia-M 10k
Message-ID: <200412140633.25583.ben.sommer@berlin.de>

Hi
is here someone with a working bios for the epia-m board? I need the config 
file or the bios for 256MB and filo boot.

Thx Ben -)


From YhLu at tyan.com  Tue Dec 14 13:13:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue Dec 14 13:13:01 2004
Subject: 4G 4 Rank memory module
Message-ID: <3174569B9743D511922F00A0C943142306BA3B9C@TYANWEB>

Eric,

Currently, duplicate ram in auto.c make the 4 ranks works. ( the MB that I'm
using is EVT version. The HW engineer just did some rework to meet the
production version).

Also I want to mix the 2 ranks and 4 ranks memory by change raminit.c, but
it does not work.

Please check the diff, maybe I miss sth.

YH

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ddr_4ranks.diff
Type: application/octet-stream
Size: 2370 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041214/bd1da870/attachment.obj>

From ginlin at nexcom.com.tw  Tue Dec 14 15:27:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Tue Dec 14 15:27:01 2004
Subject: booting slow
In-Reply-To: <Pine.LNX.4.58.0412132239480.8852@linux.site>
Message-ID: <000001c4e247$89fc8680$4f01060a@nexcom.com.tw>

>that's the interesting part. What happens is that once init is running
and 
>things get a bit more formal, things start to slow down. There are lots
of 
>causes we've found for this, but interrupts is typically  the big one.

The serial interrupt? Shouldn't it be easy like assigning it an irq? 
What other causes that you've found out? One possibility I can think of
is the cache. It was turned off.

gin



From rminnich at lanl.gov  Tue Dec 14 16:01:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Dec 14 16:01:00 2004
Subject: booting slow
In-Reply-To: <000001c4e247$89fc8680$4f01060a@nexcom.com.tw>
References: <000001c4e247$89fc8680$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412141918510.2507@linux.site>


On Wed, 15 Dec 2004, Gin wrote:

> The serial interrupt? Shouldn't it be easy like assigning it an irq? 
> What other causes that you've found out? One possibility I can think of
> is the cache. It was turned off.

well, that was the other possibility I was going to mention, on our first 
tries at smp four years ago we'd see things run fast until the other SMP 
CPU got turned on, then run slow. Turns out the cache was only enabled on 
one cpu ...

ron


From YhLu at tyan.com  Tue Dec 14 16:47:00 2004
From: YhLu at tyan.com (YhLu)
Date: Tue Dec 14 16:47:00 2004
Subject: 4G 4 Rank memory module
Message-ID: <3174569B9743D511922F00A0C943142306BA3BD5@TYANWEB>

Done.

Forget 4xDIMM in DRAM_CONFIG_LOW.

YH

-----Original Message-----
From: YhLu 
Sent: Tuesday, December 14, 2004 3:41 PM
To: ebiederman at lnxi.com
Cc: Stefan Reinauer; 'LinuxBIOS'
Subject: RE: 4G 4 Rank memory module

Eric,

Currently, duplicate ram in auto.c make the 4 ranks works. ( the MB that I'm
using is EVT version. The HW engineer just did some rework to meet the
production version).

Also I want to mix the 2 ranks and 4 ranks memory by change raminit.c, but
it does not work.

Please check the diff, maybe I miss sth.

YH


-------------- next part --------------
A non-text attachment was scrubbed...
Name: ddr_4ranks_done.diff
Type: application/octet-stream
Size: 2792 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041214/24172b91/attachment.obj>

From sagivy at 3vium.com  Tue Dec 14 21:43:00 2004
From: sagivy at 3vium.com (Sagiv Yefet)
Date: Tue Dec 14 21:43:00 2004
Subject: Running with VGA
Message-ID: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB228AB5@cronos.trivium>

I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running
with console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041214/1a0d2bf3/attachment.html>

From daubin at actuality-systems.com  Wed Dec 15 03:26:00 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Wed Dec 15 03:26:00 2004
Subject: booting slow
Message-ID: <E8F8DBCB0468204E856114A2CD20741F390EDE@mail.local.ActualitySystems.com>

Seen this when interrupts in irq.c were wrong based on 
The motherboard.  In our case we'd use etherboot to
Load the kernel (which doesn't handle interrupts) then
Once kernel was loaded we'd see the problem.  This
Was fixed by fixing the irq table.

Dave 

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Ronald G. Minnich
Sent: Tuesday, December 14, 2004 9:20 PM
To: Gin
Cc: 'LinuxBIOS'
Subject: RE: booting slow



On Wed, 15 Dec 2004, Gin wrote:

> The serial interrupt? Shouldn't it be easy like assigning it an irq? 
> What other causes that you've found out? One possibility I can think 
> of is the cache. It was turned off.

well, that was the other possibility I was going to mention, on our
first tries at smp four years ago we'd see things run fast until the
other SMP CPU got turned on, then run slow. Turns out the cache was only
enabled on one cpu ...

ron
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From rminnich at lanl.gov  Wed Dec 15 05:51:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Dec 15 05:51:01 2004
Subject: booting slow
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F390EDE@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F390EDE@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.58.0412150908500.4253@linux.site>


On Wed, 15 Dec 2004, Dave Aubin wrote:

> Seen this when interrupts in irq.c were wrong based on The motherboard.  
> In our case we'd use etherboot to Load the kernel (which doesn't handle
> interrupts) then Once kernel was loaded we'd see the problem.  This Was
> fixed by fixing the irq table.

glad to see someone else confirm this ... 

ron


From stepan at openbios.org  Wed Dec 15 06:16:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed Dec 15 06:16:01 2004
Subject: collapsing devices.
In-Reply-To: <E1CdgLf-0003pk-Vx@khepri.openbios.org>
References: <20041211204140.GB24016@openbios.org> <E1CdgLf-0003pk-Vx@khepri.openbios.org>
Message-ID: <20041215163441.GB19153@openbios.org>

* Yinghai Lu <yhlu at tyan.com> [041213 03:54]:
> Please try this:
> 1. Comment out inconherent init in auto.c
> 2. disable hard_reset in northbridge.c 

It will hang here:
PCI: 04:00.0 [1022/7464] enabled
PCI: 04:00.1 [1022/7464] enabled
PCI: 04:00.2 No device operations
PCI: 04:01.0 No device operations
PCI: 04:04.0 [1002/4752] enabled
PCI: 04:05.0 [8086/1209] enabled
PCI: pci_scan_bus returning with max=04
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
I2C: 70 enabled
PCI: pci_scan_bus returning with max=04
PCI: 00:18.0 Hyper transport scan link: 1 new max: 4
PCI: 00:19.0 amdk8_scan_chains max: 4 starting...
PCI: 00:19.0 Hyper transport scan link: 2 max: 5
<hang>

which made me assume that the ht chain on cpu1 (0:19.x) is mapped to
bus 5 and higher. Wrong?

Stefan



From stepan at openbios.org  Wed Dec 15 06:17:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed Dec 15 06:17:01 2004
Subject: collapsing devices.
In-Reply-To: <3174569B9743D511922F00A0C943142306BA3B49@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA3B49@TYANWEB>
Message-ID: <20041215163603.GC19153@openbios.org>

* YhLu <YhLu at tyan.com> [041214 03:14]:
> Stefan,
> 
> I add dump_pci_decvies_on_bus in debug.c
> 
> Please add calling to dump_pci_devices_on_bus(busn) before
> ht_collapse_previous_enumeration(busn). In ht_setup_chains.
> 
> Also in auto.c you need to put inconerent_ht.c after debug.c.

See the other mail I sent you. When just calling a loop for scanning
bus 0-16 before ht_setup_chains, it finds the devices on bus0, none on
1-5 and then hangs while scanning bus5

Stefan



From jbors at mail.ru  Wed Dec 15 08:13:00 2004
From: jbors at mail.ru (Dmitry Borisov)
Date: Wed Dec 15 08:13:00 2004
Subject: EPIA-M freebios.v1 linux loading problem
References: <019501c4e0c6$27248df0$0200a8c0@amr.corp.intel.com>
Message-ID: <004201c4e2d4$6435ad40$0200a8c0@amr.corp.intel.com>

I was not able to pass through the agpgart module, so I disabled it in the kernel.
Everything works now.
Dmitry/
 
  ----- Original Message ----- 
  From: Dmitry Borisov 
  To: linuxbios at clustermatic.org 
  Sent: Sunday, December 12, 2004 7:45 PM
  Subject: EPIA-M freebios.v1 linux loading problem


  Guys,
  I use freebios v1 from CVS and it works smoothly with the filo payload and Dave Ashley's fix for the raminit.
  The only caveat is that linux hangs when it is trying to initialize CLE266. Here is the log:

  ------------------------------------------LOG STARTS --------------------------------
  ...
  Linux agpgart interface v0.99 (c) Jeff Hartmann
  agpgart: Maximum main memory to use for agp memory: 177M
  agpgart: Detected Via CLE266 chipset

  That's it. After that Linux just sits there forever. I'll try to see what's causing it today/tomorrow but really appreciate if someone could throw me a hand. 
  Appreciate it,
  Dmitry/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041215/aed11f02/attachment.html>

From YhLu at tyan.com  Wed Dec 15 09:01:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec 15 09:01:01 2004
Subject: collapsing devices.
Message-ID: <3174569B9743D511922F00A0C943142306BA3C2C@TYANWEB>

Eric,

static void ht_collapse_previous_enumeration(unsigned bus)
{       
        device_t dev;
                
        /* Spin through the devices and collapse any previous
         * hypertransport enumeration.
         */
        for(dev = PCI_DEV(bus, 0, 0); dev <= PCI_DEV(bus, 0x1f, 0x7); dev +=
PCI_DEV(0, 1, 0)) {

I think PCI_DEV(bus, 0, 0) should be changed to PCI_DEV(bus, 1, 0)
And before that it should check PCI_DEV(bus,0,0), if the device is there,
collapse should get back right away and don't do any collapse.

In the hypertransport.c collapse don't need to check PCI_DEV(bus, 0, 0),
because it must begin from unitid 1.

YH

-----Original Message-----
From: Stefan Reinauer [mailto:stepan at openbios.org] 
Sent: Wednesday, December 15, 2004 8:36 AM
To: YhLu
Cc: 'Eric W. Biederman'; linuxbios at clustermatic.org
Subject: Re: collapsing devices.

* YhLu <YhLu at tyan.com> [041214 03:14]:
> Stefan,
> 
> I add dump_pci_decvies_on_bus in debug.c
> 
> Please add calling to dump_pci_devices_on_bus(busn) before
> ht_collapse_previous_enumeration(busn). In ht_setup_chains.
> 
> Also in auto.c you need to put inconerent_ht.c after debug.c.

See the other mail I sent you. When just calling a loop for scanning
bus 0-16 before ht_setup_chains, it finds the devices on bus0, none on
1-5 and then hangs while scanning bus5

Stefan


From YhLu at tyan.com  Wed Dec 15 09:37:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec 15 09:37:01 2004
Subject: collapsing devices.
Message-ID: <3174569B9743D511922F00A0C943142306BA3C34@TYANWEB>

Stefan,

Please check out the patch. It works well with our MB.

YH

-----Original Message-----
From: YhLu 
Sent: Wednesday, December 15, 2004 11:29 AM
To: Stefan Reinauer
Cc: 'Eric W. Biederman'; linuxbios at clustermatic.org
Subject: RE: collapsing devices.

Eric,

static void ht_collapse_previous_enumeration(unsigned bus)
{       
        device_t dev;
                
        /* Spin through the devices and collapse any previous
         * hypertransport enumeration.
         */
        for(dev = PCI_DEV(bus, 0, 0); dev <= PCI_DEV(bus, 0x1f, 0x7); dev +=
PCI_DEV(0, 1, 0)) {

I think PCI_DEV(bus, 0, 0) should be changed to PCI_DEV(bus, 1, 0)
And before that it should check PCI_DEV(bus,0,0), if the device is there,
collapse should get back right away and don't do any collapse.

In the hypertransport.c collapse don't need to check PCI_DEV(bus, 0, 0),
because it must begin from unitid 1.

YH

-----Original Message-----
From: Stefan Reinauer [mailto:stepan at openbios.org] 
Sent: Wednesday, December 15, 2004 8:36 AM
To: YhLu
Cc: 'Eric W. Biederman'; linuxbios at clustermatic.org
Subject: Re: collapsing devices.

* YhLu <YhLu at tyan.com> [041214 03:14]:
> Stefan,
> 
> I add dump_pci_decvies_on_bus in debug.c
> 
> Please add calling to dump_pci_devices_on_bus(busn) before
> ht_collapse_previous_enumeration(busn). In ht_setup_chains.
> 
> Also in auto.c you need to put inconerent_ht.c after debug.c.

See the other mail I sent you. When just calling a loop for scanning
bus 0-16 before ht_setup_chains, it finds the devices on bus0, none on
1-5 and then hangs while scanning bus5

Stefan
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ht_collapse.patch
Type: application/octet-stream
Size: 1511 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041215/c6f85d86/attachment.obj>

From daubin at actuality-systems.com  Wed Dec 15 10:27:00 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Wed Dec 15 10:27:00 2004
Subject: booting slow
Message-ID: <E8F8DBCB0468204E856114A2CD20741F390F23@mail.local.ActualitySystems.com>

Oh, one more thing.  It was easy to see when doing 
A cat /proc/interrupts and watching the offending interrupt configured
wrong
Just increment like mad. 

-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: Wednesday, December 15, 2004 11:09 AM
To: Dave Aubin
Cc: Gin; LinuxBIOS
Subject: RE: booting slow



On Wed, 15 Dec 2004, Dave Aubin wrote:

> Seen this when interrupts in irq.c were wrong based on The
motherboard.  
> In our case we'd use etherboot to Load the kernel (which doesn't 
> handle
> interrupts) then Once kernel was loaded we'd see the problem.  This 
> Was fixed by fixing the irq table.

glad to see someone else confirm this ... 

ron


From YhLu at tyan.com  Wed Dec 15 11:04:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec 15 11:04:00 2004
Subject: warning about pci_driver
Message-ID: <3174569B9743D511922F00A0C943142307290ABF@TYANWEB>

/tmp/ccX7Rb2q.s:9: Warning: setting incorrect section attributes for
.rodata.pci_driver

Why?

YH


From ebiederman at lnxi.com  Wed Dec 15 11:57:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed Dec 15 11:57:00 2004
Subject: warning about pci_driver
In-Reply-To: <3174569B9743D511922F00A0C943142307290ABF@TYANWEB>
References: <3174569B9743D511922F00A0C943142307290ABF@TYANWEB>
Message-ID: <m3k6rjcin6.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> /tmp/ccX7Rb2q.s:9: Warning: setting incorrect section attributes for
> .rodata.pci_driver
> 
> Why?

Good question.  We set section attributes that say the section will
be present.  Beyond that I don't know why binutils (I think it's as in
this case) is complaining.

Eric


From stepan at openbios.org  Wed Dec 15 12:13:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed Dec 15 12:13:00 2004
Subject: collapsing devices.
In-Reply-To: <3174569B9743D511922F00A0C943142306BA3C34@TYANWEB>
References: <3174569B9743D511922F00A0C943142306BA3C34@TYANWEB>
Message-ID: <20041215223124.GB1997@openbios.org>

* YhLu <YhLu at tyan.com> [041215 21:05]:
> Stefan,
> 
> Please check out the patch. It works well with our MB.
> 
> YH

No change here. The machine still hangs. It seems it is dead as soon as I
am trying to put my fingers on anything higher than bus4. I'll go and
compare bridge setups tomorrow.

 Stefan


From YhLu at tyan.com  Wed Dec 15 16:29:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec 15 16:29:01 2004
Subject: Running with VGA
Message-ID: <3174569B9743D511922F00A0C943142307290B24@TYANWEB>

I commit the changes for you. Please check it out from
 
http://snapshots.linuxbios.org/ <http://snapshots.linuxbios.org/> 
 
one hour later.
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Wednesday, December 15, 2004 12:09 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running with
console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041215/bb3952e9/attachment.html>

From ginlin at nexcom.com.tw  Wed Dec 15 16:39:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec 15 16:39:00 2004
Subject: booting slow
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F390F23@mail.local.ActualitySystems.com>
Message-ID: <000001c4e31a$f9982890$4f01060a@nexcom.com.tw>

>It was easy to see when doing 
>A cat /proc/interrupts and watching the offending interrupt configured
>Wrong. Just increment like mad. 
 
This is the result of a cat /proc/interrupts. The interrupt increments
of timer and ide0 seem fine. I compared it with a normal bios boot. 


=========================================================

           CPU0
  0:    5331065          XT-PIC  timer
  1:          0          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:          0          XT-PIC  serial
  5:          0          XT-PIC  usb-uhci
  8:          1          XT-PIC  rtc
 10:          0          XT-PIC  usb-uhci
 11:          0          XT-PIC  usb-uhci
 14:      22880          XT-PIC  ide0
NMI:          0
ERR:          0
================================================================



From ginlin at nexcom.com.tw  Wed Dec 15 16:56:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec 15 16:56:01 2004
Subject: booting slow
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F390EDE@mail.local.ActualitySystems.com>
Message-ID: <000301c4e31d$4ca672b0$4f01060a@nexcom.com.tw>

>Seen this when interrupts in irq.c were wrong based on 
>The motherboard.  In our case we'd use etherboot to
>Load the kernel (which doesn't handle interrupts) then
>Once kernel was loaded we'd see the problem.  This
>Was fixed by fixing the irq table.

Thanks for the hint.
I am able to load the kernel now. It just executes commands very slowly.

One question for the irq_routing table(is that what you mean by irq.c?).
The getpir util generates a routing table by looking at the memory
config of my "developing" machine. How's it related to my target
machine? 

Any document I can reference? This link mentioned on irq_tables.c
http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM doesn't work.


gin



From rminnich at lanl.gov  Wed Dec 15 18:03:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Dec 15 18:03:00 2004
Subject: booting slow
In-Reply-To: <000301c4e31d$4ca672b0$4f01060a@nexcom.com.tw>
References: <000301c4e31d$4ca672b0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412152121050.6102@linux.site>


On Thu, 16 Dec 2004, Gin wrote:

> The getpir util generates a routing table by looking at the memory
> config of my "developing" machine. How's it related to my target
> machine? 

It almost certainly is wrong, unless all the wires on the machines are 
absolutely identical. I am willing to guess your irq tabls for the target 
are wrong.

> Any document I can reference? This link mentioned on irq_tables.c
> http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM doesn't work.

oh great. I will try to find a copy here.

ron


From talbotx at comcast.net  Wed Dec 15 18:21:01 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Wed Dec 15 18:21:01 2004
Subject: Fast question
Message-ID: <013601c4e329$3c723b20$9901a8c0@newflame>

What files are needed off my target system? I now I need to build
irq_tables.c, what else do i need to build, if anything?
-Adam




From bari at onelabs.com  Wed Dec 15 19:04:01 2004
From: bari at onelabs.com (Bari Ari)
Date: Wed Dec 15 19:04:01 2004
Subject: booting slow
In-Reply-To: <Pine.LNX.4.58.0412152121050.6102@linux.site>
References: <000301c4e31d$4ca672b0$4f01060a@nexcom.com.tw> <Pine.LNX.4.58.0412152121050.6102@linux.site>
Message-ID: <41C11C00.4060809@onelabs.com>

Ronald G. Minnich wrote:
> 
> On Thu, 16 Dec 2004, Gin wrote:

>>Any document I can reference? This link mentioned on irq_tables.c
>>http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM doesn't work.

I think they moved it here: 
http://www.microsoft.com/whdc/archive/pciirq.mspx

-Bari



From daubin at actuality-systems.com  Thu Dec 16 04:25:01 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Thu Dec 16 04:25:01 2004
Subject: booting slow
Message-ID: <E8F8DBCB0468204E856114A2CD20741F390F45@mail.local.ActualitySystems.com>

 

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Ronald G. Minnich
Sent: Wednesday, December 15, 2004 11:22 PM
To: Gin
Cc: 'LinuxBIOS'
Subject: RE: booting slow



On Thu, 16 Dec 2004, Gin wrote:

> The getpir util generates a routing table by looking at the memory 
> config of my "developing" machine. How's it related to my target 
> machine?

It almost certainly is wrong, unless all the wires on the machines are
absolutely identical. I am willing to guess your irq tabls for the
target are wrong.

You can only use getpir if you have a working bios.  Otherwise you
Will get junk.  Considering your board is new, you don't have a
Working bios, no?  You have to go the hard way and read the 
Bottom link as to how to make the irq.c file.  Base it off of your
Motherboard design and make changes where the wires are, based on
The shematic.  Enjoy:)

> Any document I can reference? This link mentioned on irq_tables.c 
> http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM doesn't work.

oh great. I will try to find a copy here.

Ron

Here it is:
http://www.microsoft.com/whdc/archive/pciirq.mspx
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From rminnich at lanl.gov  Thu Dec 16 05:52:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Dec 16 05:52:00 2004
Subject: Fast question
In-Reply-To: <013601c4e329$3c723b20$9901a8c0@newflame>
References: <013601c4e329$3c723b20$9901a8c0@newflame>
Message-ID: <Pine.LNX.4.58.0412160848220.7595@linux.site>


On Wed, 15 Dec 2004, Adam Talbot wrote:

> What files are needed off my target system? I now I need to build
> irq_tables.c, what else do i need to build, if anything?

start with irq_tables.c and boot non-smp.

ron


From ollie at lanl.gov  Thu Dec 16 06:40:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu Dec 16 06:40:00 2004
Subject: booting slow
In-Reply-To: <000001c4e31a$f9982890$4f01060a@nexcom.com.tw>
References: <000001c4e31a$f9982890$4f01060a@nexcom.com.tw>
Message-ID: <1103216320.23704.1.camel@exponential.lanl.gov>

On Wed, 2004-12-15 at 19:56, Gin wrote:
> >It was easy to see when doing 
> >A cat /proc/interrupts and watching the offending interrupt configured
> >Wrong. Just increment like mad. 
>  
> This is the result of a cat /proc/interrupts. The interrupt increments
> of timer and ide0 seem fine. I compared it with a normal bios boot. 
> 

Timer and IDE are consider 'legacy' device in the IRQ routing
context (i.e. they are not routed at all).

I think you have to construct the PRIQ table by hand from the
schematic diagram.

Ollie

> 
> =========================================================
> 
>            CPU0
>   0:    5331065          XT-PIC  timer
>   1:          0          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   4:          0          XT-PIC  serial
>   5:          0          XT-PIC  usb-uhci
>   8:          1          XT-PIC  rtc
>  10:          0          XT-PIC  usb-uhci
>  11:          0          XT-PIC  usb-uhci
>  14:      22880          XT-PIC  ide0
> NMI:          0
> ERR:          0
> ================================================================
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From ginlin at nexcom.com.tw  Thu Dec 16 19:47:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Thu Dec 16 19:47:00 2004
Subject: irq_tables.c
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F390F45@mail.local.ActualitySystems.com>
Message-ID: <000001c4e3fe$85c735c0$4f01060a@nexcom.com.tw>

>You can only use getpir if you have a working bios.  Otherwise you
>Will get junk.  

Oh..i got it. I do have a working bios. Thank God. And I generated the
irq_tables.c using getpir. It still doesn't help. 

One thing I did notice, it starts getting slow after mounting file
system. 

gin



From stepan at openbios.org  Thu Dec 16 21:07:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu Dec 16 21:07:00 2004
Subject: irq_tables.c
In-Reply-To: <000001c4e3fe$85c735c0$4f01060a@nexcom.com.tw>
References: <E8F8DBCB0468204E856114A2CD20741F390F45@mail.local.ActualitySystems.com> <000001c4e3fe$85c735c0$4f01060a@nexcom.com.tw>
Message-ID: <20041217072638.GB28515@openbios.org>

* Gin <ginlin at nexcom.com.tw> [041217 07:06]:
> Oh..i got it. I do have a working bios. Thank God. And I generated the
> irq_tables.c using getpir. It still doesn't help. 

You might have to adjust bus numbers. LinuxBIOS uses a different bus
enumeration than other boards on some systems

> One thing I did notice, it starts getting slow after mounting file
> system. 

is dma enabled?

Stefan




From sagivy at 3vium.com  Fri Dec 17 00:39:01 2004
From: sagivy at 3vium.com (Sagiv Yefet)
Date: Fri Dec 17 00:39:01 2004
Subject: Running with VGA
Message-ID: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB228AB6@cronos.trivium>

I try to build freebios2-20041216-0400
And I get this compilation error:
 
gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux
-gnu/bin/ld: section .reset [fffdfff0 -> fffdffff] overlaps section .rom
[fffd88c1 -> fffe0d7f]
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux
-gnu/bin/ld: section .id [fffdffd9 -> fffdffef] overlaps section .rom
[fffd88c1 -> fffe0d7f]
collect2: ld returned 1 exit status
make: *** [linuxbios] Error 1
 
What do you think it is?
 
Sagiv.
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, December 16, 2004 4:57 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I commit the changes for you. Please check it out from
 
http://snapshots.linuxbios.org/
 
one hour later.
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Wednesday, December 15, 2004 12:09 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running
with console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041217/c80b4294/attachment.html>

From stepan at openbios.org  Fri Dec 17 00:52:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Fri Dec 17 00:52:01 2004
Subject: Running with VGA
In-Reply-To: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB228AB6@cronos.trivium>
References: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB228AB6@cronos.trivium>
Message-ID: <20041217111142.GA31368@openbios.org>

* Sagiv Yefet <sagivy at 3vium.com> [041217 12:05]:
> I try to build freebios2-20041216-0400
> And I get this compilation error:
>  
> -gnu/bin/ld: section .id [fffdffd9 -> fffdffef] overlaps section .rom
> [fffd88c1 -> fffe0d7f]
>  
> What do you think it is?

Your ROM_IMAGE_SIZE is too small..

 Stefan



From rminnich at lanl.gov  Fri Dec 17 05:33:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 17 05:33:01 2004
Subject: irq_tables.c
In-Reply-To: <000001c4e3fe$85c735c0$4f01060a@nexcom.com.tw>
References: <000001c4e3fe$85c735c0$4f01060a@nexcom.com.tw>
Message-ID: <Pine.LNX.4.58.0412170851350.10747@linux.site>


On Fri, 17 Dec 2004, Gin wrote:

> One thing I did notice, it starts getting slow after mounting file
> system. 

I would guess that means 'after I start /sbin/init'. 

Can you do this:
boot with init=/bin/bash
which will get you an immediate shell prompt. Then do some looking around 
in that mode. 

ron


From rminnich at lanl.gov  Fri Dec 17 05:40:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 17 05:40:00 2004
Subject: irq_tables.c
In-Reply-To: <20041217072638.GB28515@openbios.org>
References: <E8F8DBCB0468204E856114A2CD20741F390F45@mail.local.ActualitySystems.com>
 <000001c4e3fe$85c735c0$4f01060a@nexcom.com.tw> <20041217072638.GB28515@openbios.org>
Message-ID: <Pine.LNX.4.58.0412170852400.10747@linux.site>


On Fri, 17 Dec 2004, Stefan Reinauer wrote:

> * Gin <ginlin at nexcom.com.tw> [041217 07:06]:
> > Oh..i got it. I do have a working bios. Thank God. And I generated the
> > irq_tables.c using getpir. It still doesn't help. 
> 
> You might have to adjust bus numbers. LinuxBIOS uses a different bus
> enumeration than other boards on some systems

once you get up in init=/bin/bash mode, do an lspci.

ron


From YhLu at tyan.com  Fri Dec 17 07:25:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri Dec 17 07:25:00 2004
Subject: Running with VGA
Message-ID: <3174569B9743D511922F00A0C943142307290BFC@TYANWEB>

In the targest/tyan/s2850/Config.lb
Change
                option ROM_IMAGE_SIZE=0x10000
to
        option ROM_IMAGE_SIZE=0x11800
        option XIP_ROM_SIZE=0x20000
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Friday, December 17, 2004 3:05 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I try to build freebios2-20041216-0400
And I get this compilation error:
 
gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu
/bin/ld: section .reset [fffdfff0 -> fffdffff] overlaps section .rom
[fffd88c1 -> fffe0d7f]
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu
/bin/ld: section .id [fffdffd9 -> fffdffef] overlaps section .rom [fffd88c1
-> fffe0d7f]
collect2: ld returned 1 exit status
make: *** [linuxbios] Error 1
 
What do you think it is?
 
Sagiv.
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, December 16, 2004 4:57 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I commit the changes for you. Please check it out from
 
http://snapshots.linuxbios.org/ <http://snapshots.linuxbios.org/> 
 
one hour later.
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Wednesday, December 15, 2004 12:09 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running with
console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041217/3ad20465/attachment.html>

From rminnich at lanl.gov  Fri Dec 17 07:33:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 17 07:33:00 2004
Subject: Running with VGA [PMX:#]
In-Reply-To: <3174569B9743D511922F00A0C943142307290BFC@TYANWEB>
References: <3174569B9743D511922F00A0C943142307290BFC@TYANWEB>
Message-ID: <Pine.LNX.4.58.0412171051090.10747@linux.site>


On Fri, 17 Dec 2004, YhLu wrote:

> In the targest/tyan/s2850/Config.lb
> Change
>                 option ROM_IMAGE_SIZE=0x10000
> to
>         option ROM_IMAGE_SIZE=0x11800
>         option XIP_ROM_SIZE=0x20000


actually, if you are modifying a Config.lb, it is always best to make your 
own. 

cp targets/tyan/s2850/Config.lb targets/tyan/s2850/Config.mine.lb

then change Config.mine.lb

then
./buildtarget tyan/s2850/Config.mine.lb

Then you can make sure you changes won't go away.

ron


From YhLu at tyan.com  Fri Dec 17 10:54:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri Dec 17 10:54:00 2004
Subject: collapsing devices.
Message-ID: <3174569B9743D511922F00A0C943142307290C13@TYANWEB>

Just commit.

Two ways calling 

In auto.c

#if 0
	// You need to preset bus num in PCI_DEV(0, 0x18,1) 0xe0, 0xe4,
0xe8, 0xec
        needs_reset |= ht_setup_chains(2);
#else
	// automatically set that for you, but you might meet tight space
        needs_reset |= ht_setup_chains_x();
#endif

YH

non coherent ht chain setup automatically
CVS: ----------------------------------------------------------------------
CVS: Enter Log.  Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS:    incoherent_ht.c
CVS: ----------------------------------------------------------------------



From adam at cfar.umd.edu  Fri Dec 17 14:11:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri Dec 17 14:11:00 2004
Subject: i845GB MB progress
In-Reply-To: <20041117122310.I84271-100000@www.missl.cs.umd.edu>
References: <20041117122310.I84271-100000@www.missl.cs.umd.edu>
Message-ID: <Pine.BSF.4.61.0412171948190.11879@www.missl.cs.umd.edu>

>> forget post codes under linux. port 80 is used for io delays there.
>
> no kidding.
>
> and I was looking for some ready-to-use delay loop to hold stuff after
> using port 80.
>
> either way ended up using serial port

actually, is linux actually writing to those ports?

I have been here looking over an LK book and it mentions that the delay is 
being done by _reading_ only those ports, not writing.

It also mentions that jumps were used before. It would be worthwhile to 
re-examine the delays used in IDE driver in ADLO code. And change it to 
perhaps reading the port 0x80. It could potentially make it more reliable.


From rminnich at lanl.gov  Fri Dec 17 17:49:00 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Dec 17 17:49:00 2004
Subject: i845GB MB progress
In-Reply-To: <Pine.BSF.4.61.0412171948190.11879@www.missl.cs.umd.edu>
References: <20041117122310.I84271-100000@www.missl.cs.umd.edu>
 <Pine.BSF.4.61.0412171948190.11879@www.missl.cs.umd.edu>
Message-ID: <Pine.LNX.4.58.0412172107300.11929@linux.site>


On Fri, 17 Dec 2004, Adam Sulmicki wrote:

> actually, is linux actually writing to those ports?

yes it is. 

Just watch a post card when linux is running. 

ron


From adam at cfar.umd.edu  Sat Dec 18 07:27:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Sat Dec 18 07:27:01 2004
Subject: i845GB MB progress
In-Reply-To: <Pine.LNX.4.58.0412172107300.11929@linux.site>
References: <20041117122310.I84271-100000@www.missl.cs.umd.edu>
 <Pine.BSF.4.61.0412171948190.11879@www.missl.cs.umd.edu>
 <Pine.LNX.4.58.0412172107300.11929@linux.site>
Message-ID: <Pine.BSF.4.61.0412181305450.11879@www.missl.cs.umd.edu>

>> actually, is linux actually writing to those ports?
> yes it is.
> Just watch a post card when linux is running.

well it boots fast, so it is hard to tell what is debug what's wait loops

Adam,
who probably just should RTFS


From juha.anon at chello.se  Sat Dec 18 13:12:00 2004
From: juha.anon at chello.se (Juha Anon)
Date: Sat Dec 18 13:12:00 2004
Subject: How about using LinuxBIOS for WakeUp
Message-ID: <41C4BDE8.20509@chello.se>

I'm woundering if LinuxBIOS would be a good basis for a wakeup mechanism 
for a Home Theater PC (HTPC).

The general idea is that the computer should be in standby until the 
time when a recording is scheduled. Then it would boot up and do it's 
job; and then go back to standby again. The reason for not having the PC 
running is partly because a HTPC is in the living room and we dont want 
to have the noice it makes when running. It is also nice to save all 
that power...

Another use of this is to wake the PC up when something happens -- like 
a mail arrives. Then it would run a spam filter and turn on a 
notification of some kind if the message wasn't spam. Perhaps LinuxBIOS 
could be running and listen for the event and not boot up further until 
it's needed.

I havn't been studing the LinuxBIOS yet, so I don't really know if this 
is a viable idea or not. Is it?

    -- Juha


From sagivy at 3vium.com  Sun Dec 19 00:00:01 2004
From: sagivy at 3vium.com (Sagiv Yefet)
Date: Sun Dec 19 00:00:01 2004
Subject: Running with VGA
Message-ID: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB22D6CF@cronos.trivium>

Great, It solved the problem.
About the etherboot I try to run with 5.2.6 version as you said (enable
BTEXT) and It is not working.
It stack in:  Jumping to LinuxBIOS
When I use the 5.2.5 version that you sent me before It work.
Command: Make bin/r8169.zelf
 
Now the elf image is loading and there is no respond from the VGA.. 
The kernel parameter is: console=tty0.
Maybe I didn't patch the kernel with the correct patch file.
Where can I get the patch of the kernel supporting ATI Ragexl?
 I am using 2.4.24 kernel version.
 
Thanks,
Sagiv
 
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Friday, December 17, 2004 7:53 PM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
In the targest/tyan/s2850/Config.lb
Change
                option ROM_IMAGE_SIZE=0x10000
to
        option ROM_IMAGE_SIZE=0x11800
        option XIP_ROM_SIZE=0x20000
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Friday, December 17, 2004 3:05 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I try to build freebios2-20041216-0400
And I get this compilation error:
 
gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux
-gnu/bin/ld: section .reset [fffdfff0 -> fffdffff] overlaps section .rom
[fffd88c1 -> fffe0d7f]
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux
-gnu/bin/ld: section .id [fffdffd9 -> fffdffef] overlaps section .rom
[fffd88c1 -> fffe0d7f]
collect2: ld returned 1 exit status
make: *** [linuxbios] Error 1
 
What do you think it is?
 
Sagiv.
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, December 16, 2004 4:57 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I commit the changes for you. Please check it out from
 
http://snapshots.linuxbios.org/
 
one hour later.
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Wednesday, December 15, 2004 12:09 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running
with console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041219/2a6ba05d/attachment.html>

From talbotx at comcast.net  Sun Dec 19 06:12:01 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Sun Dec 19 06:12:01 2004
Subject: Vga bios?
Message-ID: <001e01c4e5e8$419f9f90$9901a8c0@newflame>

If i have the rom image for the graphics card rom, can I load that into linuxbios?
-Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041219/70e4b503/attachment.html>

From ginlin at nexcom.com.tw  Sun Dec 19 19:53:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Sun Dec 19 19:53:00 2004
Subject: booting slow aftering mouting root
In-Reply-To: <Pine.LNX.4.58.0412170851350.10747@linux.site>
Message-ID: <000201c4e65a$e076e570$4f01060a@nexcom.com.tw>

I compare 2 output of linux command "pci"
from both Linuxbios booted linux and a regular bios booted linux. 
There are no IRQ assignments for lots of devices including IDE
controller, SMBUS.
Does linuxbios assign IRQs at all in the code?


==========================
Linuxbios
==========================
Bus  0, device  31, function  1:
    IDE interface: Intel Corp. 82801CA IDE U100 (rev 2).
      I/O at 0x3080 [0x308f].
      Non-prefetchable 32 bit memory at 0xfe601000 [0xfe6013ff].
  Bus  0, device  31, function  3:
    SMBus: Intel Corp. 82801CA/CAM SMBus (rev 2).
      I/O at 0x3060 [0x307f].





=============================
regular bios 
============================
Bus  0, device  31, function  1:
    IDE interface: Intel Corp. 82801CA IDE U100 (rev 2).
      IRQ 12.
      I/O at 0xf000 [0xf00f].
      Non-prefetchable 32 bit memory at 0x3fff0000 [0x3fff03ff].
Bus  0, device  31, function  3:
    SMBus: Intel Corp. 82801CA/CAM SMBus (rev 2).
      IRQ 5.
      I/O at 0x500 [0x51f].




From rminnich at lanl.gov  Mon Dec 20 06:40:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Dec 20 06:40:01 2004
Subject: How about using LinuxBIOS for WakeUp
In-Reply-To: <41C4BDE8.20509@chello.se>
References: <41C4BDE8.20509@chello.se>
Message-ID: <Pine.LNX.4.58.0412201000000.18682@linux.site>

I think your ideas are viable, it just needs someone to do 'em :-)

ron



From YhLu at tyan.com  Mon Dec 20 08:04:00 2004
From: YhLu at tyan.com (YhLu)
Date: Mon Dec 20 08:04:00 2004
Subject: Running with VGA
Message-ID: <3174569B9743D511922F00A0C943142307290C75@TYANWEB>

Please get the Etherboot 5.2.6.
 
You need to use patch for 2.4.22 and only enable ati rage xl framebuffer.
 
Regards
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Sunday, December 19, 2004 2:27 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
Great, It solved the problem.
About the etherboot I try to run with 5.2.6 version as you said (enable
BTEXT) and It is not working.
It stack in:  Jumping to LinuxBIOS
When I use the 5.2.5 version that you sent me before It work.
Command: Make bin/r8169.zelf
 
Now the elf image is loading and there is no respond from the VGA.. 
The kernel parameter is: console=tty0.
Maybe I didn't patch the kernel with the correct patch file.
Where can I get the patch of the kernel supporting ATI Ragexl?
 I am using 2.4.24 kernel version.
 
Thanks,
Sagiv
 
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Friday, December 17, 2004 7:53 PM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
In the targest/tyan/s2850/Config.lb
Change
                option ROM_IMAGE_SIZE=0x10000
to
        option ROM_IMAGE_SIZE=0x11800
        option XIP_ROM_SIZE=0x20000
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Friday, December 17, 2004 3:05 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I try to build freebios2-20041216-0400
And I get this compilation error:
 
gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu
/bin/ld: section .reset [fffdfff0 -> fffdffff] overlaps section .rom
[fffd88c1 -> fffe0d7f]
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu
/bin/ld: section .id [fffdffd9 -> fffdffef] overlaps section .rom [fffd88c1
-> fffe0d7f]
collect2: ld returned 1 exit status
make: *** [linuxbios] Error 1
 
What do you think it is?
 
Sagiv.
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, December 16, 2004 4:57 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I commit the changes for you. Please check it out from
 
http://snapshots.linuxbios.org/ <http://snapshots.linuxbios.org/> 
 
one hour later.
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Wednesday, December 15, 2004 12:09 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running with
console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041220/10d8a774/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.4.22-offical-aty_nobiosinit.patch
Type: application/octet-stream
Size: 43979 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041220/10d8a774/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.6.5-offcial-mach64.diff.gz
Type: application/octet-stream
Size: 47435 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041220/10d8a774/attachment-0001.obj>

From bari at onelabs.com  Mon Dec 20 15:15:01 2004
From: bari at onelabs.com (Bari Ari)
Date: Mon Dec 20 15:15:01 2004
Subject: Another LinuxBIOS Laptop Candidate?
Message-ID: <41C77E5B.3000709@onelabs.com>

<$500 Laptop at Walmart

http://linux.slashdot.org/article.pl?sid=04/12/20/2314235&tid=163&tid=184&tid=90&tid=106

http://www.walmart.com/catalog/product.gsp?product_id=3504708&cat=179113&type=19&dept=3944

-Bari



From YhLu at tyan.com  Tue Dec 21 08:06:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue Dec 21 08:06:01 2004
Subject: K8 Routing Table.
Message-ID: <3174569B9743D511922F00A0C943142307290CFF@TYANWEB>

FYI.

I made some changes to coherent_ht.c to make it create RT dynamically.

If you like to check it, please let me know, and I would check it in.

YH


From stepan at openbios.org  Tue Dec 21 08:20:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue Dec 21 08:20:01 2004
Subject: K8 Routing Table.
In-Reply-To: <3174569B9743D511922F00A0C943142307290CFF@TYANWEB>
References: <3174569B9743D511922F00A0C943142307290CFF@TYANWEB>
Message-ID: <20041221182907.GA17558@openbios.org>

* YhLu <YhLu at tyan.com> [041221 19:36]:
> FYI.
> 
> I made some changes to coherent_ht.c to make it create RT dynamically.
> 
> If you like to check it, please let me know, and I would check it in.
 
Sounds wonderful! Please go ahead!




From YhLu at tyan.com  Tue Dec 21 11:55:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue Dec 21 11:55:01 2004
Subject: K8 Routing Table.
Message-ID: <3174569B9743D511922F00A0C943142307290D21@TYANWEB>

Committed.

-----Original Message-----
From: Stefan Reinauer [mailto:stepan at openbios.org] 
Sent: Tuesday, December 21, 2004 10:29 AM
To: YhLu
Cc: 'Eric W. Biederman'; linuxbios at clustermatic.org
Subject: Re: K8 Routing Table.

* YhLu <YhLu at tyan.com> [041221 19:36]:
> FYI.
> 
> I made some changes to coherent_ht.c to make it create RT dynamically.
> 
> If you like to check it, please let me know, and I would check it in.
 
Sounds wonderful! Please go ahead!



From talbotx at comcast.net  Tue Dec 21 14:31:01 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Tue Dec 21 14:31:01 2004
Subject: No booting
Message-ID: <007601c4e7c0$501420d0$9901a8c0@newflame>

OK, Guys...
I am stuck on this one.
I have a Shuttle motherboard FV24 running a Via vt8604 chipset.  I have the system booting linux and have been tring to install linuxbios.  I can never get any output from the com port.  I have console redirect running in grub, so I no that part is running and good test point. My current config is just the epia config with an updated irq_tables.c.  I make the linuxbios.rom, clean compile, no errors.  I flash the system I get nothing.  No boot, no output from console, nothing....  What am I missing?
http://www.dslwebserver.com/main/fr_index.html?/main/shuttle-sv24-2.html

-Adam Talbot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041221/92fb0ee8/attachment.html>

From ginlin at nexcom.com.tw  Tue Dec 21 15:27:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Tue Dec 21 15:27:01 2004
Subject: No booting
In-Reply-To: <007601c4e7c0$501420d0$9901a8c0@newflame>
Message-ID: <000001c4e7c8$284e92d0$4f01060a@nexcom.com.tw>

>I can never get any output from the com port.  I have console redirect
running in grub, so I no that part is running and good test point. 
Your com port might not be turned on yet. Check your super IO. See if
it's the same with what your code is based on.
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041221/79ea1658/attachment.html>

From YhLu at tyan.com  Tue Dec 21 16:56:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue Dec 21 16:56:01 2004
Subject: K8 Routing Table.
Message-ID: <3174569B9743D511922F00A0C943142307290D4C@TYANWEB>

Committed change with broadcast and response table for 4p above system.

-----Original Message-----
From: YhLu 
Sent: Tuesday, December 21, 2004 2:25 PM
To: Stefan Reinauer
Cc: 'Eric W. Biederman'; linuxbios at clustermatic.org
Subject: RE: K8 Routing Table.

Committed.

-----Original Message-----
From: Stefan Reinauer [mailto:stepan at openbios.org] 
Sent: Tuesday, December 21, 2004 10:29 AM
To: YhLu
Cc: 'Eric W. Biederman'; linuxbios at clustermatic.org
Subject: Re: K8 Routing Table.

* YhLu <YhLu at tyan.com> [041221 19:36]:
> FYI.
> 
> I made some changes to coherent_ht.c to make it create RT dynamically.
> 
> If you like to check it, please let me know, and I would check it in.
 
Sounds wonderful! Please go ahead!

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From rminnich at lanl.gov  Tue Dec 21 18:01:01 2004
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Dec 21 18:01:01 2004
Subject: Hi
In-Reply-To: <200412211317.iBLDH2L12762@nwn.definitive.org>
References: <200412211317.iBLDH2L12762@nwn.definitive.org>
Message-ID: <Pine.LNX.4.58.0412212121260.22540@linux.site>

Sorry about the spam from the jackass guys, I will try to see how this 
happened tomorrow.

ron


From ginlin at nexcom.com.tw  Tue Dec 21 22:13:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Tue Dec 21 22:13:00 2004
Subject: Merry X'mas
Message-ID: <000001c4e800$dce49b30$4f01060a@nexcom.com.tw>

Thanks for everyone's help this year. Wish you guys a wonderful holiday.

gin






From talbotx at comcast.net  Tue Dec 21 22:17:00 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Tue Dec 21 22:17:00 2004
Subject: No booting
References: <000001c4e7c8$284e92d0$4f01060a@nexcom.com.tw>
Message-ID: <008e01c4e801$04c00180$9901a8c0@newflame>

Humm, been looking over this board... Cant spot the super IO... Normally that is a very easy thing to ID. Any easy ways to find such things from the Linux command line? A quick googling turned up nothing.
-Adam
  ----- Original Message ----- 
  From: Gin 
  To: linuxbios at clustermatic.org 
  Sent: Tuesday, December 21, 2004 5:47 PM
  Subject: RE: No booting


  >I can never get any output from the com port.  I have console redirect running in grub, so I no that part is running and good test point. 

  Your com port might not be turned on yet. Check your super IO. See if it's the same with what your code is based on.

   

   

   

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041221/c551b592/attachment.html>

From smithbone69 at yahoo.com  Tue Dec 21 22:41:00 2004
From: smithbone69 at yahoo.com (Richard Smith)
Date: Tue Dec 21 22:41:00 2004
Subject: Vga bios?
In-Reply-To: <001e01c4e5e8$419f9f90$9901a8c0@newflame>
Message-ID: <20041222090142.59036.qmail@web54005.mail.yahoo.com>

--- Adam Talbot <talbotx at comcast.net> wrote:

> If i have the rom image for the graphics card rom,
> can I load that into linuxbios?

Maybe.

There are 2 methods of doing VGA bios with LB.  Both
of these methods are for v1. I can't speak for v2
since I haven't made the switch yet.

Method one is to enable the real mode IDT stuff that
sets up a 16 bit enviroment and jumps into the
vgabios.  I've attempted this but never took it far
enough to actually make it work.  Search the archives
for 'vgabios' or 'vga bios' and you should find lots
of posts describing what to set.

The second option and the one that I'm most familiar
with is using ADLO.  ADLO is a glue layer to the BIOS
used int the bochs project which attempts to set up a
legacy BIOS enviroment.

Using ADLO and Bochs, I've made LILO and several
vgabios's work under LinuxBios with our Intel 440bx
chipset.

What chipset are you using? 

--
Richard A Smith


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250


From adam at cfar.umd.edu  Wed Dec 22 07:17:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Wed Dec 22 07:17:00 2004
Subject: No booting
In-Reply-To: <008e01c4e801$04c00180$9901a8c0@newflame>
References: <000001c4e7c8$284e92d0$4f01060a@nexcom.com.tw>
 <008e01c4e801$04c00180$9901a8c0@newflame>
Message-ID: <Pine.BSF.4.61.0412221258240.53490@www.missl.cs.umd.edu>

> Humm, been looking over this board... Cant spot the super IO... Normally 
> that is a very easy thing to ID. Any easy ways to find such things from 
> the Linux command line? A quick googling turned up nothing.

i think it is part of your south bridge.. probably.



From talbotx at comcast.net  Wed Dec 22 09:30:01 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Wed Dec 22 09:30:01 2004
Subject: No booting
References: <000001c4e7c8$284e92d0$4f01060a@nexcom.com.tw> <008e01c4e801$04c00180$9901a8c0@newflame> <Pine.BSF.4.61.0412221258240.53490@www.missl.cs.umd.edu>
Message-ID: <00ac01c4e85f$697810f0$9901a8c0@newflame>

Grumble Grumble.... The super io is built into my southbridge VT82C686B... OK, i hope that via was lazy, I will try to compile with the vt1211 super io, hope that works.
-Adam

 
----- Original Message ----- 
From: "Adam Sulmicki" <adam at cfar.umd.edu>
To: "Adam Talbot" <talbotx at comcast.net>
Cc: "Gin" <ginlin at nexcom.com.tw>; <linuxbios at clustermatic.org>
Sent: Wednesday, December 22, 2004 9:58 AM
Subject: Re: No booting


> > Humm, been looking over this board... Cant spot the super IO... Normally 
> > that is a very easy thing to ID. Any easy ways to find such things from 
> > the Linux command line? A quick googling turned up nothing.
> 
> i think it is part of your south bridge.. probably.
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041222/e139a740/attachment.html>

From talbotx at comcast.net  Wed Dec 22 09:48:00 2004
From: talbotx at comcast.net (Adam Talbot)
Date: Wed Dec 22 09:48:00 2004
Subject: Vga bios?
References: <20041222090142.59036.qmail@web54005.mail.yahoo.com>
Message-ID: <00c601c4e861$f5712040$9901a8c0@newflame>

Humm  OK, the main point in asking the question was coming from the stand
point that it is easy to obtain a vga rom. Most standard bios images are
just a zip file.  There are tools on the web that allow one to unzip a bios
rom file and grab the rom for the graphics controller. This was an idea that
I was toying around with that I think could help the whole linuxbios group
of people. I am not at that part yet.  Both my board do not boot linux bios
yet.  The Pentium M board is not supported, yet.  The P3 board has the super
IO in the southbridge makeing life harder. When I get one of these board
booting linuxbios then I will be willing to try to get VGA bios running.
-Adam Talbot

----- Original Message ----- 
From: "Richard Smith" <smithbone69 at yahoo.com>
To: "Adam Talbot" <talbotx at comcast.net>; <linuxbios at clustermatic.org>
Sent: Wednesday, December 22, 2004 1:01 AM
Subject: Re: Vga bios?


>
> --- Adam Talbot <talbotx at comcast.net> wrote:
>
> > If i have the rom image for the graphics card rom,
> > can I load that into linuxbios?
>
> Maybe.
>
> There are 2 methods of doing VGA bios with LB.  Both
> of these methods are for v1. I can't speak for v2
> since I haven't made the switch yet.
>
> Method one is to enable the real mode IDT stuff that
> sets up a 16 bit enviroment and jumps into the
> vgabios.  I've attempted this but never took it far
> enough to actually make it work.  Search the archives
> for 'vgabios' or 'vga bios' and you should find lots
> of posts describing what to set.
>
> The second option and the one that I'm most familiar
> with is using ADLO.  ADLO is a glue layer to the BIOS
> used int the bochs project which attempts to set up a
> legacy BIOS enviroment.
>
> Using ADLO and Bochs, I've made LILO and several
> vgabios's work under LinuxBios with our Intel 440bx
> chipset.
>
> What chipset are you using?
>
> --
> Richard A Smith
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Easier than ever with enhanced search. Learn more.
> http://info.mail.yahoo.com/mail_250
>




From adam at cfar.umd.edu  Wed Dec 22 09:55:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Wed Dec 22 09:55:01 2004
Subject: Vga bios?
In-Reply-To: <00c601c4e861$f5712040$9901a8c0@newflame>
References: <20041222090142.59036.qmail@web54005.mail.yahoo.com>
 <00c601c4e861$f5712040$9901a8c0@newflame>
Message-ID: <Pine.BSF.4.61.0412221533180.53490@www.missl.cs.umd.edu>

On Wed, 22 Dec 2004, Adam Talbot wrote:

> Humm  OK, the main point in asking the question was coming from the stand
> point that it is easy to obtain a vga rom. Most standard bios images are
> just a zip file.  There are tools on the web that allow one to unzip a bios
> rom file and grab the rom for the graphics controller. This was an idea that

it is trivial to grab bios image. you just run 'dd' under linuxbios while 
booted from pcbios. In that way you don't have to wonder what they used to 
pack/compress the bios image.

what is tricky is that the vga bios usually expect to run in 16 bit mode 
and with some of pc bios routines available. There's Ollie's testvga, 
there's ADLO which both attemp to solve this issue.

> Both my board do not boot linux bios yet.

> When I get one of these board booting linuxbios then I will be willing 
> to try to get VGA bios running.

good idea.


From thomas at wehrspann.de  Thu Dec 23 10:14:01 2004
From: thomas at wehrspann.de (Thomas Wehrspann)
Date: Thu Dec 23 10:14:01 2004
Subject: How about using LinuxBIOS for WakeUp
In-Reply-To: <41C4BDE8.20509@chello.se>
References: <41C4BDE8.20509@chello.se>
Message-ID: <200412232134.58857.thomas@wehrspann.de>

On Sunday 19 December 2004 00:31, Juha Anon wrote:
> I'm woundering if LinuxBIOS would be a good basis for a wakeup mechanism 
> for a Home Theater PC (HTPC).
> 
There are three ways to wake up a computer and i think only one is working 
with LinuxBIOS.
1) An external hardware wakeup device is always working.
2) The program NVRAM-WakeUp uses the BIOS fuctions for wakeup and does not 
work with freebios1 (i can't use freebios2)
3) And if a ACPI based solution is working, i don't know, either.

Thomas


From YhLu at tyan.com  Thu Dec 23 10:53:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu Dec 23 10:53:00 2004
Subject: if in the chip/device block
Message-ID: <3174569B9743D511922F00A0C943142307290E03@TYANWEB>

Why followings can not pass the buildtarget
..
                end     
if CONFIG_MAX_PHYSICAL_CPUS>4
                chip northbridge/amd/amdk8
                        device pci 1c.0 on end
                        device pci 1c.0 on end
                        device pci 1c.0 on end
                        device pci 1c.1 on end
                        device pci 1c.2 on end
                        device pci 1c.3 on end
                end     
                chip northbridge/amd/amdk8
                        device pci 1d.0 on end
                        device pci 1d.0 on end
                        device pci 1d.0 on end
                        device pci 1d.1 on end
                        device pci 1d.2 on end
                        device pci 1d.3 on end
                end     
                chip northbridge/amd/amdk8
                        device pci 1e.0 on end
                        device pci 1e.0 on end
                        device pci 1e.0 on end
                        device pci 1e.1 on end
                        device pci 1e.2 on end
                        device pci 1e.3 on end
                end     
                chip northbridge/amd/amdk8
                        device pci 1f.0 on end
                        device pci 1f.0 on end
                        device pci 1f.0 on end
                        device pci 1f.1 on end
                        device pci 1f.2 on end
                        device pci 1f.3 on end
                end
end
        end # pci_domain


From sagivy at 3vium.com  Fri Dec 24 00:56:00 2004
From: sagivy at 3vium.com (Sagiv Yefet)
Date: Fri Dec 24 00:56:00 2004
Subject: Running with VGA
Message-ID: <4A3D5F6DC9406A4DBE93D9BA8F07E4BB228AB9@cronos.trivium>

            I get 5.2.6 but the vga stack when reachs:
 
Jumping to boot code at 0x20000
 
I enable btext.
 
Sagiv
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Monday, December 20, 2004 8:34 PM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
Please get the Etherboot 5.2.6.
 
You need to use patch for 2.4.22 and only enable ati rage xl
framebuffer.
 
Regards
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Sunday, December 19, 2004 2:27 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
Great, It solved the problem.
About the etherboot I try to run with 5.2.6 version as you said (enable
BTEXT) and It is not working.
It stack in:  Jumping to LinuxBIOS
When I use the 5.2.5 version that you sent me before It work.
Command: Make bin/r8169.zelf
 
Now the elf image is loading and there is no respond from the VGA.. 
The kernel parameter is: console=tty0.
Maybe I didn't patch the kernel with the correct patch file.
Where can I get the patch of the kernel supporting ATI Ragexl?
 I am using 2.4.24 kernel version.
 
Thanks,
Sagiv
 
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Friday, December 17, 2004 7:53 PM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
In the targest/tyan/s2850/Config.lb
Change
                option ROM_IMAGE_SIZE=0x10000
to
        option ROM_IMAGE_SIZE=0x11800
        option XIP_ROM_SIZE=0x20000
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Friday, December 17, 2004 3:05 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I try to build freebios2-20041216-0400
And I get this compilation error:
 
gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux
-gnu/bin/ld: section .reset [fffdfff0 -> fffdffff] overlaps section .rom
[fffd88c1 -> fffe0d7f]
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux
-gnu/bin/ld: section .id [fffdffd9 -> fffdffef] overlaps section .rom
[fffd88c1 -> fffe0d7f]
collect2: ld returned 1 exit status
make: *** [linuxbios] Error 1
 
What do you think it is?
 
Sagiv.
-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, December 16, 2004 4:57 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I commit the changes for you. Please check it out from
 
http://snapshots.linuxbios.org/
 
one hour later.
 
YH
 
  _____  

From: Sagiv Yefet [mailto:sagivy at 3vium.com] 
Sent: Wednesday, December 15, 2004 12:09 AM
To: YhLu; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
I have this definition in targets/tyan/s2850/Config.lb:
option CONFIG_CONSOLE_BTEXT=1
Not default as you wrote.
Is it ok? 
 
Should I had the same thing in src/mainboard/tyan/s2850/Config.lb? 
 
Sagiv.
 
 
 
 
-----Original Message-----
From: Yinghai Lu [mailto:yhlu at tyan.com] 
Sent: Monday, December 13, 2004 4:01 AM
To: Sagiv Yefet; linuxbios at clustermatic.org
Subject: RE: Running with VGA
 
You need to add
 
uses CONFIG_CONSOLE_BTEXT
 
default CONFIG_CONSOLE_BTEXT=1
 
dir /drivers/ati/ragexl
 
after that you can get ouput in Linuxbios after vga init.
 
You also need to enable the btext in Etherboot. You should use Etherboot
5.2.6. it includes filo and btext console.
 
About kernel, you need to use kernel patch to enable ragexl frame buffer
support.
 
YH
 
  _____  

From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Sagiv Yefet
Sent: Sunday, December 12, 2004 5:23 AM
To: linuxbios at clustermatic.org
Subject: Running with VGA
 
Hello, 
            I am using Linux Bios on Tyan 2850. The machine is running
with console.
            I add to the command line: "console=ttyS0,115200" and I have
linux which runs with console.
            
How can I run with VGA? Should I add some code to the bios? 
 
            The VGA driver is: ATI Rage XL.
Sagiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041224/0ce5f984/attachment.html>

From zhushisongzhu at yahoo.com  Fri Dec 24 23:10:00 2004
From: zhushisongzhu at yahoo.com (zhu shi song)
Date: Fri Dec 24 23:10:00 2004
Subject: rtl8139 hangup
In-Reply-To: <20041224055600.27510.77452.Mailman@nwn.definitive.org>
Message-ID: <20041225093112.87634.qmail@web13204.mail.yahoo.com>

   Now I'm testing my i845 based MB intensively.  The
box is running with linux 2.4.28, linuxbios v1 and my
port supporting i845.  I have met one problem.  There
is no packet on NIC after six hours rtl8139 hangup.  I
can't ping other machine from linux box and can't ping
linux box from other machine either.  I unplugged RJ45
from NIC and plugged it again.  The rtl8139 returned
to normal. 
   Who know what cause the problem?  Is it related
with kernel, my linuxbios and i845 MB? 
   tks
   zhu


		
__________________________________ 
Do you Yahoo!? 
Jazz up your holiday email with celebrity designs. Learn more. 
http://celebrity.mail.yahoo.com


From cro_marmot at comcast.net  Sat Dec 25 07:26:01 2004
From: cro_marmot at comcast.net (David Hendricks)
Date: Sat Dec 25 07:26:01 2004
Subject: rtl8139 hangup
In-Reply-To: <20041225093112.87634.qmail@web13204.mail.yahoo.com>
References: <20041224055600.27510.77452.Mailman@nwn.definitive.org>
	<20041225093112.87634.qmail@web13204.mail.yahoo.com>
Message-ID: <20041225104657.0c9bd6a1@sunder>

I recall having a similar problem, though mine was with an Intel NIC
instead. A kernel update to 2.6.x seemed to fix it. You might want to
try a 2.6 kernel to see if that is the case with your NIC as well. If
so, then perhaps the newest Realtek driver can be back ported to your
2.4.28 kernel.

You also might want to make sure your kernel is set to use direct access
for PCI devices ( CONFIG_PCI_DIRECT=y ).

On Sat, 25 Dec 2004 01:31:12 -0800 (PST)
zhu shi song <zhushisongzhu at yahoo.com> wrote:

>    Now I'm testing my i845 based MB intensively.  The
> box is running with linux 2.4.28, linuxbios v1 and my
> port supporting i845.  I have met one problem.  There
> is no packet on NIC after six hours rtl8139 hangup.  I
> can't ping other machine from linux box and can't ping
> linux box from other machine either.  I unplugged RJ45
> from NIC and plugged it again.  The rtl8139 returned
> to normal. 
>    Who know what cause the problem?  Is it related
> with kernel, my linuxbios and i845 MB? 
>    tks
>    zhu
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Jazz up your holiday email with celebrity designs. Learn more. 
> http://celebrity.mail.yahoo.com
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios


From cro_marmot at comcast.net  Sat Dec 25 12:17:01 2004
From: cro_marmot at comcast.net (David Hendricks)
Date: Sat Dec 25 12:17:01 2004
Subject: Another LinuxBIOS Laptop Candidate?
In-Reply-To: <41C77E5B.3000709@onelabs.com>
References: <41C77E5B.3000709@onelabs.com>
Message-ID: <20041225153746.1ee902e5@sunder>

They look kind of like the EPIA-II boxes from a hardware standpoint. I
wonder if they have a removable flash...

On Mon, 20 Dec 2004 19:37:31 -0600
Bari Ari <bari at onelabs.com> wrote:

> <$500 Laptop at Walmart
> 
> http://linux.slashdot.org/article.pl?sid=04/12/20/2314235&tid=163&tid=184&tid=90&tid=106
> 
> http://www.walmart.com/catalog/product.gsp?product_id=3504708&cat=179113&type=19&dept=3944
> 
> -Bari
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios


From ollie at lanl.gov  Mon Dec 27 10:53:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Mon Dec 27 10:53:00 2004
Subject: vgabios.c and vgachip.h removed
Message-ID: <1104182068.3261.2.camel@logarithm.lanl.gov>

Hello,

Is there any one actually using the pc80/vgabios.c and pc80/vgachip.h?
The two files should not be in the pc80 directory because they have
too much via/epia dependence. I just removed these two files and
am working on porting the x86emu into LinuxBIOS.

Ollie




From smithbone69 at yahoo.com  Mon Dec 27 15:13:00 2004
From: smithbone69 at yahoo.com (Richard Smith)
Date: Mon Dec 27 15:13:00 2004
Subject: vgabios.c and vgachip.h removed
In-Reply-To: <1104182068.3261.2.camel@logarithm.lanl.gov>
Message-ID: <20041228013422.40594.qmail@web54007.mail.yahoo.com>

--- Li-Ta Lo <ollie at lanl.gov> wrote:

> am working on porting the x86emu into LinuxBIOS.
> 

Ollie,

You need to join forces with some of the developers on
the framebuffer list.  About 2 months ago a developer
from SciTech Soft (Who wrote and maintains a good
portion of x86emu) posted to the framebuffer
describing their port of x86emu to the linux kernel
and asking if the community was interested in
including it into general distribution.

This of course spawned a large debate.  I'll spare you
the details.

The short of the matter is that somebody did a lot of
work on reducing the size of the emulator and made a
huge difference by refactoring the layering on how the
instructions are emulated.

So its probally worth your while to go read the
framebuffer list archives and see if anything else
happened on that and ask for a copy since it already
has things like stdlib dependence removed.

Since bitworks.com died I haven't signed back up to
all  the mailing lists.

If you can't find it let me know and I'll dig up the
people you need to contact.

Richard.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From yhlu at tyan.com  Mon Dec 27 17:45:01 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Mon Dec 27 17:45:01 2004
Subject: vgabios.c and vgachip.h removed
In-Reply-To: <1104182068.3261.2.camel@logarithm.lanl.gov>
Message-ID: <200412272244.iBRMikL19287@nwn.definitive.org>

Ollie,

It seems that there some allocate resource for vga...stuff, and main focus
is to fix the mem io to some range and enable the io for vga.

For the first one, I suggest you to create one driver for the VGA device,
and it could override the read_resource of pci_read_resource to return fixed
mem resource.

Then the MB Config.lb could include the "driver ....."

Regards

YH

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Li-Ta Lo
Sent: Monday, December 27, 2004 1:14 PM
To: LinuxBIOS
Subject: vgabios.c and vgachip.h removed

Hello,

Is there any one actually using the pc80/vgabios.c and pc80/vgachip.h?
The two files should not be in the pc80 directory because they have
too much via/epia dependence. I just removed these two files and
am working on porting the x86emu into LinuxBIOS.

Ollie


_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From ginlin at nexcom.com.tw  Tue Dec 28 02:03:01 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Tue Dec 28 02:03:01 2004
Subject: PXE support
In-Reply-To: <20041101100508.GA12769@openbios.org>
Message-ID: <000001c4ecd8$3a8767a0$4f01060a@nexcom.com.tw>

>etherboot supports PXE. If you use etherboot as LB payload it should
>work. Never tried this though since I can't really recognize an
>advantage over the usual dhcp/tftpboot scenario. It's unlikely that you
>are able to use any driver like code on the network adapters without
>16bit bios.

I saw the Config options for PXE boot in Etherboot. Has anyone
successfully remote booted an image using PXE through Etherboot?

If so, what is the target name I should give to the makefile. I am not
sure how to build the file to use as the payload in Etherboot.


gin  



From ollie at lanl.gov  Wed Dec 29 07:57:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed Dec 29 07:57:01 2004
Subject: vgabios.c and vgachip.h removed
In-Reply-To: <200412280406.iBS46prT027569@proofpoint2.lanl.gov>
References: <200412280406.iBS46prT027569@proofpoint2.lanl.gov>
Message-ID: <1104344310.3143.5.camel@logarithm.lanl.gov>

On Mon, 2004-12-27 at 21:04, Yinghai Lu wrote:
> Ollie,
> 
> It seems that there some allocate resource for vga...stuff, and main focus
> is to fix the mem io to some range and enable the io for vga.
> 
> For the first one, I suggest you to create one driver for the VGA device,
> and it could override the read_resource of pci_read_resource to return fixed
> mem resource.
> 
> Then the MB Config.lb could include the "driver ....."
> 

I am doing that now. I just haven't committed that part yet. BTW, I 
don't think the current compute_allocate_resource can handle the
legacy vga mem resource (0xA0000-0xBFFFF) by modifying the
read_resource() of either the VGA device or K8 NB. I always got
strange allocation (like resources allocated near 1MB for other
devices). I guess the current K8/northbridge.c is the best thing
I can get.

Ollie




From daubin at actuality-systems.com  Wed Dec 29 10:05:00 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Wed Dec 29 10:05:00 2004
Subject: Memtest+
Message-ID: <E8F8DBCB0468204E856114A2CD20741F39117F@mail.local.ActualitySystems.com>

Hi,

  I'm trying to get memtest+ to fly on our system.  Problem is
That I don't have a console on my system.  I have USB and a video card,
But the video card bios isn't run since I run linuxbios.
  Can anyone please give me a hint as to how they've done it?

Thanks,
Dave


From YhLu at tyan.com  Wed Dec 29 11:34:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed Dec 29 11:34:01 2004
Subject: Memtest+
Message-ID: <3174569B9743D511922F00A0C943142307290F20@TYANWEB>

What's you motherboard...

If you are using btext_console, then you may need to add bcontext console
calling in memtest+, Please refer btext in Etherboot....

YH

-----Original Message-----
From: Dave Aubin [mailto:daubin at actuality-systems.com] 
Sent: Wednesday, December 29, 2004 12:27 PM
To: LinuxBIOS
Subject: Memtest+

Hi,

  I'm trying to get memtest+ to fly on our system.  Problem is
That I don't have a console on my system.  I have USB and a video card,
But the video card bios isn't run since I run linuxbios.
  Can anyone please give me a hint as to how they've done it?

Thanks,
Dave
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From daubin at actuality-systems.com  Wed Dec 29 11:37:59 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Wed Dec 29 11:37:59 2004
Subject: Memtest+
Message-ID: <E8F8DBCB0468204E856114A2CD20741F39118F@mail.local.ActualitySystems.com>

Hi,

  Home groan motherboard that does not have a serial connection
Due to cost concerns.  So using the serial line is out of the
Question.
  Has no one else hit this?  One idea I have being a PIC lover is
To use some LED's on the mother board and make a serial protocol 
Over the LED's, much like a software UART for a PIC.
  Anyone have an input on this? 

Thanks,
Dave

-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Wednesday, December 29, 2004 5:06 PM
To: Dave Aubin; LinuxBIOS
Subject: RE: Memtest+

What's you motherboard...

If you are using btext_console, then you may need to add bcontext
console calling in memtest+, Please refer btext in Etherboot....

YH

-----Original Message-----
From: Dave Aubin [mailto:daubin at actuality-systems.com]
Sent: Wednesday, December 29, 2004 12:27 PM
To: LinuxBIOS
Subject: Memtest+

Hi,

  I'm trying to get memtest+ to fly on our system.  Problem is That I
don't have a console on my system.  I have USB and a video card, But the
video card bios isn't run since I run linuxbios.
  Can anyone please give me a hint as to how they've done it?

Thanks,
Dave
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From ginlin at nexcom.com.tw  Wed Dec 29 19:44:00 2004
From: ginlin at nexcom.com.tw (Gin)
Date: Wed Dec 29 19:44:00 2004
Subject: flash rom utility
Message-ID: <003301c4ee35$a4af3640$4f01060a@nexcom.com.tw>

Is there a flash rom utility I can use to flash linuxbios to my EEPROM?
Currently I am WICE to do it. But I can't depend on a hardware device to
update bios.
 
gin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20041229/4585dd94/attachment.html>

From stuge-linuxbios at cdy.org  Thu Dec 30 08:35:00 2004
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Thu Dec 30 08:35:00 2004
Subject: Memtest+
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F39118F@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F39118F@mail.local.ActualitySystems.com>
Message-ID: <20041230185651.GA9845@foo.birdnet.se>

On Wed, Dec 29, 2004 at 04:58:57PM -0500, Dave Aubin wrote:
>   Has no one else hit this?  One idea I have being a PIC lover is
> To use some LED's on the mother board and make a serial protocol 
> Over the LED's, much like a software UART for a PIC.
>   Anyone have an input on this? 

That will work just fine, but watch out for running the "GPIO serial
bus" too fast for the PIC.

(With GPIO I'm referring to pins driving the LEDs on the target system,
not a PIC GPIO port.)

If simplex is fun enough, you could use a single GPIO pin and connect
that to RX on the PIC, connect TX on the PIC to a MAX232 and plug
that into a regular serial port on a PC running a terminal emulator.
All the PIC has to do then is read from RCREG and send everything
back out through TXREG. Any PIC with a USART in async mode should do
for this.

For duplex (etherboot/filo menu) you may need a separate GPIO pin for
flow control, the usual serial start/stop bit handshake may not be
very reliable without a hardware UART on the target system. The easy
solution is to use a synchronous serial interface instead; add a
clock signal driven by the target. This also overcomes any problems
caused by the PIC baud rate generator being controllable only with
relatively low precision.

The 16F87x series have both an MSSP and a USART; the MSSP could be
used in SPI Slave mode for duplex communication with the target
system, and the USART for talking to the PC running the terminal
emulator. One thing to keep in mind is that SPI always transmits data
in both directions, this means that the serial port wont be 8-bit
clean unless you make a small protocol to indicate when data actually
is available, this wastes twice the bandwidth, but may still be good
enough.

A USB device with a 16C745 or possibly 18F2550 if they can be sourced
is tempting, but that also requires writing some kind of driver for
the USB device, or figuring out how an existing USB<->serial adapter
works and reimplementing that. Too much work. Plus the 16C7x5 only do
low-speed USB.

Hope it works out though!


//Peter


From daubin at actuality-systems.com  Thu Dec 30 09:04:00 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Thu Dec 30 09:04:00 2004
Subject: Memtest+
Message-ID: <E8F8DBCB0468204E856114A2CD20741F3911CB@mail.local.ActualitySystems.com>

Nice read Peter, thank you for the info:)
Would be nice to use some voltage reference differencing
Instead of using a Max 232, but the Max is probably a cleaner approach.

A nerdy aside, I heard the 18F4550 and 18F2550 can run up to 12MIPs from
a 4MHz crystal, they've got a whopping 16K of flash, and they have a
Full-Speed USB v2.0 hardware.

Now if I could only run Linux on a PIC;)

Thanks,
Dave

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Peter Stuge
Sent: Thursday, December 30, 2004 1:57 PM
To: LinuxBIOS
Subject: Re: Memtest+

On Wed, Dec 29, 2004 at 04:58:57PM -0500, Dave Aubin wrote:
>   Has no one else hit this?  One idea I have being a PIC lover is To 
> use some LED's on the mother board and make a serial protocol Over the

> LED's, much like a software UART for a PIC.
>   Anyone have an input on this? 

That will work just fine, but watch out for running the "GPIO serial
bus" too fast for the PIC.

(With GPIO I'm referring to pins driving the LEDs on the target system,
not a PIC GPIO port.)

If simplex is fun enough, you could use a single GPIO pin and connect
that to RX on the PIC, connect TX on the PIC to a MAX232 and plug that
into a regular serial port on a PC running a terminal emulator.
All the PIC has to do then is read from RCREG and send everything back
out through TXREG. Any PIC with a USART in async mode should do for
this.

For duplex (etherboot/filo menu) you may need a separate GPIO pin for
flow control, the usual serial start/stop bit handshake may not be very
reliable without a hardware UART on the target system. The easy solution
is to use a synchronous serial interface instead; add a clock signal
driven by the target. This also overcomes any problems caused by the PIC
baud rate generator being controllable only with relatively low
precision.

The 16F87x series have both an MSSP and a USART; the MSSP could be used
in SPI Slave mode for duplex communication with the target system, and
the USART for talking to the PC running the terminal emulator. One thing
to keep in mind is that SPI always transmits data in both directions,
this means that the serial port wont be 8-bit clean unless you make a
small protocol to indicate when data actually is available, this wastes
twice the bandwidth, but may still be good enough.

A USB device with a 16C745 or possibly 18F2550 if they can be sourced is
tempting, but that also requires writing some kind of driver for the USB
device, or figuring out how an existing USB<->serial adapter works and
reimplementing that. Too much work. Plus the 16C7x5 only do low-speed
USB.

Hope it works out though!


//Peter
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From stuge-linuxbios at cdy.org  Thu Dec 30 09:32:01 2004
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Thu Dec 30 09:32:01 2004
Subject: off-topic: PIC and ETRAX [was: Memtest+]
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F3911CB@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F3911CB@mail.local.ActualitySystems.com>
Message-ID: <20041230195425.GA23406@foo.birdnet.se>

On Thu, Dec 30, 2004 at 02:25:47PM -0500, Dave Aubin wrote:
> Nice read Peter, thank you for the info:)

No problem!


> Would be nice to use some voltage reference differencing
> Instead of using a Max 232, but the Max is probably a cleaner
> approach.

The MAX232 is pretty common for connecting both PIC and AVR devices
to RS-232 equipment. It just needs a few external capacitors, which
is nice.


> A nerdy aside, I heard the 18F4550 and 18F2550 can run up to 12MIPs
> from a 4MHz crystal, they've got a whopping 16K of flash, and they
> have a Full-Speed USB v2.0 hardware.

Yep. And 2kb RAM. Check out the data sheet page 11 and chapter 2.
http://ww1.microchip.com/downloads/en/DeviceDoc/39632b.pdf


> Now if I could only run Linux on a PIC;)

Linux? That's for the ETRAX, made by Axis. Check out
http://developer.axis.com/

Everything-is-included Linux chip with 10/100 and both NOR and NAND
flash for boot as well as storage. They've ported the GNU toolchain
too.

I'm still waiting for some project where I can use the MCM and end up
with a few extra boards. :)


//Peter


From daubin at actuality-systems.com  Thu Dec 30 10:03:00 2004
From: daubin at actuality-systems.com (Dave Aubin)
Date: Thu Dec 30 10:03:00 2004
Subject: off-topic part 2: PIC and ETRAX [was: Memtest+]
Message-ID: <E8F8DBCB0468204E856114A2CD20741F3911D6@mail.local.ActualitySystems.com>

Again Peter, very nice:)

I will give you one more tid bit as it consumes less power than the
Axis, but still runs Linux and is quite small:)
Check out: http://www.brightstareng.com/
They have entire set ups on a form factor less than a credit card
Running Linux:)  Although it is still not a PIC, it is very good
For PIC type needs.

Thanks again,
Dave:)
 

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Peter Stuge
Sent: Thursday, December 30, 2004 2:54 PM
To: LinuxBIOS
Subject: Re: off-topic: PIC and ETRAX [was: Memtest+]

On Thu, Dec 30, 2004 at 02:25:47PM -0500, Dave Aubin wrote:
> Nice read Peter, thank you for the info:)

No problem!


> Would be nice to use some voltage reference differencing Instead of 
> using a Max 232, but the Max is probably a cleaner approach.

The MAX232 is pretty common for connecting both PIC and AVR devices to
RS-232 equipment. It just needs a few external capacitors, which is
nice.


> A nerdy aside, I heard the 18F4550 and 18F2550 can run up to 12MIPs 
> from a 4MHz crystal, they've got a whopping 16K of flash, and they 
> have a Full-Speed USB v2.0 hardware.

Yep. And 2kb RAM. Check out the data sheet page 11 and chapter 2.
http://ww1.microchip.com/downloads/en/DeviceDoc/39632b.pdf


> Now if I could only run Linux on a PIC;)

Linux? That's for the ETRAX, made by Axis. Check out
http://developer.axis.com/

Everything-is-included Linux chip with 10/100 and both NOR and NAND
flash for boot as well as storage. They've ported the GNU toolchain too.

I'm still waiting for some project where I can use the MCM and end up
with a few extra boards. :)


//Peter
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From bari at onelabs.com  Thu Dec 30 11:42:00 2004
From: bari at onelabs.com (Bari Ari)
Date: Thu Dec 30 11:42:00 2004
Subject: off-topic: PIC and ETRAX [was: Memtest+]
In-Reply-To: <20041230195425.GA23406@foo.birdnet.se>
References: <E8F8DBCB0468204E856114A2CD20741F3911CB@mail.local.ActualitySystems.com> <20041230195425.GA23406@foo.birdnet.se>
Message-ID: <41D47BEC.105@onelabs.com>

Peter Stuge wrote:

>>Now if I could only run Linux on a PIC;)
> 
> 
> Linux? That's for the ETRAX, made by Axis. Check out
> http://developer.axis.com/
> 
Also look at uClinux  http://www.uclinux.org/

We use it for dsp's and cpu's like PIC's that don't have mmu's.

-Bari



From hisheirs at bellsouth.net  Thu Dec 30 19:15:00 2004
From: hisheirs at bellsouth.net (hisheirs at bellsouth.net)
Date: Thu Dec 30 19:15:00 2004
Subject: thread here carring a payload
Message-ID: <20041231053706.HIBV1992.imf16aec.mail.bellsouth.net@mail.bellsouth.net>

mr admin .. 
 the following page is being used to deliver W32.Netsky.P at mm!enc
just thought you should know