[LinuxBIOS] issue 25: amd k8 microcode support

[Ronald G Minnich]

I have committed this. It was waiting too long. It caused no problems 
for building arima/hdama once I corrected a few typos.
Signed-off-by: Ronald G. Minnich

let me know if there are troubles. Will the first person to test this on 
real hardware please change status to resolved, instead of testing.

Stefan, can we have status items of 'builds ok'? It would help.

thanks

ron

[Li-Ta Lo]

On Tue, 2005-11-22 at 16:45 -0700, Ronald G Minnich wrote:
> I have committed this. It was waiting too long. It caused no problems 
> for building arima/hdama once I corrected a few typos.
> Signed-off-by: Ronald G. Minnich

Did you actually committed it? From the web page, the latest patch level
is 2091 which is the FSF address. SVN update shows the same thing.
> let me know if there are troubles. Will the first person to test this on 
> real hardware please change status to resolved, instead of testing.

Does this include the apid id stuff as well? AFIAK we need at least
a function in that patch to compile Tyan boards.
> Stefan, can we have status items of 'builds ok'? It would help.
>
> thanks
>
> ron

[ron minnich]

On 11/22/05, Li-Ta Lo  wrote:
> Did you actually committed it? From the web page, the latest patch level
> is 2091 which is the FSF address. SVN update shows the same thing.

my mistake, and thanks, ollie. It is now commited.
> Does this include the apid id stuff as well? AFIAK we need at least
> a function in that patch to compile Tyan boards.

this is purely the microcode patch.

thanks

ron

[Li-Ta Lo]

> > Does this include the apid id stuff as well? AFIAK we need at least
> > a function in that patch to compile Tyan boards.
>
> this is purely the microcode patch.

I will try to find out the get_apic_id() patch and commit it.
Without it, none of the Tyan targets can be built.

BTW, I have a minor change to the mptable.c for s2881, should I
put it into the issue tracker and get sign off by someone else?

Ollie

[ron minnich]

On 11/22/05, Li-Ta Lo  wrote:
> BTW, I have a minor change to the mptable.c for s2881, should I
> put it into the issue tracker and get sign off by someone else?

Your call. If it's really one file, and it's that simple, and you are sure
it only affects that single target, I think it is ok.

ron

[yhlu]

ron,

1. you missed microcode_rev_c.h, microcode_rev_d.h, microcode_rev_e.h

2. you didn't use my latest that seperate model_fxx_update_microcode.c from
model_fxx_init.c

do you need me  do that for you?

YH

On 11/22/05, ron minnich  wrote:
> On 11/22/05, Li-Ta Lo  wrote:
> > Did you actually committed it? From the web page, the latest patch level
> > is 2091 which is the FSF address. SVN update shows the same thing.
>
> my mistake, and thanks, ollie. It is now commited.
> > Does this include the apid id stuff as well? AFIAK we need at least
> > a function in that patch to compile Tyan boards.
>
> this is purely the microcode patch.
>
> thanks
>
> ron

[Li-Ta Lo]

> ron,
>
> you missed microcode_rev_c.h, microcode_rev_d.h, microcode_rev_e.h
>
> you didn't use my latest that seperate model_fxx_update_microcode.c
>
> from
> model_fxx_init.c
>
> do you need me  do that for you?

Could you send the CAR enabling and get_apic_id patch again?

Ollie

[ron minnich]

On 11/22/05, yhlu  wrote:
> ron,
> you missed microcode_rev_c.h, microcode_rev_d.h, microcode_rev_e.h

fixed.

2. you didn't use my latest that seperate model_fxx_update_microcode.c from
> model_fxx_init.c

put a patch for this in the issue tracker. Let's start trying to do this
correctly.

I'm digging through this mess and it's not easy. If you have a new patch
that outdates one in the issue tracker, it's a good idea to change the
status of the issue.

thanks

ron

[yhlu]

I will send out another patch that seperate it....

YH

On 11/22/05, ron minnich  wrote:
> On 11/22/05, yhlu  wrote:
> > ron,
> > you missed microcode_rev_c.h, microcode_rev_d.h, microcode_rev_e.h
>
> fixed.
> you didn't use my latest that seperate model_fxx_update_microcode.c
> > from model_fxx_init.c
>
> put a patch for this in the issue tracker. Let's start trying to do this
> correctly.
>
> I'm digging through this mess and it's not easy. If you have a new patch
> that outdates one in the issue tracker, it's a good idea to change the
> status of the issue.
>
> thanks
>
> ron

[yhlu]

add issue 34 about that.

YH

On 11/22/05, yhlu  wrote:
> I will send out another patch that seperate it....
>
> YH
>
> On 11/22/05, ron minnich  wrote:
> > On 11/22/05, yhlu <[e-mail] > wrote:
> > > ron,
> > > you missed microcode_rev_c.h, microcode_rev_d.h, microcode_rev_e.h
> >
> > fixed.
> > you didn't use my latest that seperate model_fxx_update_microcode.c
> > > from model_fxx_init.c
> >
> > put a patch for this in the issue tracker. Let's start trying to do this
> > correctly.
> >
> > I'm digging through this mess and it's not easy. If you have a new patch
> > that outdates one in the issue tracker, it's a good idea to change the
> > status of the issue.
> >
> > thanks
> >
> > ron