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
Am Sonntag, den 02.05.2010, 21:47 -0600 schrieb Marc Jones:
> I was just looking at the same thing. I don't like the MTRR
> manipulation that is happening in post_cache_as_ram.c. Doing 0-TOM is
> a little tricky if the dimms are different sizes. It is easier to let
It's one MTRR per DIMM, where ide
On Sun, May 2, 2010 at 4:45 PM, Rudolf Marek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Rudolf Marek wrote:
>> I found that in k8 CAR set_var_mtrr is set as it the arguments would be an
>> adresses, but in fact they HAVE TO be in kilobytes.
>
> Hi again,
>
> I re-checked and it w
On Sun, May 2, 2010 at 9:24 PM, Ed Swierk wrote:
> On Sun, May 2, 2010 at 3:45 PM, Rudolf Marek wrote:
>> I re-checked and it was OK, we do have an early function with same name which
>> takes bytes parameters (mtrr-early.c). So this is not the case. I
>> investigated
>> MTRRs bit more.
>
> I no
On Sun, May 2, 2010 at 3:45 PM, Rudolf Marek wrote:
> I re-checked and it was OK, we do have an early function with same name which
> takes bytes parameters (mtrr-early.c). So this is not the case. I investigated
> MTRRs bit more.
I noticed that too. Perhaps we should rename the early version to
On Sun, May 2, 2010 at 4:59 PM, Rudolf Marek 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 are easy t
On Fri, Apr 30, 2010 at 9:49 PM, Myles Watson wrote:
>
>> /* variable MTRRs */
>> msr 0200=
>> msr 0201=
>> msr 0202=fff6
>> msr 0203=fff80800
> This looks wrong to me. I'm not an expert, but Since 202 is the base, and
> 203 is
-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
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rudolf Marek wrote:
> I found that in k8 CAR set_var_mtrr is set as it the arguments would be an
> adresses, but in fact they HAVE TO be in kilobytes.
Hi again,
I re-checked and it was OK, we do have an early function with same name which
takes bytes
Stefan Reinauer wrote:
> On 5/2/10 5:00 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> Hello, when testing on QEMU I noticed that it always assumed 64 MiB RAM.
>> Fix attached. Tested from 16 MiB to 2047 MiB
>>
>>
> Hi Vladimir,
>
> please sign off your patch so we can commit it:
>
> http:/
On 5/2/10 5:00 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, when testing on QEMU I noticed that it always assumed 64 MiB RAM.
> Fix attached. Tested from 16 MiB to 2047 MiB
>
>
Hi Vladimir,
please sign off your patch so we can commit it:
http://www.coreboot.org/Development_Guideli
Hello, when testing on QEMU I noticed that it always assumed 64 MiB RAM.
Fix attached. Tested from 16 MiB to 2047 MiB
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
=== modified file 'src/mainboard/emulation/qemu-x86/northbridge.c'
--- src/mainboard/emulation/qemu-x86/northbridge.c 2010-04-08
Hello, I was playing with loading FreeBSD using grub2 as bootloader and
have met following problems:
1) FreeBSD-i386 makes BIOS calls. On coreboot they cause a crash.
I propose to restructure machdep.c to call int12 only if no smap is
supplied. Patch attached.
Abandon keyboard rate retrieving from
13 matches
Mail list logo
