tuxnes-devel — Development discussion for the TuxNES project

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27629

Modified Files:
      Tag: tuxnes-0_75_branch
	configure.in emu.c globals.h unzip.c ziploader.c 
Log Message:
More ported from HEAD.

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27845

Modified Files:
      Tag: tuxnes-0_75_branch
	ChangeLog configure.in dynrec.c emu.c mapper.c sound.c unzip.c 
Log Message:
Backports from HEAD, may not build.

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27718

Modified Files:
	emulator.h emulator_x86.h io.h palettes.h renderer.c 
	renderer_ggi.c renderer_sdl.c renderer_sdl.h renderer_w.c 
	renderer_w.h renderer_x11.h sounder.c sounder.h sounder_oss.c 
	sounder_sdl.c 
Log Message:
Fixed SDL headers and now it builds.
Terminator comments over the top.
Some more uniform file headers added.

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17604

Modified Files:
	emu.c emulator.c 
Log Message:
Help pritty printing of core(renderes) and expresed x86's fastnes for help.

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7778

Modified Files:
      Tag: tuxnes-0_75_branch
	ChangeLog README 
Log Message:
I wanted to commit the tag and these doc changes at the same time.

Re: [Tuxnes-devel] 0.75 Stable CVS help wanted.

[Mike M. <che...@ya...>]

That's what I was trying to think of.  Should the next version(current
head) be 2.x or 1.x?  1.x signefies a stable version dose it not?

Fixing these bugs will requier lots of reading throught to find why it was
changed/disabeled.  In the mean time I realy think the current 0.x code
should be our stable flag ship for releases in the file section.

As for 0.x branch can continue, I'l tag it 0.x.1 as I did some bugfixing
too it.  Then I'l start on 0.x+1 and later release that as 0.x+1.0, just
like Jason said.

--- Jason Dorje Short <jd...@us...> wrote:

> Mike Mestnik wrote:
> > Since there are any number of unknowen small problems with CVS head. 
> I'd
> > like to hack on 0.75 and bring closer to where CVS head is.  Dose any
> one
> > know how I might branch this new work?  Do I just need a branch name
> for
> > my work or would it be better to put HEAD on a development branch and
> move
> > Stable to cvs head?  I guess I just want to rename branches withought
> > loosing history.
> > 
> > Also under Featurs in README it says "game saving" dose any one know
> what
> > happened to that code?
> 
> You can branch CVS with "cvs tag -j <tagname>".  See the manual.
> 
> For a short-term solution you can branch the original 0.75 and work on 
> that [1].  But this won't help future development much.  For a 
> longer-term solution you should branch the current code and work on it 
> until it's stable [2].  Of course most bugfixes you make will apply to 
> both branches so they'll have to be committed separately.
> 
> In freeciv we use static tags like R1_14_0 for a release and branch tags
> 
> like S1_14 for a whole branch.  We made a stable branch S1_14 before the
> 
> 1.14.0 release, and let it stabilize through several beta cycles before 
> releasing 1.14.0.  After further bugfixes 1.14.1 was released based on 
> this same branch.  Meanwhile in the HEAD branch (the main branch) 
> development work proceeded normally.
> 
> [1] cvs up -r R0_75; cvs tag -j S0_75
> [2] cvs up -A; cvs tag -j S0_76
> 
> jason
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

Re: [Tuxnes-devel] 0.75 Stable CVS help wanted.

[Jason D. S. <jd...@us...>]

Mike Mestnik wrote:
> Since there are any number of unknowen small problems with CVS head.  I'd
> like to hack on 0.75 and bring closer to where CVS head is.  Dose any one
> know how I might branch this new work?  Do I just need a branch name for
> my work or would it be better to put HEAD on a development branch and move
> Stable to cvs head?  I guess I just want to rename branches withought
> loosing history.
> 
> Also under Featurs in README it says "game saving" dose any one know what
> happened to that code?

You can branch CVS with "cvs tag -j <tagname>".  See the manual.

For a short-term solution you can branch the original 0.75 and work on 
that [1].  But this won't help future development much.  For a 
longer-term solution you should branch the current code and work on it 
until it's stable [2].  Of course most bugfixes you make will apply to 
both branches so they'll have to be committed separately.

In freeciv we use static tags like R1_14_0 for a release and branch tags 
like S1_14 for a whole branch.  We made a stable branch S1_14 before the 
1.14.0 release, and let it stabilize through several beta cycles before 
releasing 1.14.0.  After further bugfixes 1.14.1 was released based on 
this same branch.  Meanwhile in the HEAD branch (the main branch) 
development work proceeded normally.

[1] cvs up -r R0_75; cvs tag -j S0_75
[2] cvs up -A; cvs tag -j S0_76

jason

[Tuxnes-devel] 0.75 Stable CVS help wanted.

[Mike M. <che...@ya...>]

Since there are any number of unknowen small problems with CVS head.  I'd
like to hack on 0.75 and bring closer to where CVS head is.  Dose any one
know how I might branch this new work?  Do I just need a branch name for
my work or would it be better to put HEAD on a development branch and move
Stable to cvs head?  I guess I just want to rename branches withought
loosing history.

Also under Featurs in README it says "game saving" dose any one know what
happened to that code?



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Re: [Tuxnes-devel] How to pause with minimal effect on seti or distributed.net?

[Jason D. S. <jd...@us...>]

Mike Mestnik wrote:
> After looking into this I wonder how the current pause code may even work
> at all, it's if'ed out in places.  As for select vs useep this is
> imposible as we need to call XPending to get events and it's vary unlikely
> we will receve any signals(interupts) since among other things we don't
> have any children.
> 
> I'm going to run some ddd/gdb tests.

Last time I looked it definitely didn't work.

jason

[Tuxnes-devel] How to pause with minimal effect on seti or distributed.net?

[Mike M. <che...@ya...>]

After looking into this I wonder how the current pause code may even work
at all, it's if'ed out in places.  As for select vs useep this is
imposible as we need to call XPending to get events and it's vary unlikely
we will receve any signals(interupts) since among other things we don't
have any children.

I'm going to run some ddd/gdb tests.

--- Jason Dorje Short <jd...@us...> wrote:

> Mike Mestnik wrote:
> > That's correct, I just used usleep for finding when the event might
> end. 
> > This way where not constintaly looking for the event, just once every
> time
> > frame.
> > 
> > While forward porting this too CVS HEAD I saw that non of the working
> > renderes still had this code.  This could be the clue I needed to get
> GGI
> > working, since it still has this code.
> 
> Well, you could replace it with a select(NULL, NULL, NULL, &tv), where 
> tv holds the polling time.  The poll time doesn't have to correspond to 
> a frame, though.  Using select _might_ give better results (lower lag) 
> since it will exit if there's an interrupt.  But in most cases it 
> probably doesn't matter.
> 
> Looking at the internals of a function like gtk_main() may show a better
> 
> way to do this.  Most GUI libraries have code like this already.
> 
> jason
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail

Re: [Tuxnes-devel] A fue minor patches too 0.75.

[Jason D. S. <jd...@us...>]

Mike Mestnik wrote:
> That's correct, I just used usleep for finding when the event might end. 
> This way where not constintaly looking for the event, just once every time
> frame.
> 
> While forward porting this too CVS HEAD I saw that non of the working
> renderes still had this code.  This could be the clue I needed to get GGI
> working, since it still has this code.

Well, you could replace it with a select(NULL, NULL, NULL, &tv), where 
tv holds the polling time.  The poll time doesn't have to correspond to 
a frame, though.  Using select _might_ give better results (lower lag) 
since it will exit if there's an interrupt.  But in most cases it 
probably doesn't matter.

Looking at the internals of a function like gtk_main() may show a better 
way to do this.  Most GUI libraries have code like this already.

jason

Re: [Tuxnes-devel] A fue minor patches too 0.75.

[Mike M. <che...@ya...>]

That's correct, I just used usleep for finding when the event might end. 
This way where not constintaly looking for the event, just once every time
frame.

While forward porting this too CVS HEAD I saw that non of the working
renderes still had this code.  This could be the clue I needed to get GGI
working, since it still has this code.

--- Jason Dorje Short <jd...@us...> wrote:

> Mike Mestnik wrote:
> > Today when I built 0.75 I had to add AM_PROG_AS to configure.in. 
> There
> > was several AC_PROG lines and I was not sure witch one I should use AC
> or
> > AM.
> > 
> > There was also a race condition when the emulator was paused, I'l have
> to
> > look into adding a select for this.  It shoulden't be a big deal to
> just
> > halt execution inside the input handeler should it?
> > For CVS HEAD I'd also like to see if calling a generic input(alarm
> signal)
> > handeler(or a timer) for emulator type
> > events(pause,save,snapshoot,quit,ect) so were not relying on the nes
> rom
> > to pool these for us.
> 
> It needs to pause while waiting for an "event".
> 
> An "event" may be input from keyboard or mouse or any arbitrary X (or 
> whatever GUI) event.
> 
> Using a select loop _may_ work here since select will exit when there's 
> an interrupt/signal received (but I don't know if the above events 
> generate interrupts).  In that case all FD sets should be NULL.
> 
> jason
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel
> 



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29258

Modified Files:
	controller.c controller.h controller_linux.c 
	controller_linux.h controller_sdl.c controller_sdl.h 
	controller_x11.c controller_x11.h defines.h emulator.c 
	emulator.h emulator_c_iface.c emulator_c_iface.h 
	emulator_x86.c renderer_ggi.c renderer_ggi.h renderer_sdl.c 
	renderer_util.c renderer_w.c sounder.c sounder_oss.c 
	sounder_oss.h sounder_sdl.c sounder_sdl.h unzip.c unzip.h 
Log Message:
readded uniform file header to most source code files

Re: [Tuxnes-devel] A fue minor patches too 0.75.

[Jason D. S. <jd...@us...>]

Mike Mestnik wrote:
> Today when I built 0.75 I had to add AM_PROG_AS to configure.in.  There
> was several AC_PROG lines and I was not sure witch one I should use AC or
> AM.
> 
> There was also a race condition when the emulator was paused, I'l have to
> look into adding a select for this.  It shoulden't be a big deal to just
> halt execution inside the input handeler should it?
> For CVS HEAD I'd also like to see if calling a generic input(alarm signal)
> handeler(or a timer) for emulator type
> events(pause,save,snapshoot,quit,ect) so were not relying on the nes rom
> to pool these for us.

It needs to pause while waiting for an "event".

An "event" may be input from keyboard or mouse or any arbitrary X (or 
whatever GUI) event.

Using a select loop _may_ work here since select will exit when there's 
an interrupt/signal received (but I don't know if the above events 
generate interrupts).  In that case all FD sets should be NULL.

jason

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23101

Modified Files:
      Tag: tuxnes-0_75_branch
	configure.in ggi.c renderer.c w.c x11.c 
Log Message:
This will fix the building of x86.S.
 dnl Check for programs which we might need
 dnl --------------------------------------------------------------------
+AM_PROG_AS
 AC_PROG_CC
 AC_PROG_INSTALL

Idle loops need sched_yeld or the more portible usleep.  These "Input loops"
would be better off with a select, however I'm not at this time sure what we
would be selecting for.
+    if (renderer_data.pause_display)
+       usleep (16666);
   } while (renderer_data.pause_display);

[Tuxnes-devel] A fue minor patches too 0.75.

[Mike M. <che...@ya...>]

Today when I built 0.75 I had to add AM_PROG_AS to configure.in.  There
was several AC_PROG lines and I was not sure witch one I should use AC or
AM.

There was also a race condition when the emulator was paused, I'l have to
look into adding a select for this.  It shoulden't be a big deal to just
halt execution inside the input handeler should it?
For CVS HEAD I'd also like to see if calling a generic input(alarm signal)
handeler(or a timer) for emulator type
events(pause,save,snapshoot,quit,ect) so were not relying on the nes rom
to pool these for us.



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

[Tuxnes-devel] Time to start talking about a tuxnes release.

[Mike M. <che...@ya...>]

Since the release of TuxNES v0.75, There has been at least one major bug
fix in CVS under tuxnes-0_75_branch.  There has been litle development and
I think a release is just what is needed to get the wheels going again.

The list of changes are.
  -- Support for Multiple(more than one) GameGenie Codes.
  -- Fixed the support for more than one Joystick.

That's all for stable, as for the new work in progress it needs tesing and
feedback.  I'm not sure if we can make a realese of CVS HEAD but I would
certanily tend to any love it may need.  I was thinking if we put a copy
of CVS HEAD on the tuxnes.sf.neet pages and updated the Project File List
with the above fixes then we would be in good shape.

I would gladly take care of this, however I don't know how or if I have
access.



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

[Tuxnes-devel] efp: It's time to seriously take a look at this.

[Mike M. <che...@ya...>]

I got a bug report some time back complaining that "Escape from Pong" an
open sourced nes game segfaulted tuxnes.  I tracked it down to ether a
problem with the mapper or the game running off the end of the rom.  Dose
any one know what MAPTABLE[8] is?

http://hcs.freeshell.org/efp.html

Mapper 0 (No mapper)  Program ROM 16k  Video ROM 0k
Using horizontal mirroring

emulator_x86_dynrec.c:76
MAPTABLE[8] addr=32768



	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

[Tuxnes-devel] CVS commit log for Tuxnes

[Mike M. <ch...@us...>]

Update of /cvsroot/tuxnes/tuxnes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9763

Modified Files:
	Makefile.am emu.c emulator_x86.c renderer.c renderer_x11.c 
	sound.c sound.h sounder_sdl.c 
Added Files:
	sounder.c sounder.h sounder_oss.c sounder_oss.h sounder_sdl.h 
Log Message:
Sounder and Sound split.  Removed sounder code, leaving only nes sound code,
from sound.c.

Re: [Tuxnes-devel] Sound Core

[Mike M. <che...@ya...>]

The way that the sound(ers) and other parts (I.E. emulators) have been
made into modules it would be easy to have a diffrent sound emulation for
each output.  Also the problem with interupting the emulator can be done
quite easily, if there is still a need.

I would be happy too see some of this code cleaned up, not that I'l ever
be able to understand it.

--- Paul Zaremba <pe...@tr...> wrote:
> Hello,
> 
>   I wrote the sound core about three years ago while I was still
> in college.  Though it works it's really a horrible unmaintainable mess.
> Is there a desire for the code to be cleaner?  I was thinking about
> pulling
> the different channels into data structures and functions to isolate
> each channel's sound generation (for a tight loop per channel).  Then 
> I'd make
> a final pass to mix and convert the output to the supported format and 
> send it to
> the output device.  It will mean more code size but the CPU should be 
> able to cache
> a few tight loops better than the current monolithic monster.
> 
> Just wanted some input before I devoted any time to it.
> 
> Thanks,
>    Paul
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel



	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

Re: [Tuxnes-devel] LINUX_SOUNDCARD vs LINUX_SOUNDCARD_H.

[Mike M. <che...@ya...>]

Ahh yes it's a work in progress.  I got it compiling but not working -s
mute workes fine but oss dosen't.

The thing that is not compiling is sounder_oss.c's SNDCTL_DSP_RESET stuff,
it is defined in linux/soundcard.h but I don't think it's included.

Attached is a more upto date copy.  I get a blank screen and realy slow
sound.

--- Jason Dorje Short <jd...@us...> wrote:
> I don't understand.  What is the problem?
> 
> Although this code won't compile for me.  I get:
> 
> enderer_ggi.Tpo"; exit 1; fi
> renderer_ggi.c: In function `UpdateDisplayGGI':
> renderer_ggi.c:1140: error: `sounder' undeclared (first use in this 
> function)
> renderer_ggi.c:1140: error: (Each undeclared identifier is reported only
> 
> once
> renderer_ggi.c:1140: error: for each function it appears in.)
> make[1]: *** [renderer_ggi.o] Error 1
> 
> jason
> 


	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

Re: [Tuxnes-devel] compiler warning

[Mike M. <che...@ya...>]

Fixed (void **) is the correct type.

--- Jason Dorje Short <jd...@us...> wrote:
> Now I get this compiler warning:
> 
> emulator_x86.c: In function `InitMemoryX86':
> emulator_x86.c:217: warning: assignment from incompatible pointer type
> 
> jason
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel



	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

Re: [Tuxnes-devel] LINUX_SOUNDCARD vs LINUX_SOUNDCARD_H.

[Jason D. S. <jd...@us...>]

I don't understand.  What is the problem?

Although this code won't compile for me.  I get:

enderer_ggi.Tpo"; exit 1; fi
renderer_ggi.c: In function `UpdateDisplayGGI':
renderer_ggi.c:1140: error: `sounder' undeclared (first use in this 
function)
renderer_ggi.c:1140: error: (Each undeclared identifier is reported only 
once
renderer_ggi.c:1140: error: for each function it appears in.)
make[1]: *** [renderer_ggi.o] Error 1

jason

[Tuxnes-devel] compiler warning

[Jason D. S. <jd...@us...>]

Now I get this compiler warning:

emulator_x86.c: In function `InitMemoryX86':
emulator_x86.c:217: warning: assignment from incompatible pointer type

jason

[Tuxnes-devel] Sound Core

[Paul Z. <pe...@tr...>]

Hello,

  I wrote the sound core about three years ago while I was still
in college.  Though it works it's really a horrible unmaintainable mess.
Is there a desire for the code to be cleaner?  I was thinking about pulling
the different channels into data structures and functions to isolate
each channel's sound generation (for a tight loop per channel).  Then 
I'd make
a final pass to mix and convert the output to the supported format and 
send it to
the output device.  It will mean more code size but the CPU should be 
able to cache
a few tight loops better than the current monolithic monster.

Just wanted some input before I devoted any time to it.

Thanks,
   Paul