Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
GSport now running on Raspberry Pi
438 views
Skip to first unread message
Polymorph
Feb 15, 2013, 8:23:24 AM2/15/13
to
Hi All,
Just thought I'd drop a quick note to say that I have managed to get GSport running on the Raspberry Pi (I don't think anyone has done this yet?).
It was quite simple really, and only required 2 things running the recommended Raspbian "wheezy" distro (although mine is not the latest build):
1) update the "vars_x86Linux" file and change the line:
CCOPTS = -O2 -Wall -fomit-frame-pointer -march=pentium
to:
CCOPTS = -O2 -Wall -fomit-frame-pointer -march=armv6
2) install the xfonts-base package (I had to debug the executable to find that the absence of the 8x13 font was responsible for crashing the program during initialisation)
I've successfully tested it running a few disk images. It's running at ~20MHz, which is very usable. It may run faster on the latest Raspbian distro which has more optimisations (I'll have to try that soon).
One major drawback: I haven't got sound working yet though :-(
I'll post back after I've done some more testing, and hopefully can figure out the deal with sound.
But it's a very promising start. :-)
Cheers,
Mike
Just thought I'd drop a quick note to say that I have managed to get GSport running on the Raspberry Pi (I don't think anyone has done this yet?).
It was quite simple really, and only required 2 things running the recommended Raspbian "wheezy" distro (although mine is not the latest build):
1) update the "vars_x86Linux" file and change the line:
CCOPTS = -O2 -Wall -fomit-frame-pointer -march=pentium
to:
CCOPTS = -O2 -Wall -fomit-frame-pointer -march=armv6
2) install the xfonts-base package (I had to debug the executable to find that the absence of the 8x13 font was responsible for crashing the program during initialisation)
I've successfully tested it running a few disk images. It's running at ~20MHz, which is very usable. It may run faster on the latest Raspbian distro which has more optimisations (I'll have to try that soon).
One major drawback: I haven't got sound working yet though :-(
I'll post back after I've done some more testing, and hopefully can figure out the deal with sound.
But it's a very promising start. :-)
Cheers,
Mike
David Schmidt
Feb 15, 2013, 8:37:51 AM2/15/13
to
On 2/15/2013 8:23 AM, Polymorph wrote:
> Hi All,
>
> Just thought I'd drop a quick note to say that I have managed to get GSport running on the Raspberry Pi (I don't think anyone has done this yet?).
Very cool. We can update the developer page with that and any other
> Hi All,
>
> Just thought I'd drop a quick note to say that I have managed to get GSport running on the Raspberry Pi (I don't think anyone has done this yet?).
tweaks and suggestions you find for the Pi.
> One major drawback: I haven't got sound working yet though :-(
that we can probably re-engineer into GSport. So if you want to dig
deep into that code, that would be a good thing to take a look at as
well... in case you were looking for more work. ;-)
BLuRry
Feb 15, 2013, 10:23:45 AM2/15/13
to
Congrats on the working port!! :-)
-B
Christopher G. Mason
Feb 15, 2013, 3:55:17 PM2/15/13
to
On 2/15/2013 8:37 AM, David Schmidt wrote:
> Chris Mason noted a fix that went into MESS for their Ensoniq emulation
> that we can probably re-engineer into GSport. So if you want to dig
> deep into that code, that would be a good thing to take a look at as
> well... in case you were looking for more work. ;-)
The *NIX GSport sound output uses OSS I believe, looks like a straight
> Chris Mason noted a fix that went into MESS for their Ensoniq emulation
> that we can probably re-engineer into GSport. So if you want to dig
> deep into that code, that would be a good thing to take a look at as
> well... in case you were looking for more work. ;-)
dump to /dev/dsp. Newer Linux distros usually use ALSA and/or
PulseAudio. Direct writes to /dev/dsp are generally rerouted through the
above audio stacks for backwards compatibility, but there is no
guarantee it will work or is setup on all platforms.
I'm surprised that the FTA crew hasn't fixed the Ensoniq bug during
their ActiveGS development. Then again they haven't released their
source in quite awhile. (current is 3.5.894, last source was 3.0.242!)
Its nice to see that GSport is still portable. Despite its rough edges,
namely the lack of a GUI user interface, its still a ton easier to get
working then the MESS IIgs driver.
Oracle
Feb 16, 2013, 5:09:15 AM2/16/13
to
On 15 Feb, 14:23, Polymorph <mike.a.steph...@gmail.com> wrote:
>
> 2) install the xfonts-base package (I had to debug the executable to find that the absence of the 8x13 font was responsible for crashing the program during initialisation)
>
Well done Mike!
>
> 2) install the xfonts-base package (I had to debug the executable to find that the absence of the 8x13 font was responsible for crashing the program during initialisation)
>
I finally understand why it crashed!
Thank you.
Mauro
Polymorph
Feb 16, 2013, 5:52:09 PM2/16/13
to
Ok, a quick update. I have switched to using the latest Raspian build and started from scratch (pulled the latest source down using subversion).
I did have some initial difficulties getting it to build (an internal gcc error), and I'm not exactly sure how I resolved the issue apart from doing an upgrade of all packages (only a handful required updating however). It may have been a memory issue - I'm really not sure. But rebuilding everything this morning is working. Oh, I did have to add "include <stdio.h>" into printer.cpp to get it to build (I may have done this on my old Raspian build too but I can't remember).
Also to get sound working, add "snd-pcm-oss" to "/etc/modules" and reboot. This will ensure the kernel module is added each time you boot. A side note:- I did try this on my previous Raspian build, but it locked up the system everytime. A quick Google seemed to indicate that other people had hit this as well. So my advice is to grab the latest Raspian build like I did, and it should be OK.
So I now have a fully working GSPort running on Raspberry Pi. The sound works, although can be a bit "clicky" when sounds start/stop. Performance is about the same as on my previous Raspian build - ~18MHz. It runs like a very snappy IIgs, but not so much like running on more powerful hardware (running Windows or Mac OSX).
When I get around to it, I might check my source into a separate branch. If anyone needs any help getting it running on the Pi, just drop me a line.
Cheers,
Mike
I did have some initial difficulties getting it to build (an internal gcc error), and I'm not exactly sure how I resolved the issue apart from doing an upgrade of all packages (only a handful required updating however). It may have been a memory issue - I'm really not sure. But rebuilding everything this morning is working. Oh, I did have to add "include <stdio.h>" into printer.cpp to get it to build (I may have done this on my old Raspian build too but I can't remember).
Also to get sound working, add "snd-pcm-oss" to "/etc/modules" and reboot. This will ensure the kernel module is added each time you boot. A side note:- I did try this on my previous Raspian build, but it locked up the system everytime. A quick Google seemed to indicate that other people had hit this as well. So my advice is to grab the latest Raspian build like I did, and it should be OK.
So I now have a fully working GSPort running on Raspberry Pi. The sound works, although can be a bit "clicky" when sounds start/stop. Performance is about the same as on my previous Raspian build - ~18MHz. It runs like a very snappy IIgs, but not so much like running on more powerful hardware (running Windows or Mac OSX).
When I get around to it, I might check my source into a separate branch. If anyone needs any help getting it running on the Pi, just drop me a line.
Cheers,
Mike
Polymorph
Feb 17, 2013, 2:37:17 AM2/17/13
to
And I forgot to mention, from a clean slate (i.e. freshly installed Raspian), I had to install the following packages:
* xfonts-base (as previously mentioned)
* libX11-dev
* libext-dev
That should help any would be compilers getting underway quickly. :-)
Hope this helps!
Cheers,
Mike
* xfonts-base (as previously mentioned)
* libX11-dev
* libext-dev
That should help any would be compilers getting underway quickly. :-)
Hope this helps!
Cheers,
Mike
Scott Alfter
Feb 18, 2013, 11:00:56 AM2/18/13
to
In article <23585bf6-c77f-4c96...@googlegroups.com>,
autotools-related files in Subversion or the downloadable tarballs. There's
a makefile in src, but it fails to build on Linux.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( http://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
Polymorph <mike.a....@gmail.com> wrote:
>Just thought I'd drop a quick note to say that I have managed to get
>GSport running on the Raspberry Pi (I don't think anyone has done this
>yet?).
Where did you get buildable source? SourceForge doesn't have the
>Just thought I'd drop a quick note to say that I have managed to get
>GSport running on the Raspberry Pi (I don't think anyone has done this
>yet?).
autotools-related files in Subversion or the downloadable tarballs. There's
a makefile in src, but it fails to build on Linux.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( http://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
David Schmidt
Feb 18, 2013, 11:34:38 AM2/18/13
to
On 2/18/2013 11:00 AM, Scott Alfter wrote:
> In article <23585bf6-c77f-4c96...@googlegroups.com>,
> Polymorph <mike.a....@gmail.com> wrote:
>> Just thought I'd drop a quick note to say that I have managed to get
>> GSport running on the Raspberry Pi (I don't think anyone has done this
>> yet?).
>
> Where did you get buildable source? SourceForge doesn't have the
> autotools-related files in Subversion or the downloadable tarballs. There's
> a makefile in src, but it fails to build on Linux.
Just link vars to vars_x86linux and type make in the src directory. See:
> In article <23585bf6-c77f-4c96...@googlegroups.com>,
> Polymorph <mike.a....@gmail.com> wrote:
>> Just thought I'd drop a quick note to say that I have managed to get
>> GSport running on the Raspberry Pi (I don't think anyone has done this
>> yet?).
>
> Where did you get buildable source? SourceForge doesn't have the
> autotools-related files in Subversion or the downloadable tarballs. There's
> a makefile in src, but it fails to build on Linux.
http://gsport.sourceforge.net/developing.html
and scroll down to X86 Linux. The autotools build system hasn't been
built out.
Lee O.
Feb 20, 2013, 8:37:53 PM2/20/13
to
On 2013-02-16 22:52:09 +0000, Polymorph said:
> So I now have a fully working GSPort running on Raspberry Pi. The sound
> works, although can be a bit "clicky" when sounds start/stop.
At least the popping/clicking/ is a known RPi bug, and not a GSPort issue.
> So I now have a fully working GSPort running on Raspberry Pi. The sound
> works, although can be a bit "clicky" when sounds start/stop.
The current workaround is to prevent the audio from going idle, see
links below:
Details: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=35&t=20445
Bug report: https://github.com/raspberrypi/linux/issues/128
0 new messages