Hi Christian,
> I'd like to make a 0.9 release of Basilisk II this week, since the last
> "official" release is now a year old. So if anyone has objections, he should
> speak up now. Also, each contributor should read the README, INSTALL, TODO
> and TECH files and check them for errors and outdated information.
Depending on exactly when you intend to release version 0.9 and how long
the testing process will take, I would have liked to rearrange the
blitters in the VOSF code so that the right RGB mask values could be
taken into account. I could work on it only that weekend, however.
About the documentation:
* Should we detail configure options in the INSTALL file ?
--enable-addressing=<mode> where mode is:
fastest Try to auto-detect the best mode available
real Real Addressing
direct Direct Addressing
banks Banked Memory Addressing
Notes:
1. Real addressing works only for Linux/i386 insofar Basilisk II is able
to map the whole 680x0 address space to 0x00000000, in the host address
space. Otherwise, Basilisk II may fail due to another LowMem global (or
any other variable) that we still don't patch correctly thus making B2
to address something off the valid memory regions...
2. Direct addressing should work on any platform that supports extended
signal handlers (a signal handler that takes a siginfo_t structure as
parameter) or on any platform we provide a subterfuge.
Direct addressing requires VOSF and therefore the configure script
checks if the system is capable of that. If VOSF can't be enabled, you
will have to switch to banked memory addressing mode. In that case,
please tell the authors about it (operating system used, kernel version,
etc.)
* TECH file: I think it is worth mentioning those
- direct addressing
- real addressing now works under Linux/i386 provided that the
above-mentioned requirements are met.
- VOSF
[I probably won't have the time to add them, however]
Bye;
|
