| Re: [hatari-devel] Enabling NatFeats |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Enabling NatFeats
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Sun, 16 Aug 2015 18:43:56 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1439743436; l=743; s=domk; d=seimet.de; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Subject:To:From:Date; bh=skY8pUYHZxzlXMa9DSVbgF2GXVfpe+Wr5yPo7rg4qjI=; b=rFMlK/XH1luVj70/I+CAoKy6xCUZ1fcayk96keyZYmb2xk0ZFPbSElTFqpxhkmXtJFR +lNqquqgZHZccIGTHuqcpwNVlYLrE+rZL65IUpGD9l6cw4Yk9IIUUIRhPqyuC9UWAGs96 Xiyr2QdTiJTGfY+FCAHM7TSFl9NoWf0J4qg=
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
>
>
>