The attached patch does several fixes so the H8QME-2+ boards builds and boots successfully with Kconfig. I also corrected some issues regarding mptables.
/Signed-off-by: Knut Kujat knuku@gap.upv.es
---
/Thats all :)
thx, Knut Kujat
Am 24.02.2010 09:35, schrieb Knut Kujat:
The attached patch does several fixes so the H8QME-2+ boards builds and boots successfully with Kconfig. I also corrected some issues regarding mptables.
/Signed-off-by: Knut Kujat knuku@gap.upv.es
Acked-by: Patrick Georgi patrick.georgi@coresystems.de
Committed as r5154. I changed whitespace a bit, so it will probably conflict on your tree.
Thanks, Patrick
On 2/24/10 9:35 AM, Knut Kujat wrote:
The attached patch does several fixes so the H8QME-2+ boards builds and boots successfully with Kconfig. I also corrected some issues regarding mptables.
/Signed-off-by: Knut Kujat knuku@gap.upv.es
Wow... about a Megabyte of heap and 64kb stack? That's quite a lot... It will definitely break S3 as it's currently implemented (assumes that all of coreboot fits in 1MB, code, heap, stack)
Stefan
Stefan Reinauer escribió:
On 2/24/10 9:35 AM, Knut Kujat wrote:
The attached patch does several fixes so the H8QME-2+ boards builds and boots successfully with Kconfig. I also corrected some issues regarding mptables.
/Signed-off-by: Knut Kujat knuku@gap.upv.es
Wow... about a Megabyte of heap and 64kb stack? That's quite a lot... It will definitely break S3 as it's currently implemented (assumes that all of coreboot fits in 1MB, code, heap, stack)
Stefan
Hi,
the big heap is because of some experiments I was doing with some htx cards on one it told me at a certain point of the boot process that malloc failed so I started increasing the heap size until I was so annoyed about none of the values were working so I "aimed high" but without card I got it booting with heap size = 0xc000. So which value should go into the Kconfig file ? I guess 0xc000?!
Thx, Knut Kujat.
-
Knut Kujat -
Patrick Georgi -
Stefan Reinauer