From: <jasper.lowell@bt.com>
To: <balaton@eik.bme.hu>
Cc: tony.nguyen@bt.com, mark.cave-ayland@ilande.co.uk,
dgilbert@redhat.com, atar4qemu@gmail.com, qemu-devel@nongnu.org
Subject: Re: Emulating Solaris 10 on SPARC64 sun4u
Date: Fri, 8 May 2020 02:55:45 +0000 [thread overview]
Message-ID: <78d72c7f09a45357b151231cba9454d6d288680d.camel@bt.com> (raw)
In-Reply-To: <alpine.BSF.2.22.395.2005072048510.5891@zero.eik.bme.hu>
> I don't know anything about this chip so don't know if it helps but
> if
> it's any way similar to ESCC (and the ESCC2 name is not just
> marketing)
> then there's some emulation of that in hw/char/escc.c that you may
> want to
> look at.
From what I can tell, the SAB 82532 is a bit more complex than the ESCC
ones. It's not difficult to implement but a complete solution will be
lengthy because of the large combination of configuration options the
chip supports.
> Maybe you can get away with setting these to the values the driver
> would
> set and hard coding it for now just to get some output. Then you can
> ignore the corresponding registers which could simplify initial
> device
> model.
I'll take this approach.
Thanks,
Jasper Lowell.
On Thu, 2020-05-07 at 20:54 +0200, BALATON Zoltan wrote:
> On Thu, 7 May 2020, jasper.lowell@bt.com wrote:
> > I've started work on emulating the SAB 82532 ESSC2 but it's
> > unfortunately way more complex than than the 16550A. For instance,
> > it's
>
> I don't know anything about this chip so don't know if it helps but
> if
> it's any way similar to ESCC (and the ESCC2 name is not just
> marketing)
> then there's some emulation of that in hw/char/escc.c that you may
> want to
> look at.
>
> > possible to configure different baudrates for receiving and
> > transmitting. QEMU's chardev interface doesn't appear to handle
> > that.
> > QEMUSerialSetParams has a single speed value that is passed to
> > cfsetispeed and cfsetospeed. The chip also has support for stick
> > parity
> > , which aren't valid options right now either. If I'm wrong on
> > either
> > of those points please correct me. Unless there is an alternative,
> > changes to the interface may need to be made if adding this device
> > is
> > to be considered.
>
> Maybe you can get away with setting these to the values the driver
> would
> set and hard coding it for now just to get some output. Then you can
> ignore the corresponding registers which could simplify initial
> device
> model.
>
> Regards,
> BALATON Zoltan
prev parent reply other threads:[~2020-05-08 2:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 6:31 Emulating Solaris 10 on SPARC64 sun4u jasper.lowell
2020-02-05 17:33 ` Dr. David Alan Gilbert
2020-02-07 5:43 ` jasper.lowell
2020-02-08 0:03 ` BALATON Zoltan
2020-02-10 15:38 ` BALATON Zoltan
2020-02-10 19:04 ` John Snow
2020-02-10 22:32 ` Missing IRQ with bmdma on ppc/mips/sparc? (was: Re: Emulating Solaris 10 on SPARC64 sun4u) BALATON Zoltan
2020-02-25 20:55 ` IDE IRQ problem after UDMA enabled " BALATON Zoltan
2020-02-25 22:00 ` BALATON Zoltan
2020-02-25 22:12 ` Emulating Solaris 10 on SPARC64 sun4u BALATON Zoltan
2020-02-09 11:26 ` Mark Cave-Ayland
2020-02-19 3:42 ` jasper.lowell
2020-02-19 18:54 ` BALATON Zoltan
2020-02-19 20:10 ` BALATON Zoltan
2020-02-21 19:53 ` Dr. David Alan Gilbert
2020-02-28 22:05 ` BALATON Zoltan
2020-03-01 0:15 ` BALATON Zoltan
2020-05-07 14:29 ` jasper.lowell
2020-05-07 15:02 ` Artyom Tarasenko
2020-05-08 2:33 ` jasper.lowell
2020-05-08 8:51 ` Peter Tribble
2020-05-08 13:45 ` Artyom Tarasenko
2020-05-10 2:46 ` jasper.lowell
2020-05-10 9:22 ` Mark Cave-Ayland
2020-05-17 7:57 ` jasper.lowell
2020-05-17 12:37 ` Artyom Tarasenko
2020-05-18 2:56 ` jasper.lowell
2020-05-20 17:44 ` Mike Russo
2020-05-07 18:54 ` BALATON Zoltan
2020-05-08 2:55 ` jasper.lowell [this message]
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=78d72c7f09a45357b151231cba9454d6d288680d.camel@bt.com \
--to=jasper.lowell@bt.com \
--cc=atar4qemu@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=dgilbert@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=tony.nguyen@bt.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).