qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Laurent Vivier <laurent@vivier.eu>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH] mos6522: remove anh register
Date: Sat, 14 Dec 2019 10:47:19 +0000	[thread overview]
Message-ID: <9c731591-3180-d9f8-e5f9-d1b34356664b@ilande.co.uk> (raw)
In-Reply-To: <68431265-fd33-89de-6a61-0c823beaa16e@vivier.eu>

On 13/12/2019 08:45, Laurent Vivier wrote:

> Le 13/12/2019 à 02:44, David Gibson a écrit :
>> On Thu, Dec 12, 2019 at 08:43:59PM +0100, Laurent Vivier wrote:
>>> Register addr 1 is defined as buffer A with handshake (vBufAH),
>>> register addr 15 is also defined as buffer A without handshake (vBufA).
>>>
>>> Linux kernel has a big "DON'T USE!" next to the register 1 addr
>>> definition (vBufAH), and only uses register 15 (vBufA).
>>>
>>> So remove the definition of 'anh' and use only 'a' (with VIA_REG_ANH and
>>> VIA_REG_A).
>>
>> I'm not actually following the rationale for removing the register.
>> Linux doesn't use it, but if it's part of the real hardware model we
>> should keep it, no?
> 
> It's actually two methods to access the same register (with handshake,
> without handshake).
> 
> In the datashit Register 15 is described as "Same as register 1 except
> no handshake".

Indeed, certainly my reading of the specification was that it was the same register.
I'd be inclined to add qemu_log() at unimp for the handshake registers so at least we
can easily spot if anything is using them.


ATB,

Mark.


  reply	other threads:[~2019-12-14 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 19:43 [PATCH] mos6522: remove anh register Laurent Vivier
2019-12-13  1:44 ` David Gibson
2019-12-13  8:45   ` Laurent Vivier
2019-12-14 10:47     ` Mark Cave-Ayland [this message]
2019-12-14 13:19       ` Philippe Mathieu-Daudé
2019-12-13  9:36 ` Philippe Mathieu-Daudé

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=9c731591-3180-d9f8-e5f9-d1b34356664b@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=david@gibson.dropbear.id.au \
    --cc=dgilbert@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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).