here's a stupid question
I know just enough about Machine and OS architecture to ask this stupid question:
Why couldn't a system have both a PPC and an Athlon?
All applications interact with the upper layers of the system architecture. Those interact with the kernel. The kernel interacts with the processor. Right? Since both PPC and Athlon are Big Endian they could store their information in the same registers in the kernel. Couldn't the kernel direct x86 instructions to an Athlon and PPC instructions to the g4?
Native execution of the instructions would allow for some serious increases in clock speed. Additionally, since there would be a native X86 in the box, wouldn't they be able to exploit the work of the various WINE teams? Or for people who needed more "windows" than WINE, a "native" version of Virtual PC could be released.
<Shrug>
Flame me and list the myriad of reasons I know nothing about anything.

Binky
I know just enough about Machine and OS architecture to ask this stupid question:
Why couldn't a system have both a PPC and an Athlon?
All applications interact with the upper layers of the system architecture. Those interact with the kernel. The kernel interacts with the processor. Right? Since both PPC and Athlon are Big Endian they could store their information in the same registers in the kernel. Couldn't the kernel direct x86 instructions to an Athlon and PPC instructions to the g4?
Native execution of the instructions would allow for some serious increases in clock speed. Additionally, since there would be a native X86 in the box, wouldn't they be able to exploit the work of the various WINE teams? Or for people who needed more "windows" than WINE, a "native" version of Virtual PC could be released.
<Shrug>
Flame me and list the myriad of reasons I know nothing about anything.
Binky