Hi,
Am 2018-07-18 04:30, schrieb David Gibson:
On Mon, Jul 16, 2018 at 09:43:05PM +0100, Peter Maydell wrote:
On 16 July 2018 at 21:26, BALATON Zoltan wrote:
> I could list sm501 in the sam460ex section thus formally taking
> sub-maintainership but this would only go as far that I'll get cc-d
On Mon, Jul 16, 2018 at 09:43:05PM +0100, Peter Maydell wrote:
> On 16 July 2018 at 21:26, BALATON Zoltan wrote:
> > I could list sm501 in the sam460ex section thus formally taking
> > sub-maintainership but this would only go as far that I'll get cc-d on
> > changes and try to review them. I stil
On 16 July 2018 at 21:26, BALATON Zoltan wrote:
> I could list sm501 in the sam460ex section thus formally taking
> sub-maintainership but this would only go as far that I'll get cc-d on
> changes and try to review them. I still can't (and don't want to) maintain
> my own tree and send pull reques
On Mon, 16 Jul 2018, David Gibson wrote:
On Sun, Jul 15, 2018 at 11:29:56AM +0200, BALATON Zoltan wrote:
So before sending more patches I'd like to clear who can review and merge
patches for sm501 in the future and what is the maintainership of this
device?
The unfortunate answer is that there
On Sun, Jul 15, 2018 at 11:29:56AM +0200, BALATON Zoltan wrote:
> Hello,
>
> I plan to make more changes to sm501 emulation to make it more usable for
> AmigaOS and other Amiga like OSes. This would include first cleaning up of
> current state, then trying to optimise 2D ops and display updates be
Hello,
I plan to make more changes to sm501 emulation to make it more usable for
AmigaOS and other Amiga like OSes. This would include first cleaning up of
current state, then trying to optimise 2D ops and display updates because
it was found these are currently quite slow. (Especially when us
