All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Blue Swirl <blauwirbel@gmail.com>, Bob Breuer <breuerr@mc.net>,
	Anthony Liguori <aliguori@amazon.com>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCHv2 1/2] sun4m: Add Sun CG3 framebuffer and corresponding OpenBIOS FCode ROM
Date: Mon, 17 Feb 2014 12:50:12 +0000	[thread overview]
Message-ID: <53020584.9050004@ilande.co.uk> (raw)
In-Reply-To: <CAEgOgz6m1+pMZY6UaxSok3bh-g9nw_C_NK_Ei43DoUwhkuuxSw@mail.gmail.com>

On 14/02/14 14:54, Peter Crosthwaite wrote:

>> The short answer is "we don't know" because we don't have any documentation.
>
> Sigh.... This has happened quite a lot lately.
>
> If the kernel driver has macros, re-use them as much as possible. If
> you have a vague idea on whats, what, a few well invented names would
> help the device self-documentation.

Okay. I now have a revised version which borrows macro names from the 
Linux and BSD drivers which I think should be more readable. I'll post 
the revised version to the list shortly.

>>> Your hander switch statements stride in 4, are you only doing this for
>>> your one exception case of that one-byte big-endian access I commented
>>> earlier.
>>
>>
>> Yes, that is correct.
>>
>
> Should you trap misaligned accesses then?

Over the weekend I found out that the non-BT458 accesses (addr >= 0x10) 
are done as byte accesses and so byte accesses do need to be allowed to 
these registers. My interpretation of reading the SBus documentation is 
that on real hardware the bus converts accesses for you, and so I don't 
think a trap would be suitable here. Also I've not found an image (yet) 
that attempts bad accesses in this way across my OpenBIOS ISO test suite...


ATB,

Mark.

  reply	other threads:[~2014-02-17 12:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 16:38 [Qemu-devel] [PATCHv2 0/2] sun4m: Implement Sun CG3 framebuffer for QEMU Mark Cave-Ayland
2014-02-08 16:38 ` [Qemu-devel] [PATCHv2 1/2] sun4m: Add Sun CG3 framebuffer and corresponding OpenBIOS FCode ROM Mark Cave-Ayland
2014-02-09  4:14   ` Peter Crosthwaite
2014-02-09 13:35     ` Mark Cave-Ayland
2014-02-14 14:54       ` Peter Crosthwaite
2014-02-17 12:50         ` Mark Cave-Ayland [this message]
2014-02-17 16:18           ` Bob Breuer
2014-02-09 14:41   ` Peter Maydell
2014-02-09 15:19     ` Mark Cave-Ayland
2014-02-09 15:33       ` Peter Maydell
2014-02-17 12:33         ` Mark Cave-Ayland
2014-02-09 15:10   ` Andreas Färber
2014-02-09 15:24     ` Mark Cave-Ayland
2014-02-09 15:39       ` Andreas Färber
2014-02-10  8:20       ` Paolo Bonzini
2014-02-17 12:43         ` Mark Cave-Ayland
2014-02-17 12:54           ` Paolo Bonzini
2014-02-08 16:38 ` [Qemu-devel] [PATCHv2 2/2] sun4m: Add Sun CG3 framebuffer initialisation function Mark Cave-Ayland
2014-02-09 15:32   ` Andreas Färber
2014-02-17 12:30     ` Mark Cave-Ayland
2014-02-19 21:23       ` Mark Cave-Ayland

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=53020584.9050004@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=aliguori@amazon.com \
    --cc=atar4qemu@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=breuerr@mc.net \
    --cc=peter.crosthwaite@xilinx.com \
    --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.