Welcome, Guest. Please login or register.

Author Topic: Shark Os4  (Read 7866 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Jose

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Shark Os4
« on: June 26, 2004, 05:09:38 PM »
@KennyR

"...think about all those horrible 1991 A1200 bottlenecks. PIO HD access (ARGH), slow memory bandwidth, the works. Why pay so much money for a card that's going to be able to reach about 20% of its true potential in an ancient Amiga, an ancient Amiga that could die any time soon?"

As was the case already with many Amiga accelerators the memory and controllers, and in this case the PCI bus, are not restricted to the Classic Amiga's motherboard constraints. The access to memory on the Shark would not be done through the Amiga motherboard, same to the PCI accesses.
Actually Elbox has said that the Shark (or was that the Shark + only?) was an all computer in itself, with access to classic hardware. So there you go, one more PPC choice.
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline Jose

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Shark Os4
« Reply #1 on: June 26, 2004, 07:50:02 PM »
@Piru

Sounds interesting and I honestly can't answer those but some things come to mind...

- How come there is a working version of OS4 on the Blizzard PPC in wich DeluxePaint works fine? (I really don't know but  by this logic it should not work right?)


- "How can SharkPPC ensure the emulation and Amiga 1200 status remain synced?"

Maybe either there is emulation working and 68k halted, or 68k is working by itself and one can't have custom chipset acess? :-?

I can't think of anything about the interrupts problem though.... If some card on the Classic issues an interrupt and the interrupt changes the contents of some registers I guess the only possibility would be to have new drivers/Patches written for those cards :-?
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline Jose

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Shark Os4
« Reply #2 on: June 26, 2004, 08:04:10 PM »
I was thinking about it and the only way to prevents apps colliding with each other with custom hardware access was not to do it and use the OS. The same thing apply here, so I guess what you were talking about was how the emulation, for example with a demo that has taken over the hardware, knew about 68k interrupts for example? I guess it couldn't know, but demos and code directly accesing the hardware that didn't rely on 68k interrupts would still work? Didn't much demos took control of the hardware but still used the OS for some stuff (like interrups)?
Must admit I'm half in the dark here...
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline Jose

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Shark Os4
« Reply #3 on: June 29, 2004, 03:42:55 AM »
@HopperJF

Cheers! :pint: :pint: :-D
\\"We made Amiga, they {bleep}ed it up\\"