Re: [hatari-devel] Enabling NatFeats

[Thorsten Otto <halgara@xxxxxxxx>]

> Looks to me as if the existing features are mainly related to the debugger..

Thats maybe because Hatari does not need anything else yet. There are quite some more features implemented in eg. Aranym.

> is there a preferred way of doing that, some kind of extension point, some guideline?

I dont't think that there is a general guideline. There are is bit of documentation on Native Features Intro [ARAnyM Wiki] that covers the basic features. Most features use sub-id 0 to identify their interface version, and i would recommend to do this for any new feature. Anything else largely depends on what your feature implements.

		Native Features Intro [ARAnyM Wiki] Native Features is a powerful name for a technique and API with a simple goal: to allow the software running inside ARAnyM use certain features of the host platform.
		Auf wiki.aranym.org anzeigen	Vorschau nach Yahoo

Uwe Seimet <Uwe.Seimet@xxxxxxxxx> schrieb am 18:44 Sonntag, 16.August 2015:

Next question ;-). Is there any suggested way how to extend the current
natfeats? Looks to me as if the existing features are mainly related to the
debugger. If I wanted to add additional features, is there a preferred
way of doing that, some kind of extension point, some guideline?

> On 16 Aug 2015 at 17:56, Uwe Seimet wrote:
> >
> > Are special compiler options required when compiling Hatari in order to
> > enable the NatFeats feature? Opcode $7300 results in an exception via
> > vector $10, but I would have expected the availability of NatFeats to be
> > signalled, i.e. no exception. (The code is running in supervisor mode.)
> >
> Did you use "--natfeats true" on the Hatari command line?
>
> Roger Burrows
>
>
>