All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Peter Maydell <peter.maydell@linaro.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Sebastian Bauer <mail@sebastianbauer.info>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] hw/display/sm501* status
Date: Sun, 15 Jul 2018 11:29:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.BSF.2.21.1807151041060.88858@zero.eik.bme.hu> (raw)

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 using 8bit 
or 16bit screen modes as AmigaOS does where every screen update does pixel 
format conversion with a simple loop in a suboptimal way. Maybe we can use 
more optimal pixman routines for these.)

We have found while merging previous patches that the status of sm501 is 
not clear. It was originally part of SH emulation added for the R2D board 
but now it's also used by PPC sam460ex board (and can be used with mac99 
as well to run MorphOS that does not yet boot on sam460ex). David Gibson, 
the PPC maintainer has indicated that he can't review changes to this 
device and it is not really related to PPC so the practice of merging 
sm501 patches via his PPC tree is not preferred.

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?

Regards,
BALATON Zoltan

             reply	other threads:[~2018-07-15  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15  9:29 BALATON Zoltan [this message]
2018-07-16  2:53 ` [Qemu-devel] hw/display/sm501* status David Gibson
2018-07-16 20:26   ` BALATON Zoltan
2018-07-16 20:43     ` Peter Maydell
2018-07-18  2:30       ` David Gibson
2018-07-18 20:06         ` Sebastian Bauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.BSF.2.21.1807151041060.88858@zero.eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=aurelien@aurel32.net \
    --cc=david@gibson.dropbear.id.au \
    --cc=kraxel@redhat.com \
    --cc=magnus.damm@gmail.com \
    --cc=mail@sebastianbauer.info \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.