|Re: [hatari-devel] Manual update|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
This is a multi-part message in MIME format.
On 12/20/19 9:03 AM, Thomas Huth wrote:
Am Sun, 15 Dec 2019 16:27:17 +0200
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
I noticed that Manual was missing some recent
Does the info regarding Mega ST/STE, and SCC B
look correct on the attached patch?
I think it's rather confusing if you summarize the Mega-ST and Mega-STE
in the same section.
Dang, I've already pushed it.
Apart from the RTC, they don't have that much in
common. Mega-ST features should be mentioned in the ST section, and
Mega-STE features should simply be mentioned in the STE section.
I think that was OK when RTC was its own option,
but now that there are separate machine settings,
I'd rather have them in separate section(s) for
To avoid the confusion, attached patch continues
this by separating different Mega models to
* adds separate section for CPU / FPU emulation
* splits emulator features from HW features,
like they're in release notes, plus adds some
missing items there
* removes "most of the ST specific hardware"
item as I think Hatari now implements all
ST HW features
Opposite approach would be listing all features
in one big list, and e.g. having some feature
matrix table which lists which features belong
to which machines, with some notes about TOS
That HW matrix could look something like this:
ST STe MegaST MegaSTE TT Falcon
ACSI x x x x x -
IDE - - - - - x
SCSI - - - - x x
Blitter [x] x [x] x x x
Sound DMA - x - x x x
DSP - - - - - x
MIC - - - - - x
MMU - - - - x x
RTC - - x x x x
TT-RAM - - - - x x
[x] = supported only with TOS 2.06 / EmuTOS
Or there could be some mix of these two approaches. HW matrix might be
nice in any case.
Personally I'd rather split things to smaller
sections for readability, as long as that can
be done logically.