On 24 February 2017 at 21:49, BALATON Zoltan wrote:
> On Fri, 24 Feb 2017, BALATON Zoltan wrote:
>>
>> On Fri, 24 Feb 2017, Peter Maydell wrote:
>>>
>>> On 19 February 2017 at 16:35, BALATON Zoltan wrote:
Write only to allow clients to initialise these without failing
Signed-o
On Fri, 24 Feb 2017, BALATON Zoltan wrote:
On Fri, 24 Feb 2017, Peter Maydell wrote:
On 19 February 2017 at 16:35, BALATON Zoltan wrote:
Write only to allow clients to initialise these without failing
Signed-off-by: BALATON Zoltan
What's the point in write-only register values?
U-boot wr
On Fri, 24 Feb 2017, Peter Maydell wrote:
On 19 February 2017 at 16:35, BALATON Zoltan wrote:
Write only to allow clients to initialise these without failing
Signed-off-by: BALATON Zoltan
What's the point in write-only register values?
U-boot writes this register during setting up the dev
On 19 February 2017 at 16:35, BALATON Zoltan wrote:
> Write only to allow clients to initialise these without failing
>
> Signed-off-by: BALATON Zoltan
What's the point in write-only register values?
What does the real hardware do here?
If the registers are writes-ignored, there's no need to s
Write only to allow clients to initialise these without failing
Signed-off-by: BALATON Zoltan
---
hw/display/sm501.c | 42 ++
1 file changed, 42 insertions(+)
diff --git a/hw/display/sm501.c b/hw/display/sm501.c
index 2e1c4b7..16a00cc 100644
--- a/hw/disp
