>Long term I wish we had a better way to handle development before the
official
>product launch.
I think if I can keep pace with normal bios development, I can get updated
detail info from vendor and our BIOS engineers. Otherwise they may forget
some detail info and also some vendors may fail to u
"Yinghai Lu" <[EMAIL PROTECTED]> writes:
> The D0 is released last week. And Normal BIOS support it already.
>
> Thanks for your great job in raminit.c of K8 and others, and I add several
> lines to reflect the new mapping of memory bank.
Cool.
I am confused about what the current situation is.
Behalf Of Eric W.
Biederman
Sent: Saturday, December 04, 2004 4:12 PM
To: YhLu
Cc: [EMAIL PROTECTED]
Subject: Re: K8 D0 support
YhLu <[EMAIL PROTECTED]> writes:
> Opteron Rev D0 support done.
>
> So I need to wait for AMD put the updated Bios porting guide including
> Opteron Rev D
YhLu <[EMAIL PROTECTED]> writes:
> Opteron Rev D0 support done.
>
> So I need to wait for AMD put the updated Bios porting guide including
> Opteron Rev D0 info. Only after that, I can commit the patch?
> Or ask the AMD to review the code?
Essentially.
It all depends on your relationship. But
: Friday, December 03, 2004 6:24 PM
To: YhLu
Cc: Stefan Reinauer; [EMAIL PROTECTED]
Subject: Re: K8 D0 support
YhLu <[EMAIL PROTECTED]> writes:
> Eric,
>
> Are you working on Opteron D0 support? There are some memory
initialization
> changes to support D0...
It is on the near term
YhLu <[EMAIL PROTECTED]> writes:
> Eric,
>
> Are you working on Opteron D0 support? There are some memory initialization
> changes to support D0...
It is on the near term TODO list, as are way to many other
things. I need to make certain I have some so I can test with them.
My impression the bi
6 matches
Mail list logo