tuxnes-devel — Development discussion for the TuxNES project

Re: [Tuxnes-devel] full screen?

[Mike M. <mel...@pc...>]

On Tue, 10 Apr 2001, David Cougle wrote:

> is it possible to make the picture larger with latest tuxnes?

	Yep. Use the -E option to enlarge the picture. The default
enlargement factor is 2, but you can make it 3 or higher if your machine
can keep up. Also, try out the -L option for scanline emulation. Pretty
nifty.

	Hope this helps...
-- 
	-Mike Melanson

[Tuxnes-devel] OpenBSD

[Mike M. <mel...@pc...>]

On Wed, 11 Apr 2001, Jeroen Ruigrok/Asmodai wrote:

> the as -v output shows as GNU assembler version 1.92.3. =\

	Does this indicate that this OpenBSD installation doesn't have the
latest development software, thus causing incorrect building? (I know I
have v2.9.5 of the GNU assembler.) At any rate, I have OpenBSD/i386 marked
with a yellow box on the features page indicating that it's an
experimental feature.

-- 
	-Mike Melanson

Re: [Tuxnes-devel] New features

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010410 15:31], Mike Melanson (mel...@pc...) wrote:
>OpenBSD/i386 architecture: Probably (we need someone to verify this)

Doesn't work here [finally managed to install it under VMWare].

gcc -DHAVE_CONFIG_H -I. -I. -I.        -O -pipe -Wall -c x86.S
x86.S: Assembler messages:
x86.S:1666: Error: Local symbol LASTBANK never defined.
x86.S:1666: Fatal error:1 error, 0 warnings, no object file generated.

gmake: *** [x86.o] Error 1

Somewhere I can understand that given that LASTBANK is defined in
dynrec.c and mapper.h only #defines _LASTBANK to be LASTBANK.

the as -v output shows as GNU assembler version 1.92.3. =\

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
Knowledge was inherent in all things.  The world was a library...

[Tuxnes-devel] full screen?

[David C. <lun...@mo...>]

is it possible to make the picture larger with latest tuxnes?

-- 
http://www.mp3.com/lunarbard
ICQ #3795561
Lunarbard on AOL(Instant Messenger)
Proverbs 15:3

Re: [Tuxnes-devel] New features

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010410 15:31], Mike Melanson (mel...@pc...) wrote:
>OpenBSD/i386 architecture: Probably (we need someone to verify this)

I tried to install OpenBSD in a VMWare session.  I failed. =(

NetBSD works perfectly.

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
If Winter comes, can Spring be far behind..?

[Tuxnes-devel] New features

[Mike M. <mel...@pc...>]

Hi team,
	I've updated the features list (it's not on the website yet). New
and updated items:

NetBSD/i386 architecture: Yes
OpenBSD/i386 architecture: Probably (we need someone to verify this)
Joystick remapping: Yes
Read ZIP files: Yes
[all 5 sound channels]: Yes
Mapper 10 (MMC4): Yes

Any other items that should be there, or items that are there but should
be updated?

-- 
	-Mike Melanson

Re: [Tuxnes-devel] Next release (end of the week)

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010410 08:31], Mike Melanson (mel...@pc...) wrote:
>	I'm going to release this next version at the end of this week, if
>there are no serious objections.

I blessed the code. :)

I like your doc updates.

Go with it.  That might give me a chance to get it in 4.3-RELEASE of
FreeBSD still.

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
Haste makes waste...

[Tuxnes-devel] Next release (end of the week)

[Mike M. <mel...@pc...>]

Hi team,
	I'm going to release this next version at the end of this week, if
there are no serious objections.

-- 
	-Mike Melanson

Re: [Tuxnes-devel] help w/ tuxnes asm

[Mike M. <mel...@pc...>]

On Mon, 9 Apr 2001, Rigel wrote:

> All right.  I know all about AT&T style syntax, I know many x86 opcodes, but I've never seen this type of addressing mode.  This found on line 148 of table.x86 (in the BRK inst.), and looks like this: 
> "leal   0x0(%ebp,%ebx,2),%ebp".  What's inside the parentheses?

	Okay, now I understand the question. That AT&T syntax is such a
pain to digest sometimes. From plowing through my reference material, the
above instruction means:
  ebp = ebp + (ebx * 2) + 0
I think that's it, but I'm not positive.

> Got one more.  there's a nice little couplet directly before the previous (lines 146,147) that looks like this:
> testl  $0xff,%edi
> setz   %bl
> 
> This sets bl when? is it when edi == 0xff ?

	It looks to me like the net effect of the couplet is:
  if (!(edi & 0xff))
    bl = 1;
The test instruction performs a bitwise 'and' between the 2 operands. Like
a cmp instruction, it discards the result but sets flags. The setz
instruction stores a 1 into the destination if the zero flag is set.

-- 
	-Mike Melanson

[Tuxnes-devel] help w/ tuxnes asm

[Rigel <ri...@an...>]

Hi all,
My name is Rigel Freden, I live in southern Utah, USA, I am 18, a freshman at Southern Utah Univ. majoring in CS (anything else?).  I want to write an assembly port of tuxnes in MIPS (R2000).  I need help w/ x86 asm.

I already sent this to the Mighty Mike Master, but he suggested I join the mailing list...

All right.  I know all about AT&T style syntax, I know many x86 opcodes, but I've never seen this type of addressing mode.  This found on line 148 of table.x86 (in the BRK inst.), and looks like this: 
"leal   0x0(%ebp,%ebx,2),%ebp".  What's inside the parentheses?

Got one more.  there's a nice little couplet directly before the previous (lines 146,147) that looks like this:
testl  $0xff,%edi
setz   %bl

This sets bl when? is it when edi == 0xff ?

	Thanks much,
		Rigel Freden


Who needs Cupid?  Matchmaker.com is the place to meet somebody.
FREE Two-week Trial Membership at http://www.matchmaker.com/home?rs=200015

Re: [Tuxnes-devel] Sources

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010327 22:10], Jeroen Ruigrok/Asmodai (as...@wx...) wrote:
>I'll do the final NetBSD tests tomorrow, but FreeBSD compiles and works
>and is for now blessed with my `let-it-be-released' blessing.

It compiles for now on NetBSD.  Now building X11 and recompiling after
that.

Running TuxNES on X on my FreeBSD box looked good, Immortal didn't
expose problems like it did before.

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
The fragrance always stays in the hand that gives the rose...

[Tuxnes-devel] Sources

[Jeroen Ruigrok/A. <as...@wx...>]

Please test the sources so that they compile under Linux.

I'll do the final NetBSD tests tomorrow, but FreeBSD compiles and works
and is for now blessed with my `let-it-be-released' blessing.

Mike, this means that if you guys don't have problems compiling, and I
give my ACK tomorrow wrt NetBSD, we can release the version we have in
the repo.

After that I think we should clean up the stuff and head for 1.0.

After we release 1.0 [which should merely be a clean-up release from
this version] we can add the new features.

But that's just my take on things.  Experience with FreeBSD RELEASE
schedules has taught me in the last few years that features and
clean-ups can conflict, althought the source code is manageable in the
TuxNES project. :)

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
When faith is lost, when honour dies, the man is dead!

Re: [Tuxnes-devel] D'oh, endian.h

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010327 15:54], Mike Melanson (mel...@pc...) wrote:
>On Tue, 27 Mar 2001, Jeroen Ruigrok/Asmodai wrote:
>
>> Looking at Mike's endian.h paste, it looks like I can strip the __ of
>> the defines used without penalties on the three platforms and not
>> clobber/clutter the code with weird constructs.
>> 
>> Anyone have problems with that solution?
>
>	The source still compiles fine for me. How's the status of the
>FreeBSD/NetBSD compilation?

Well, if it compiles for you then I can safely switch the __BIG_ENDIAN
like stuff to BIG_ENDIAN and probably get FreeBSD compiled now.

First dinner though. ;)

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
In space one cannot hear the sound of crying, nor of laughter...

Re: [Tuxnes-devel] D'oh, endian.h

[Mike M. <mel...@pc...>]

On Tue, 27 Mar 2001, Jeroen Ruigrok/Asmodai wrote:

> Looking at Mike's endian.h paste, it looks like I can strip the __ of
> the defines used without penalties on the three platforms and not
> clobber/clutter the code with weird constructs.
> 
> Anyone have problems with that solution?

	The source still compiles fine for me. How's the status of the
FreeBSD/NetBSD compilation?

-- 
	-Mike Melanson

[Tuxnes-devel] D'oh, endian.h

[Jeroen Ruigrok/A. <as...@wx...>]

Funny, my recent changes fix building on NetBSD with --enable-warnings
not specified.

Doesn't fix it on FreeBSD yet.  Still the endian.h issue.
I need to wrap that in some funny stuff.

Weird thing is that NetBSD only defines _BIG_ENDIAN and BIG_ENDIAN,
_NOT_ __BIG_ENDIAN so I expected it to fail.  FreeBSD only defines
BIG_ENDIAN.  That took me a bit off.  I raised the issues though.  I
wonder where the __ defines came from though, since although it is ok to
use them to avoid namespace issues, I cannot remember any problems up
till now.

Looking at Mike's endian.h paste, it looks like I can strip the __ of
the defines used without penalties on the three platforms and not
clobber/clutter the code with weird constructs.

Anyone have problems with that solution?

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
God does not play dice with the universe...

[Tuxnes-devel] NES emulator

[Jeroen Ruigrok/A. <as...@wx...>]

[Resend due to personal disability to properly compose email address  at
 06:30 in the morning.]

Hi guys,

I see you forgot to mention TuxNES at the NES emu links.

The homepage is located at: http://tuxnes.sourceforge.org/

If you could link to it, it would be great. :)

Cheers,

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
We never know the worth of water, 'till the well is dry...

[Tuxnes-devel] NES emulator

[Jeroen Ruigrok/A. <as...@wx...>]

Hi guys,

I see you forgot to mention TuxNES at the NES emu links.

The homepage is located at: http://tuxnes.sourceforge.org/

If you could link to it, it would be great. :)

Cheers,

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
We never know the worth of water, 'till the well is dry...

Re: [Tuxnes-devel] endian.h

[Mike M. <mel...@pc...>]

On Mon, 26 Mar 2001, Jeroen Ruigrok/Asmodai wrote:

> Can someone comment on whether or not Linux also supports
> BIG_ENDIAN/LITTLE_ENDIAN aside from __BIG_ENDIAN/__LITTLE_ENDIAN?

	Here's the meat of the endian.h file on my Linux box:

/* Definitions for byte order, according to significance of bytes, from
low
   addresses to high addresses.  The value is what you get by putting '4'
   in the most significant byte, '3' in the second most significant byte,
   '2' in the second least significant byte, and '1' in the least
   significant byte.  */
 
#define __LITTLE_ENDIAN 1234
#define __BIG_ENDIAN    4321
#define __PDP_ENDIAN    3412
 
/* This file defines `__BYTE_ORDER' for the particular machine.  */
#include <bits/endian.h>
 
/* Some machines may need to use a different endianness for floating point
   values.  */
#ifndef __FLOAT_WORD_ORDER
# define __FLOAT_WORD_ORDER __BYTE_ORDER
#endif
 
#ifdef  __USE_BSD
# define LITTLE_ENDIAN  __LITTLE_ENDIAN
# define BIG_ENDIAN     __BIG_ENDIAN
# define PDP_ENDIAN     __PDP_ENDIAN
# define BYTE_ORDER     __BYTE_ORDER
#endif


-- 
	-Mike Melanson

Re: [Tuxnes-devel] Releasing v0.75 (not yet)

[Mike M. <mel...@pc...>]

Hi Asmodai,
	I definitely like the idea of pushing this next version of TuxNES
to v1.0. Since the graphics look good, as they always have, and the sound
certainly rocks, I feel this thing does qualify as a one-point-oh
release. Recently, I've been sitting down and playing through some of my
old favorite games on TuxNES from start to finish using my Gravis Gamepad
and it's honestly difficult to tell the difference from a real NES. This
is great since my NES, which turned 12 years old a few weeks ago, is
having trouble staying alive.

	To respond to some of your points:

On Mon, 26 Mar 2001, Jeroen Ruigrok/Asmodai wrote:

> I'm coming near...  I got sidetracked by cleaning up stuff along the
> way [the way is long indeed].  Side effect: NetBSD compilation support.
> :)

	Great to hear...so we can add NetBSD/x86 to the features list
soon?

> >Hopefully, it will be enough time for Scott to update GTuxNES for a
> >simultaneous release.
> 
> Hah, he should have had lots of time now. :)

	Be that as it may, I was still going to have a look at it
soon. I wanted to try and figure out some nice interface option for
joystick remapping. Now that I got my Gravis Gamepad Pro working in full
10-button mode, I suddenly see the need for joystick remapping. GTuxNES
could help the user with this.

> >- go through all of the options and see which ones still exist and
> >work; clean out the others
> 
> Does this also mean to remove dead code?  Currently I #if 0'd them out,
> but if we don't need that code anymore we can schedule that for removal
> in the next version [which I hope will be dubbed 1.0 :)].

	Indeed, by all means, get rid of the dead code, and any dead
options.

> Btw, anyone interested in a gameboy emulator project on the side? :)
> I've yet to find any decent gameboy emulator on Unix, and since we have
> a nice team together already.

	I would encourage you to check out Gnuboy:
  http://www.starfox.org/gnuboy/
I've tried it out and it works great for the games I've played. Note that
I really don't know much about the Gameboy, but this emulator appeared to
work all right. And as the name implies, it's GNU-licensed. I'm sure they
would appreciate your help in porting it to BSD. In fact, Gnuboy was my
inspiration for adding the HACKING file to the CVS tree. Check out their
file of the same name for a thorough architecture description.

> And after that we might try SNES... :)  [wishful thinking mayhaps, but I
> don't like the way snes9x has been going.]

	Just out of curiousity, what don't you like about Snes9x? It's
been a long time since I've used it, but I seem to remember that it worked
great when I did use it.

-- 
	-Mike Melanson

[Tuxnes-devel] endian.h

[Jeroen Ruigrok/A. <as...@wx...>]

Can someone comment on whether or not Linux also supports
BIG_ENDIAN/LITTLE_ENDIAN aside from __BIG_ENDIAN/__LITTLE_ENDIAN?

Thanks,

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
And if it comes, the living will envy the dead...

Re: [Tuxnes-devel] Re: [tuxnes-dev] Steve's memory patch

[Jeroen Ruigrok/A. <as...@wx...>]

[sorry for the rediculous late replies]

-On [20010227 20:03], spi...@my... (spi...@my...) wrote:
>What's broken in BSD?

Mostly #include/#define stuff.  Plus I like anal compiler settings to
get more ANSI portability.  Apply large clue before fixing though. ;)

>For some reason we are allocating about 20 megs worth, and only really
>using 3... It just seems to be quite sloppy to me :-)

Normally malloc() prereserves memory but doesn't really allocate it
right away.  Doing the latter would cause immediate thrasing [be it
paging or swapping] in the OS.  So whilst we may seem to allocate a
tonload of memory, we only use a fraction. :)

>What I did for my patches was just grep through the source for FIXME's,
>then fix them(I think ;-).. Let me know is you found anything nasty
>from those patches..  The memory handling should be fine, don't see any
>problems there... I wonder if the defines react wierd on BSD?

Just look at some of my recent list of *cough* fixes.

Please let me know if I broke stuff on Linux.

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
Honesty is the first chapter of the book of wisdom...

Re: [Tuxnes-devel] Releasing v0.75 (not yet)

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010227 20:03], Mike Melanson (mel...@pc...) wrote:
>	Don't worry; I'm not releasing v0.75 just yet. I'll wait for
>Asmodai's fixes so that we officially support FreeBSD again.

I'm coming near...  I got sidetracked by cleaning up stuff along the
way [the way is long indeed].  Side effect: NetBSD compilation support.
:)

>Hopefully, it will be enough time for Scott to update GTuxNES for a
>simultaneous release.

Hah, he should have had lots of time now. :)

>- go through all of the options and see which ones still exist and
>work; clean out the others

Does this also mean to remove dead code?  Currently I #if 0'd them out,
but if we don't need that code anymore we can schedule that for removal
in the next version [which I hope will be dubbed 1.0 :)].

>Then I feel we can get this release out the door. That will be v0.75. I
>predict that v0.76 will have us working hard on save state support and the
>portable CPU core. The latter feature should also lead us to be able to
>support some more mappers.

Save state and portable CPU core sounds cool.

Btw, anyone interested in a gameboy emulator project on the side? :)
I've yet to find any decent gameboy emulator on Unix, and since we have
a nice team together already.
And after that we might try SNES... :)  [wishful thinking mayhaps, but I
don't like the way snes9x has been going.]

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
I think, therefore I am...

Re: [Tuxnes-devel] zip file support

[Jeroen Ruigrok/A. <as...@wx...>]

-On [20010227 04:45], Mike Melanson (mel...@pc...) wrote:
>	So, should we go ahead and incorporate the change and trust that
>users won't try to open up multi-ROM zip archives to play select
>ROMs? Or should we figure out some new CLI option to be able to select
>certain files inside an archive? Gee, the latter option sounds like work
>to me...:) It's great that the zip file support meets one user's
>need. Maybe we should release the option as it is (and document its
>precise functionality) and add more advanced handling if users ask for it?

The inside file option sounds like work to do when you're bored or when
people start asking for it in my opinion.

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
Better to light a candle than to curse the darkness...

Re: [Tuxnes-devel] Uninitialized(??) statics in mapper.c:mmc1()

[Jim U. <ji...@3e...>]

At 02:11pm on 2001 March 26, Jeroen Ruigrok/Asmodai did write:
> -On [20010310 06:08], Jim Ursetto (ji...@3e...) wrote:
> >At 11:53pm on 2001 March 09, Jim Ursetto did write:

> >> Can anyone explain or venture a guess as to why
> >> (compiler, etc.) none of my globals/statics are
> >> being initialized?

> >To answer my own question: the bss segment wasn't being
> >zeroed out, because the crt0.o I'm using doesn't do
> >this.  (grr...)  Time to rewrite it.
 
> Jim,
 
> so this isn't a problem anymore I assume?

Yes, clearing the BSS segment at init time fixes the
problem.  Thanks.

Jim

-- 
``The coolest thing is being able to get my e-mail read to me, like
I'm the queen,'' said Jen Bekman, 31, an AOLbyPhone user in New York
who develops Web content for streaming video.
   -- http://www0.mercurycenter.com/svtech/news/breaking/ap/docs/844798l.htm
ji...@3e... / 0x43340710 / 517B C658 D2CB 260D 3E1F  5ED1 6DB3 FBB9 4334 0710

[Tuxnes-devel] Version number

[Jeroen Ruigrok/A. <as...@wx...>]

As soon as I have the FreeBSD build working again can we bump the
version number to 1.0?

We haven't encountered any real big problems and the code acts more
stable than most other programs I've used lately.  Plus the features
provided are quite mature.

In other words, I'm of the opinion we're past the alpha/beta development
state and are quite mature.

-- 
Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
	  D78D D0AD 244D 1D12 C9CA  7152 035C 1138 546A B867
Better to light a candle than to curse the darkness...