view README.wscons @ 1524:38a12fd1a2c1

Fixed bug #46 Date: Fri, 13 Jan 2006 18:09:45 -0500 From: mhall4400 vipmail kvcc edu Subject: Possible SDL bug Greetings I believe Ive come across a bug in your SDL product (1.2.9), in the CD-ROM control portion of the library. When calling the SDL_CDPlay() function to play the last track of a CD using the offset and length from an SDL_CD structure generated by SDL_CDOpen(), I get the following error from a call to SDL_Error(): mciSendCommand() error: The specified parameter is out of range for the specified command. The code returning the error is: SDL_CDPlay(g_playingDriveSDLCD, g_playingDriveSDLCD->track[trackNumberInt].offset, g_playingDriveSDLCD->track[trackNumberInt].length) Subtracting one from the length of the provided length seems to repair the problem: SDL_CDPlay(g_playingDriveSDLCD, g_playingDriveSDLCD->track[trackNumberInt].offset, (g_playingDriveSDLCD->track[trackNumberInt].length) - 1) Ive replicated this problem on Windows 98 SE (several months since last patch), fully-patched Window ME, seldom-patched Windows XP SP1, and fully-patched Windows XP SP2. While investigating the issue, I came across a line in your librarys win32 source code in file \src\cdrom\win32\SDL_syscdrom.c (source code zip archive from your download page), function: SDL_SYS_CDGetTOC(), line 226 where you add 1 to the value for length to fix MCI last track length bug. This may be the source of the issue (because subtracting 1 from the length seems to resolve the issue). Microsoft may have patched the referenced bug since you wrote that line. Mike Hall
author Sam Lantinga <slouken@libsdl.org>
date Tue, 14 Mar 2006 05:34:39 +0000
parents 19d8949b4584
children
line wrap: on
line source

==============================================================================
Using the Simple DirectMedia Layer with OpenBSD/wscons
==============================================================================

The wscons SDL driver can be used to run SDL programs on OpenBSD
without running X.  So far, the driver only runs on the Sharp Zaurus,
but the driver is written to be easily extended for other machines.
The main missing pieces are blitting routines for anything but 16 bit
displays, and keycode maps for other keyboards.  Also, there is no
support for hardware palettes.

There is currently no mouse support.

To compile SDL with support for wscons, use the
"--enable-video-wscons" option when running configure.  I used the
following command line:

./configure --disable-oss --disable-ltdl --enable-pthread-sem \
	    --disable-esd --disable-arts --disable-video-aalib  \
	    --enable-openbsdaudio --enable-video-wscons \
	    --prefix=/usr/local --sysconfdir=/etc


Setting the console device to use
=================================

When starting an SDL program on a wscons console, the driver uses the
current virtual terminal (usually /dev/ttyC0).  To force the driver to
use a specific terminal device, set the environment variable
SDL_WSCONSDEV:

bash$ SDL_WSCONSDEV=/dev/ttyC1 ./some-sdl-program

This is especially useful when starting an SDL program from a remote
login prompt (which is great for development).  If you do this, and
want to use keyboard input, you should avoid having some other program
reading from the used virtual console (i.e., do not have a getty
running).


Rotating the display
====================

The display can be rotated by the wscons SDL driver.  This is useful
for the Sharp Zaurus, since the display hardware is wired so that it
is correctly rotated only when the display is folded into "PDA mode."
When using the Zaurus in "normal," or "keyboard" mode, the hardware
screen is rotated 90 degrees anti-clockwise.

To let the wscons SDL driver rotate the screen, set the environment
variable SDL_VIDEO_WSCONS_ROTATION to "CW", "CCW", or "UD", for
clockwise, counter clockwise, and upside-down rotation respectively.
"CW" makes the screen appear correct on a Sharp Zaurus SL-C3100.

When using rotation in the driver, a "shadow" frame buffer is used to
hold the intermediary display, before blitting it to the actual
hardware frame buffer.  This slows down performance a bit.

For completeness, the rotation "NONE" can be specified to use a shadow
frame buffer without actually rotating.  Unsetting
SDL_VIDEO_WSCONS_ROTATION, or setting it to '' turns off the shadow
frame buffer for maximum performance.


Running MAME
============

Since my main motivation for writing the driver was playing MAME on
the Zaurus, I'll give a few hints:

XMame compiles just fine under OpenBSD.

I'm not sure this is strictly necessary, but set

MY_CPU = arm

in makefile.unix, and

CFLAGS.arm = -DLSB_FIRST -DALIGN_INTS -DALIGN_SHORTS

in src/unix/unix.max

to be sure.

The latest XMame (0.101 at this writing) is a very large program.
Either tinker with the make files to compile a version without support
for all drivers, or, get an older version of XMame.  My recommendation
would be 0.37b16.

When running MAME, DO NOT SET SDL_VIDEO_WSCONS_ROTATION!  Performace
is MUCH better without this, and it is COMPLETELY UNNECESSARY, since
MAME can rotate the picture itself while drawing, and does so MUCH
FASTER.

Use the Xmame command line option "-ror" to rotate the picture to the
right.


Acknowledgments
===============

I studied the wsfb driver for XFree86/Xorg quite a bit before writing
this, so there ought to be some similarities.


--
Staffan Ulfberg <staffan@ulfberg.se>