>
> Hello all!
> First, apologies if I am off topic for this list
Seems the right place to me ;)
[stuff about the CPU coming up in ultra safe mode deleted]
> I feel that it
> desireable (and apparently _necessary_) to accomplish this task as
> part of the boot process.
In the setup.c seems about right ;)
> For philisophical reasons I think it makes
> sense to implement this as a module.
Correct me if I'm wrong, but can you change the processor you have (while
it's running) ? Ok, so how about at the same point that the
i386/i486/P5/P6 stuff is messed with ?
> My concern is that it may
> already be too late to access the CR0 register by the time the boot
> process gets to the point of initializing loadable modules. Is this
> the case or can my program move a value to CR0 at the time the kernel
> will execute it if it is written as a loadable module? I am asking
> before trying because the cxpatch doc available on the net suggests
> that the access to the CR0 register probably needs to go into the
> 'kernel proper'. Will that be necessary?
I don't see the probelm with having it in the kernel, like all the intel
stuff (I would like to see the Cyrix/IBM/NextGen/... support there too).
> If so, please advise me as
> to 'whereto' add the code, i.e init, etc. Thanks in Advance!
>
> rrbishop@dhinternet.com
Bryn
--
PGP key pass phrase forgotten, \ Overload -- core meltdown sequence
again :( and I don't care ;) | initiated.
/ This space is intentionally left
| blank, apart from this text ;-)
\____________________________________