Welcome, Guest. Please login or register.

Author Topic: OS4 Classic, why disable the 68k ?  (Read 8545 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline cha05e90

  • Full Member
  • ***
  • Join Date: Feb 2003
  • Posts: 232
  • Country: de
    • Show all replies
    • http://www.ruthe.info
Re: OS4 Classic, why disable the 68k ?
« on: April 10, 2012, 08:40:47 AM »
Quote from: Erebos;687835
Hi,
I just wondering why the onboard 68k is disable on the Classic version of OS4 ?
If it wasn't, would it be possible to run things without 'runinuae' or the likes ? or maybe it will speed up this as it wont need to emulate the 68k ?


This seems to be a common misunderstanding. You don't need UAE or RunInUAE to use 68k software with AmigaOS4.x (or MorphOS in that respect).
X1000|II/G4|440ep|2000/060|2000/040|1000
 

Offline cha05e90

  • Full Member
  • ***
  • Join Date: Feb 2003
  • Posts: 232
  • Country: de
    • Show all replies
    • http://www.ruthe.info
Re: OS4 Classic, why disable the 68k ?
« Reply #1 on: April 10, 2012, 07:46:36 PM »
Quote from: Zac67;687930
In theory, the '040/060 could run asynchronously in parallel to the PPC (WarpOS + 3.x worked that way).

Really? I don't think it worked that way.
X1000|II/G4|440ep|2000/060|2000/040|1000
 

Offline cha05e90

  • Full Member
  • ***
  • Join Date: Feb 2003
  • Posts: 232
  • Country: de
    • Show all replies
    • http://www.ruthe.info
Re: OS4 Classic, why disable the 68k ?
« Reply #2 on: April 11, 2012, 08:47:51 AM »
Quote from: Piru;687956
It was possible to run 68k and PPC code independent from each other, at least with PowerUP. There were certain highly optimized apps that used to do this. For instance the infamous FastQuake used a special cache inhibited memory area as a ring-buffer to avoid the need for cache flushes. This way both CPUs could run at full speed with as few context switches as possible.

I must admit that I've never really "seen" applications that ran parallel in that sense on a phase5 board - regardless which kernel or OS was used. Using that kind of "cache-protected" buffer looks like a way or work-around to build up some kind of transient parallel work time frame, indeed. But every now and then the context switch will show up again...Thanks for that info!

Quote from: bbond007
Power Down

Oh dear! :-) A new kernel war PowerDown vs. WarpDown will rise...
X1000|II/G4|440ep|2000/060|2000/040|1000