PowerPC arcitecture? - Ros-dev

Mike Nordell

4 Jun 4 Jun

2:18 p.m.

Rick Langschultz wrote:

[lots and lots of useless XML tags mixed in an unholy cesspool with HTTP snipped] Could you please trim that crap? I am, as I hope the majority of list subscribers are too, not especially interested in that you wrote an e-mail in MSWord and that your "SpellingState" is "Clean". Please use plain-text only. Thank you for your cooperation. /Mike

Reply

Bryan Quigley

5:29 p.m.

It is quite hard to read the content of your messages if you are using a text only email client. On 6/4/05, Rick Langschultz <rlangschultz(a)cox.net> wrote:

...

I use Outlook XP to compose mail to my boss and to a support team. I have to use HTML formatting in my mail messages. Sorry for the inconvenience I have caused. If people want to get picky about the mail format and not the content of the message, they should re-evaluate their purposes involved in developing code, and material for computers. Rick Langschultz -----Original Message----- From: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Mike Nordell Sent: Saturday, June 04, 2005 9:19 AM To: ReactOS Development List Subject: Re: [ros-dev] PowerPC arcitecture? Rick Langschultz wrote:

[lots and lots of useless XML tags mixed in an unholy cesspool with HTTP snipped] Could you please trim that crap? I am, as I hope the majority of list subscribers are too, not especially interested in that you wrote an e-mail in MSWord and that your "SpellingState" is "Clean". Please use plain-text only. Thank you for your cooperation. /Mike _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev

Reply

Robert Köpferl

6:40 p.m.

To do what others still refused, I just give an answer: Both, x86 and PPC PCs are more simmilar than different. So they're using rather the same architecture (PCI, ...). The different instruction sets are just two different devices named CPU. Therefore we use different compilers or call gcc with another architecture flag. The devices are the same on each plattform. PCI-cards are exchangeable and since PCI is PCI, the dev's adresses remain the same. So a well written driver will work on either architecture by just being recompiled. Normally. But there's still the Endian-problem (how order the multiple bytes of a large number have). x86 uses little endian, while ppc natively uses big endian. Up to G4 there's a switch to make the processor think different, but G5 misses this flag. So we seem to be forced to use big endian for our build. What did M$ use in former times, when winnt 3.51 PPC was available? Rick Langschultz wrote:

...

I was reading the email on free PowerPC computers available. I wanted to work on a port for powerpc a long time ago, but was shot down in the IRC channel. I want to use pearpc and a native powerpc with FreeBSD or linux in it to compile the project. Also since PowerPC and x86 and x64 have different instruction sets, how will ReactOS implement the NT kernel on non-intel architectures? I would imaging PPC-ata and X86-ata have different addresses. And not all adapters work from x86 on ppc. Maybe someone could work closely with Darwine to get some of this handled. ------------------------------------------------------------------------ _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev

Reply