Myles Watson escribió:
I think this can be problematic, since by the time you can dump the
factory
BIOS resource allocation has already occurred. The resource map is only
good for early initialization, before resource allocation, right?
hmm. I had always used the
Myles Watson escribió:
I think this can be problematic, since by the time you can dump the
factory
BIOS resource allocation has already occurred. The resource map is only
good for early initialization, before resource allocation, right?
hmm. I had always used the
My resource map sets:
DRAM mappings for each node
MMIO mappings for each HT chain
PCI IO mappings for each HT chain
PCI Bus numbers for each HT chain
Since all of your devices are on the same HT chain in your devicetree.cb, a
resourcemap should be pretty easy to do.
DRAM - All 0, but
-Original Message-
From: Knut Kujat [mailto:kn...@gap.upv.es]
Sent: Thursday, May 06, 2010 2:20 AM
To: Myles Watson
Cc: 'ron minnich'; 'coreboot'
Subject: Re: [coreboot] H8QME-2+ boot problems on different machines.
Myles Watson escribió:
I think this can be problematic
And for the Not so good working CPU:
AFTER setup_mb_resource
DRAM(40)00-ff, -(0), R, W, No interleave, 0
MMIO(80)00-00, -(0,0), , , CPU disable 0, Lock 0, Non
posted 0
MMIO(90)00-00, -(0,0), , , CPU disable 0, Lock 0, Non
posted 0
Hi,
I finally got it working, but I don't like my solution!
I noticed that after setup_mb_resource_map(); the board hang at outb
and inl instructions. So I commented it out to see how far this will
bring me. For my surprise the board booted right into Linux without
further problems. Now my
On Wed, May 5, 2010 at 12:39 AM, Knut Kujat kn...@gap.upv.es wrote:
- I now know that my resource map must be some kind of faulty. But why
does it work on one CPU and doesn't on another, complete identical, one?
It's not about the CPU, it is more about how the mainboard is wired
up. And, it is
I've had questions about resource maps too.
- I now know that my resource map must be some kind of faulty. But why
does it work on one CPU and doesn't on another, complete identical, one?
It's not about the CPU, it is more about how the mainboard is wired
up. And, it is not surprising
On Wed, May 5, 2010 at 7:44 AM, Myles Watson myle...@gmail.com wrote:
The reason he got to that conclusion was that the same motherboard boots
differently with a different CPU and the identical BIOS. I don't understand
how it could be a wiring issue.
I went back and managed to misunderstand
I think this can be problematic, since by the time you can dump the
factory
BIOS resource allocation has already occurred. The resource map is only
good for early initialization, before resource allocation, right?
hmm. I had always used the bios map as a starting point and it had
On 5/3/10 12:59 AM, Rudolf Marek wrote:
Hi,
There is a plenty of bugs as in all modern CPUs ;)
http://support.amd.com/us/Processor_TechDocs/41322.pdf
Quick look to coreboot shows they are not handled?
Some are easy to fix just to set some MSR, some are microcode fixes.
Thanks
Rudolf
I
Marc Jones escribió:
On Sun, May 2, 2010 at 4:59 PM, Rudolf Marek r.ma...@assembler.cz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
There is a plenty of bugs as in all modern CPUs ;)
http://support.amd.com/us/Processor_TechDocs/41322.pdf
Quick look to coreboot shows they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
There is a plenty of bugs as in all modern CPUs ;)
http://support.amd.com/us/Processor_TechDocs/41322.pdf
Quick look to coreboot shows they are not handled?
Some are easy to fix just to set some MSR, some are microcode fixes.
Thanks
Rudolf
On Sun, May 2, 2010 at 4:59 PM, Rudolf Marek r.ma...@assembler.cz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
There is a plenty of bugs as in all modern CPUs ;)
http://support.amd.com/us/Processor_TechDocs/41322.pdf
Quick look to coreboot shows they are not handled?
Some
Hi,
I now know that I'm having the same trouble Ward had with his h8dme board:
http://www.mail-archive.com/coreboot@coreboot.org/msg20923.html
Could anyone tell if and how he solved his problem?
Thanks,
Knut Kujat.
--
coreboot mailing list: coreboot@coreboot.org
Hi Knut,
On Fri, Apr 30, 2010 at 10:29:59AM +0200, Knut Kujat wrote:
I now know that I'm having the same trouble Ward had with his h8dme board:
http://www.mail-archive.com/coreboot@coreboot.org/msg20923.html
Could anyone tell if and how he solved his problem?
I have not. Unfortunately, I
Hi,
We 64 identical machines here for now I only tried to boot coreboot on
11 of them where 4 of them got this early hang.
I switched the bootstrap processor from a machine that fails and put it
into one that always boots with coreboot, now the machine which was
failing before now boots perfectly
On 4/30/10 6:26 PM, Knut Kujat wrote:
Hi,
We 64 identical machines here for now I only tried to boot coreboot on
11 of them where 4 of them got this early hang.
I switched the bootstrap processor from a machine that fails and put it
into one that always boots with coreboot, now the machine
Hi,
I have a strange problem trying to install/flash my Coreboot to several
machines in the cluster some worked just fine and other hang at a really
early moment.
The machines are identical: H8QME-2+ with 16 GB RAM and 4 quadcore AMD
Opterons 8350.
I guess that from the point where it hangs that
19 matches
Mail list logo
