-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> are you sure? I ask because what i am doing on LX (that worked) is to
> enable the cache, copy the stack back over itself, and then wbinvd. It
> worked well, I think it might work on k8.
That what I wrote was from AMD documentation (pre family F)
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl-Daniel Hailfinger wrote:
> On 12.01.2008 01:18, Rudolf Marek wrote:
>> Imho you must copy the data from CAR, because when it is OFF, no
>> writeback is
>> done to memory: (from BKDG)
>>
>> Temporary data stored in the cache during boot cannot be w
On 12.01.2008 02:23, ron minnich wrote:
> On Jan 11, 2008 5:10 PM, Carl-Daniel Hailfinger
> <[EMAIL PROTECTED]> wrote:
>
>
>> Do you want CAR to start at 0x8 and end at 0x87FFF
>>
>
> Oh shoot, I just realized, on LX it goes from 88000 to 88fff. But it
> doesn't matter that much. 8
On Jan 11, 2008 5:10 PM, Carl-Daniel Hailfinger
<[EMAIL PROTECTED]> wrote:
> Do you want CAR to start at 0x8 and end at 0x87FFF
Oh shoot, I just realized, on LX it goes from 88000 to 88fff. But it
doesn't matter that much. 8 to 87fff is fine too.
ron
--
linuxbios mailing list
linuxbios
On 12.01.2008 01:45, ron minnich wrote:
> For reference here is the geode lx disable car. CAR is at 8. The
> steps are to re-enable cache (for loop), then dirty all the tags for
> the CAR area (cld; rep movsl; etc); then write it all back (wbinvd).
>
> Works really well.
>
> for (i = 0;
For reference here is the geode lx disable car. CAR is at 8. The
steps are to re-enable cache (for loop), then dirty all the tags for
the CAR area (cld; rep movsl; etc); then write it all back (wbinvd).
Works really well.
for (i = 0; i < ARRAY_SIZE(msr_table); i++)
wrm
On Jan 11, 2008 4:33 PM, Carl-Daniel Hailfinger
<[EMAIL PROTECTED]> wrote:
> On 12.01.2008 01:18, Rudolf Marek wrote:
> > Temporary data stored in the cache during boot cannot be written back
> > to DRAM
> > after enabling the
> > DRAM controller using a CLFLUSH or WBINVB instruction. The cache sh
On Jan 11, 2008 4:35 PM, Carl-Daniel Hailfinger
<[EMAIL PROTECTED]> wrote:
> One zero too many? Your location would be 8 MB. That is impossible
> according to the BKDG.
yes, my mistake.
ron
>
> > Be advised that car on older opterons is a bit tricky, due to
> > limitations in the hardware. I ca
On 12.01.2008 01:25, ron minnich wrote:
> On Jan 11, 2008 4:13 PM, Carl-Daniel Hailfinger
> <[EMAIL PROTECTED]> wrote:
>
>
>> Ron, where would you like to have the CAR area to avoid copying the
>> stack around in v2? Any places where stack location is hardcoded without
>> using the usual #define
On 12.01.2008 01:18, Rudolf Marek wrote:
> Imho you must copy the data from CAR, because when it is OFF, no
> writeback is
> done to memory: (from BKDG)
>
> Temporary data stored in the cache during boot cannot be written back
> to DRAM
> after enabling the
> DRAM controller using a CLFLUSH or WBIN
On Jan 11, 2008 4:13 PM, Carl-Daniel Hailfinger
<[EMAIL PROTECTED]> wrote:
> Ron, where would you like to have the CAR area to avoid copying the
> stack around in v2? Any places where stack location is hardcoded without
> using the usual #define?
>
If you could put it at x80 that would work v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Imho you must copy the data from CAR, because when it is OFF, no writeback is
done to memory: (from BKDG)
Temporary data stored in the cache during boot cannot be written back to DRAM
after enabling the
DRAM controller using a CLFLUSH or WBINVB i
Hi,
I'm currently considering to completely ignore what the BKDG says about
CAR and change the AMD CAR code to 64k size at an *arbitrary* address.
Right. Any address of your choice as long as it is below 1 MB.
A few rules, though: If you want the CAR area to reside below 0x8
(512k), you have t
13 matches
Mail list logo
