Genesi

[Jason Filby]

Just came across this: http://www.genesi.lu/

Appears to be a new PPC based platform with published specs - would be
great to have ROS running on this!

Cheers
Jason

"Jason Filby" <jason.filby(a)gmail.com> wrote:


>   Just came across this: http://www.genesi.lu/
>
>  Appears to be a new PPC based platform with published specs - would be
>  great to have ROS running on this! 
Yes, the Pegasos boards look great! Have a look at this:
http://www.pegasosppc.com/

But I have to remind you that there are _no_ usable development tools
available. We will have to add little-endian PPC-PE support to GCC and
Binutils because it was either removed (GCC) or suffers from heavy bit-rot
(Binutils). This is not an easy task when you're neither a PPC-Guru nor a
GCC/Binutils-Guru.


Regards,
Eric

[Steven Edwards]

Hi Eirc and Jason,

--- Eric Kohl <eric.kohl(a)t-online.de> wrote:
>   But I have to remind you that there are _no_ usable
> development tools
>  available. We will have to add little-endian PPC-PE support to GCC
>  and
>  Binutils because it was either removed (GCC) or suffers from heavy
>  bit-rot
>  (Binutils). This is not an easy task when you're neither a PPC-Guru
>  nor a
>  GCC/Binutils-Guru. 
Right. The only other option is to add a ELF loader to ntosknrl and
ntdll and then build all of ReactOS as ELF Winelib binaries. I have
looked at this quite a bit and even have a bug for it bugzilla. We have
the needed tools to support a ELF build of ReactOS but we need someone
to write the binary loader. I have spoken to Alexandre about it at
length and Blight did some research in to this....needless to say we
have not made much progress as of yet.

I am afriad our only hopes of porting to other platforms with PE are
arm-wince-pe and sh4-pe both of which are still supported by mainly GCC
for embedded development.

Thanks
Steven



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com

[Gregor Anich]

Hi!

Steven Edwards wrote:

>  Hi Eirc and Jason,
>
> --- Eric Kohl <eric.kohl(a)t-online.de> wrote:
>   
>
> >  But I have to remind you that there are _no_
> > usable development tools
> > available. We will have to add little-endian PPC-PE support to GCC
> > and
> > Binutils because it was either removed (GCC) or suffers from heavy
> > bit-rot
> > (Binutils). This is not an easy task when you're neither a PPC-Guru
> > nor a
> > GCC/Binutils-Guru.
> >     
> >  
> Right. The only other option is to add a ELF loader to ntosknrl and
> ntdll and then build all of ReactOS as ELF Winelib binaries. I have
> looked at this quite a bit and even have a bug for it bugzilla. We have
> the needed tools to support a ELF build of ReactOS but we need someone
> to write the binary loader. I have spoken to Alexandre about it at
> length and Blight did some research in to this....needless to say we
> have not made much progress as of yet.
>
> I am afriad our only hopes of porting to other platforms with PE are
> arm-wince-pe and sh4-pe both of which are still supported by mainly GCC
> for embedded development.
>
> Thanks
> Steven
>   
>  
Adding support to load (map) ELF files to ntoskrnl is not a big problem 
I think (I have already done this and it should work)
Problems which I had was that normal ELF files do not contain an 
optional header which we need (it contains for example the required os 
and subsystem version and subsystem type) - this is what wingcc can be 
used for I think.
I have also had problems with building our libraries in ELF format to 
link some ELF test-app against, maybe this is easier with wingcc.

Maybe if I try again with the WINE tools I can get further... If anybody 
else wants to try I can send a patch for ELF support in ntoskrnl.

 -blight

[James Tabor]

Hi!

WOW! p2g4Regular price: $775.00

# MicroATX mainboard  (236 mm x 172 mm), compatible with all ATX-compliant cases.
# Open Firmware .
# MV64361 Discovery II System Controller from Marvell.
# PC2100 RAM , two sockets for DDR-266 with up to 8 gigabytes total.
# AGP slot .
# PCI subsystem with three 32bit, 33MHz slots, optional Riser Card.
# IEEE1394/Firewire providing 100, 200 or 400 megabits of data bandwidth.
# Gigabit ethernet provided by the Marvell Discovery II MV64361
# 10/100 megabit ethernet using a VIA Rhine controller.
# USB subsystem giving two external connectors and one internal connector, provided by the
VIA 8231 
chipset.
# SPDIF digital audio connector.
# AC97 sound subsystem with microphone input, line in/out and headset connector, provided
by the 
Sigmatel STAC 9766 codec.
# IRDA for infra-red remote control.
# ATA100-compatible IDE support with two channels for up to four ATA devices, provided by
the VIA 
8231 chipset.
# Two PS/2 connectors for use with standard PS/2 mice and keyboards.
# Serial (RS232) port.
# Parallel (Centronics) port.
# Gameport for PC-compatible joysticks.
# Floppy drive connector.
# Two operating systems included: MorphOS , Debian GNU/Linux with Mac-on-Linux .

It does come with a Linux Debian.

Gregor Anich wrote:
>   Hi!
>  
>  Steven Edwards wrote:
>  
> >   Hi Eirc and Jason,
> >
> >  --- Eric Kohl <eric.kohl(a)t-online.de> wrote:
> >   
> >
> > >   But I have to remind you that there are _no_
> > > usable development tools
> > >  available. We will have to add little-endian PPC-PE support to GCC
> > >  and
> > >  Binutils because it was either removed (GCC) or suffers from heavy
> > >  bit-rot
> > >  (Binutils). This is not an easy task when you're neither a PPC-Guru
> > >  nor a
> > >  GCC/Binutils-Guru.
> > >     
> >
> >  Right. The only other option is to add a ELF loader to ntosknrl and
> >  ntdll and then build all of ReactOS as ELF Winelib binaries. I have
> >  looked at this quite a bit and even have a bug for it bugzilla. We have
> >  the needed tools to support a ELF build of ReactOS but we need someone
> >  to write the binary loader. I have spoken to Alexandre about it at
> >  length and Blight did some research in to this....needless to say we
> >  have not made much progress as of yet.
> >
> >  I am afriad our only hopes of porting to other platforms with PE are
> >  arm-wince-pe and sh4-pe both of which are still supported by mainly GCC
> >  for embedded development.
> >
> >  Thanks
> >  Steven
> >   
> >  
>  
>  Adding support to load (map) ELF files to ntoskrnl is not a big problem 
>  I think (I have already done this and it should work)
>  Problems which I had was that normal ELF files do not contain an 
>  optional header which we need (it contains for example the required os 
>  and subsystem version and subsystem type) - this is what wingcc can be 
>  used for I think.
>  I have also had problems with building our libraries in ELF format to 
>  link some ELF test-app against, maybe this is easier with wingcc.
>  
>  Maybe if I try again with the WINE tools I can get further... If anybody 
>  else wants to try I can send a patch for ELF support in ntoskrnl.
>  
>  -blight 
Yes post the patch.

I have a CD with MetaWare's High C/C++ PPC for dos. (cant find it ATM)
It supports ELF/DWARF. I think using ELF is way to go.
James

[Steven Edwards]

--- James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> 
>   I have a CD with MetaWare's High C/C++ PPC for
> dos. (cant find it
>  ATM)
>  It supports ELF/DWARF. I think using ELF is way to go. 
The nice thing about going ELF is that it will let us port to every
platform currently supported by gcc. Eric had some objections to it
before but if we only do a ELF build on i386 for testing and do not
release it to the public I dont really see anything wrong with allowing
ELF for other hardware.

Thanks
Steven



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com

[Steven Edwards]

Hi,

--- Gregor Anich <blight(a)blight.eu.org> wrote:
>   Adding support to load (map) ELF files to ntoskrnl is
> not a big
>  problem 
>  I think (I have already done this and it should work)
>  Problems which I had was that normal ELF files do not contain an 
>  optional header which we need (it contains for example the required
>  os 
>  and subsystem version and subsystem type) - this is what wingcc can
>  be 
>  used for I think.
>  I have also had problems with building our libraries in ELF format to 
Great. I will try and help with this.
 
>   link some ELF test-app against, maybe this is easier
> with wingcc.
>  
>  Maybe if I try again with the WINE tools I can get further... If
>  anybody 
>  else wants to try I can send a patch for ELF support in ntoskrnl. 
Can you attach your patch to this bug?

http://reactos.com/bugzilla/show_bug.cgi?id=293

Thanks
Steven



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com