Request about OS Development

[Hans_]

Got any example of such an architecture?

AMD pays their own developers to work on the Radeon drivers & Linux kernel for their hardware. IBM pays developers for the Power architecture. Intel also has an open source team.

The organisations behind Linux distros like Red Hat & Ubuntu also pay developers to work on Linux (paid for by things such as enterprise support contracts).

Heck, Android is based on Linux and also has paid developers working on it.

A lot of money gets spent on Linux development.

Hans

[ne_one]

Which is exactly what should have happened to the Amiga 20 years ago.

And exactly what should still happen.

We've heard the same non-sensical arguments about endian orientation, preserving compatibility, limited resources, lack of qualified developers, non-existent funding and how alternative solutions relegate AmigaOS to the scrapheap for 2 decades.

In the meantime, a significant amount of money has been invested in developing the A1222, X1000 and X5000 - all of which are outdated, expensive and have suffered significant shortfalls in software support.

If you peel back the litany of excuses it ultimately comes down to two things: fraudulence and ineptitude.

[guest11527]

In the meantime, a significant amount of money has been invested in developing the A1222, X1000 and X5000 - all of which are outdated, expensive and have suffered significant shortfalls in software support.

Yes, and I personally never quite understood this move. Just for the records. The people the build the hardware are not the same that worked on the software. The problem is that the market is too small to create a competative hardware that is cost-efficient, So in essence, switching the architecture "pulled the rug" under the development. Not enough users because the hardware was too expensive, and the hardware was so expensive because there are not enough users.

If you peel back the litany of excuses it ultimately comes down to two things: fraudulence and ineptitude.

It's a little bit more complicated than that.

[psxphill]

Again, no. OS-X was when porting *to* PowerPC was finished, not porting to Intel. Sigh.

You're a drama queen, my point is valid. MacOS X always ran on Intel, they just didn't sell it. MacOS X was essentially a reskinned NextStep, it ran on x86 before it ran on PowerPC. https://www.youtube.com/watch?v=pQaqDQx3Lo8

MacOS X didn't need 68k & x64 structures to be compatible as the 68k code was running in an emulator. In classic MacOS they were able to keep all memory structures compatible because they were both big endian CPUs.

Which is exactly what should have happened to the Amiga 20 years ago.

AROS is more than 20 years old. It's biggest problem was that people hated x86 back then, people even made Intel Outside stickers. It was too late by the time the user base had conceded defeat on the CPU. Apple had the revenue, nobody else did.

The "if commodore had survived, they would have .... " argument is also kinda difficult to make. IMO if they had paid the xor patent fee so that they could import CD32 into the US and then be able to pay the factory who made them then they might have survived for a little longer. But the PlayStation would have eaten their lunch. Commodore didn't really know what to do after they launched the a500.

[kolla]

A lot of money gets spent on Linux development.

Sure, but you kinda came with a reversed answer

I was interested in architectures that have lost kernel support due to lack of money.

[kolla]

MacOS X always ran on Intel, they just didn't sell it. MacOS X was essentially a reskinned NextStep, it ran on x86 before it ran on PowerPC.

Exactly, this time you got it right

[psxphill]

Exactly, this time you got it right

So getting me to expand my answer for your pedantry was worthwhile?

[kolla]

So getting me to expand my answer for your pedantry was worthwhile?

Sure, because what you said first was wrong, simple as that.

[wizzard_o]

Port OS4 to "#?" Processor arguments are moot, PPC = OS4, AROS = x86 & OS3 = 68K.

I have several Sun Sparc stations but do you hear me bleating on about porting OS4 to it, noooo.... :lol:

Wizz.

[bloodline]

You can get big endian PowerPC chips, you can't get big endian x64 chips.

It's possible to create an x64 compiler which deals with the endian conversion (bonus points if you can figure out how to make it only do the endian conversion for data that really matters).

Hi psxphill, if you read my earlier post, I link to my inline 68k emulator. Endian issues are annoying but not a huge problem. They simply require a translation layer. In my 68k emulator the emulated 68000 is allowed access to the x86 address space, when running on AROS, all the OS data structures an Amiga App running in that space expects to find will be present and so the App will run (just as it does on 68k AROS). The big problem comes when trying to run the 68000 App on a 64bit processor like the x86_64, then the Amiga App can only see the first 4gig of memory, but all the the OS data structures and even the Application itself could be anywhere in a multi terabyte address space (this is address space, not simply installed RAM)... so it will fail and there is no way around this.

The 68k Amiga is firmly trapped in a 32bit world.

[psxphill]

when running on AROS, all the OS data structures an Amiga App running in that space expects to find will be present and so the App will run (just as it does on 68k AROS).

How do you solve the problem of

DWORD x=0x12345678;
char *y=hello";

char a = [(char *)&x)[0];
char b = y[0];

a is different on a big endian cpu to a little endian cpu.

Have you essentially created a little endian 68k so it will work with native AROS structures when accessing the data with the same size as it was defined? That might work in some situations, but it's trivial to create an example where it would fail.

[QUOTE="bloodline;833534]The big problem comes when trying to run the 68000 App on a 64bit processor like the x86_64, then the Amiga App can only see the first 4gig of memory, but all the the OS data structures and even the Application itself could be anywhere in a multi terabyte address space (this is address space, not simply installed RAM)... so it will fail and there is no way around this.

The 68k Amiga is firmly trapped in a 32bit world.[/QUOTE]

Where the OS structures are is irrelevant, they will contain 64 bit pointers so the offsets will be all wrong. You could however create an x32 https://en.wikipedia.org/wiki/X32_ABI AROS build.

This would have most of the benefits of x64 (see previous link) but still allow 68k code to run, potentially as well as legacy Power PC apps (if you write another emulator). If you have solved the endian issue (and I'm looking forward to your explanation) then you might be able to throw in a way of switching to x86 code as well as supporting this on x86 builds of AROS, otherwise you need an x32 big endian ABI.

You could create another method for allocating memory > 64gb for ramdisk & file system caches where you can guarantee the pointers won't need to be accessed outside the task. Which could be used on x32 builds and x86 builds using PAE.

Apple & Microsoft have gone through similar issues.

Also, how did you handle switching between x86->68k->x86 because it would be nice if exec/SetFunction could be used from both x86 & 68k code and have it be called transparently.

[kreciu]

What more to add, AmigaOS should run on PC without any type of emulation and populate any single PC like a virus, spread as much as possible. That way AmigaOS would become accessible for people. Cheap hardware would give it a chance. After that the REAL problem would be lack of any type of productivity software, but I would worry about this LATER, when I can run AmigaOS on my PC.

BUT situation above would be viable only when we start thinking about AmigaOS as system that actually is USEFUL for most of people, at this point AmigaOS is purely hobby. Considering prices of Amiga HW this type of expense will not be justified by anybody, but AmigaOS fanatics or alternative universe fans.

[guest11527]

AmigaOS should run on PC without any type of emulation and populate any single PC like a virus, spread as much as possible.

And why exactly should it do that? Os development did not stop 25 years ago. AmigaOs is illl-designed for modern requirements. I always call it a "toy operating system" because it lacks any services that would be important today. Even if - the market works today different than it did 25 years ago.
Back then, computers were used by hobbyitsts, hackers, gamers, freaks... today, they are a commodity. You cannot expect a "modern user" to know what a .info file is, or how to "lay out" icons. It's all the wrong concept.

That way AmigaOS would become accessible for people. Cheap hardware would give it a chance. After that the REAL problem would be lack of any type of productivity software, but I would worry about this LATER, when I can run AmigaOS on my PC.

Yeah, right. And this "worry about the pesky details later" approach was exactly the reason why the PPC experiment is right now where it is. "PPC is the future, let's worry about the applications later".

You need to understand that *today* the market works differently. Nobody worries about the hardware anymore. You have it anyhow. The apps are what matters. Commodity for the user. You don't buy a computer today because it is "cool hardware". You buy it because "it looks nice" and "it runs the stuff I need". It is reduced to things the average user understands: "How thin is it" (that is currently what people seem to want) and "does it do what I need".

AmigaOs cannot do that. The Amiga story as a "useful computer" ended last century already - as I say, this ship sailed away a long time ago.

[kreciu]

And why exactly should it do that? Os development did not stop 25 years ago. AmigaOs is illl-designed for modern requirements. I always call it a "toy operating system" because it lacks any services that would be important today. Even if - the market works today different than it did 25 years ago.
Back then, computers were used by hobbyitsts, hackers, gamers, freaks... today, they are a commodity. You cannot expect a "modern user" to know what a .info file is, or how to "lay out" icons. It's all the wrong concept.

I know, but somewhere behind my head I have this sentiment that AmigaOS could takeover whole world . I feel like 25 years ago when you actually could get Amiga500 in the store. It is somehow hard for me to think about AmigaOS as a pure "hobby" (even if it is for me... hobby!).

I actually did real work on my beloved A600 back in time.

Yeah, right. And this "worry about the pesky details later" approach was exactly the reason why the PPC experiment is right now where it is. "PPC is the future, let's worry about the applications later".

Really? From my perspective I did not see it, maybe from dev. perspective PPC was the future. I liked more AmigaOS, not necessarily as a best OS, but it was nice and CHEAP alternative to PC.

You need to understand that *today* the market works differently. Nobody worries about the hardware anymore. You have it anyhow. The apps are what matters. Commodity for the user. You don't buy a computer today because it is "cool hardware". You buy it because "it looks nice" and "it runs the stuff I need". It is reduced to things the average user understands: "How thin is it" (that is currently what people seem to want) and "does it do what I need".

Exactly, nobody cares about HW, but there is boatload of PC hardware and it will not go away "tommorow", and asking to pay $2000 for HW that can run AmigaOS in a relatively well is a LOT of money AND based on number of various motherboard revisions for AmigaOS4.x idea of having proprietary HW to run AmigaOS4.1 is simply BAD. Now, we have like few versions of AmigaOS4.1 for each HW? Strange.

OK. If not PC, why not to make it run on old MacPPC hardware. This "old" HW is way better  then NEW and I can get PowerMAC G5 as a scrap metal price. Wait. I have old completely unused iBookG4 in my storage. That move would not require 100% "rewrite" of AmigaOS. Is that right? So why not?

AmigaOs cannot do that. The Amiga story as a "useful computer" ended last century already - as I say, this ship sailed away a long time ago.

This is a statement, that depend on attitude of person saying it . Let say idea of "useful computer" based on AmigaOS is gone.

Why can't I install AmigaOS on MacPPC? You just wrote that nobody cares about hardware they use. Apparently people who own rights for AmigaOS care about $2000 mobos that is slower(?) then PowerMAC G5  and promise hardware for months or years.

It is taking about 2 years to release A1222. How long it will take to adapt AmigaOS for MacMini, PowerMac etc. It is funny how MorphOS "jumped" on new AmigaOS hardware and somehow MorphOS dev. could adapt it FROM Mac to new HW, quite fast.

Linux on PowerMAC, simply great speed:https://www.youtube.com/watch?v=so35SrThHUs

[number6]

OK. If not PC, why not to make it run on old MacPPC hardware. This "old" HW is way better  then NEW and I can get PowerMAC G5 as a scrap metal price. Wait. I have old completely unused iBookG4 in my storage. That move would not require 100% "rewrite" of AmigaOS. Is that right? So why not?

Why can't I install AmigaOS on MacPPC? You just wrote that nobody cares about hardware they use. Apparently people who own rights for AmigaOS care about $2000 mobos that is slower(?) then PowerMAC G5  and promise hardware for months or years.

It is taking about 2 years to release A1222. How long it will take to adapt AmigaOS for MacMini, PowerMac etc. It is funny how MorphOS "jumped" on new AmigaOS hardware and somehow MorphOS dev. could adapt it FROM Mac to new HW, quite fast.

Consider the possibility that contracts and agreements exist that, at this time, are still in place and need be honored.

#6

[kreciu]

Consider the possibility that contracts and agreements exist that, at this time, are still in place and need be honored.

#6

IF that is true, then we can't do nothing about it, but IF it is not... then I don't know why not.