Here is the code in C.
This code is simple enough to put into stage 2.
I will look at that next. People can check me on this code.
ron
/* Copyright (C) 2008 Vincent Legoll [EMAIL PROTECTED]
* Convert to c (C) 2008 Ronald G. Minnich [EMAIL PROTECTED]
*
* This program is free software; you
On Sat, Oct 11, 2008 at 2:53 PM, Vincent Legoll
[EMAIL PROTECTED] wrote:
and PCI IO address mask is 0x3FFF, right ?
I think so, unless it is 3fff3
Then we just need C code :-)
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
On Sat, Oct 11, 2008 at 11:45 PM, ron minnich [EMAIL PROTECTED] wrote:
On Sat, Oct 11, 2008 at 1:51 PM, Vincent Legoll
[EMAIL PROTECTED] wrote:
On Sat, Oct 11, 2008 at 10:31 PM, ron minnich [EMAIL PROTECTED] wrote:
That is really nice. Yes, now we just need it for config and io and
prefmem
On Sat, Oct 11, 2008 at 10:31 PM, ron minnich [EMAIL PROTECTED] wrote:
That is really nice. Yes, now we just need it for config and io and
prefmem space :-)
ron
You mean 0x80h to 0xECh ?
MMIO base / limit
PCI IO base / limit
Config base / limit
That's my next target...
I have questions,
On Sat, Oct 11, 2008 at 1:51 PM, Vincent Legoll
[EMAIL PROTECTED] wrote:
On Sat, Oct 11, 2008 at 10:31 PM, ron minnich [EMAIL PROTECTED] wrote:
That is really nice. Yes, now we just need it for config and io and
prefmem space :-)
ron
You mean 0x80h to 0xECh ?
MMIO base / limit
PCI IO base
On Sat, Oct 11, 2008 at 11:56 PM, ron minnich [EMAIL PROTECTED] wrote:
and PCI IO address mask is 0x3FFF, right ?
I think so, unless it is 3fff3
Yes, in the register, it is shifted by 3 bytes
Then we just need C code :-)
That is another story...
Here is the python script, I have tested it
That is really nice. Yes, now we just need it for config and io and
prefmem space :-)
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Would that be the kind of decoding you had in mind ?
0x80: Ox00E3 - Memory Mapped I/O Base 0
DRAM Base: 0x00E000
Read Enable: 0x1
Write Enable: 0x1
Interleave Enable: No interleave
0x84: Ox00EFFF80 - Memory Mapped I/O Limit 0
Dst Node ID: 0
On Sat, Oct 11, 2008 at 2:52 AM, ron minnich [EMAIL PROTECTED] wrote:
On Fri, Oct 10, 2008 at 5:06 PM, Vincent Legoll
[EMAIL PROTECTED] wrote:
Is that like what you had in mind:
This is 18:1 right?
yes
~ # ./AMDK8MemMap.py
0x00: Ox1022 - Device ID
0x02: Ox1101 - Vendor ID
0x04:
On Sat, Oct 11, 2008 at 7:31 AM, Peter Stuge [EMAIL PROTECTED] wrote:
ron minnich wrote:
This is a good start but what you are missing is the interpretation
of the fields and shifting things so we know what they really are.
This is exactly what msrtool does. I must apologize for letting it
don't forget -- at some point we need C functions I can plug into
coreboot directly so that we can have coreboot dump the state of the
world as it comes up. Very handy when you can't boot linux to run
python :-)
ron
--
coreboot mailing list: coreboot@coreboot.org
On Sat, Oct 11, 2008 at 8:36 AM, Vincent Legoll
[EMAIL PROTECTED] wrote:
On Sat, Oct 11, 2008 at 5:26 PM, ron minnich [EMAIL PROTECTED] wrote:
don't forget -- at some point we need C functions I can plug into
coreboot directly so that we can have coreboot dump the state of the
world as it
On Sat, Oct 11, 2008 at 5:26 PM, ron minnich [EMAIL PROTECTED] wrote:
don't forget -- at some point we need C functions I can plug into
coreboot directly so that we can have coreboot dump the state of the
world as it comes up. Very handy when you can't boot linux to run
python :-)
I'll finish
if anybody wants to dash this off today, we need it.
The utillity would read the routing registers in k8 north and print
out what they mean. You get this info from config space.
I wrote one of these for the ultra 40 project and then lost it when I
shipped the machine back to xtreme data ...
On Fri, Oct 10, 2008 at 5:18 PM, ron minnich [EMAIL PROTECTED] wrote:
if anybody wants to dash this off today, we need it.
The utillity would read the routing registers in k8 north and print
out what they mean. You get this info from config space.
Could you explain what you call routing
On Fri, Oct 10, 2008 at 11:37 AM, Vincent Legoll
[EMAIL PROTECTED] wrote:
On Fri, Oct 10, 2008 at 5:18 PM, ron minnich [EMAIL PROTECTED] wrote:
if anybody wants to dash this off today, we need it.
The utillity would read the routing registers in k8 north and print
out what they mean. You get
Is that like what you had in mind:
~ # ./AMDK8MemMap.py
0x00: Ox1022 - Device ID
0x02: Ox1101 - Vendor ID
0x04: Ox - Status
0x06: Ox - Command
0x08: Ox00 - Base CLass Code
0x09: Ox00 - Subclass Code
0x0a: Ox00 - Program Interface
0x0b: Ox06 -
On the same machine:
~ # lspci -vvvxxx -s 0:0:18.1
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Address Map
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr-
On Fri, Oct 10, 2008 at 5:06 PM, Vincent Legoll
[EMAIL PROTECTED] wrote:
Is that like what you had in mind:
This is 18:1 right?
~ # ./AMDK8MemMap.py
0x00: Ox1022 - Device ID
0x02: Ox1101 - Vendor ID
0x04: Ox - Status
0x06: Ox - Command
0x08: Ox00 - Base CLass
ron minnich wrote:
This is a good start but what you are missing is the interpretation
of the fields and shifting things so we know what they really are.
This is exactly what msrtool does. I must apologize for letting it
bitrot on my disk just because the two killer features weren't
20 matches
Mail list logo
