From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [Qemu-devel] Booting Raspbian on RPi emulation
Date: Tue, 20 Aug 2019 17:14:39 +0200 [thread overview]
Message-ID: <9b099b2c-07d6-9733-fe90-2c2a974efc44@redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1908201648370.56910@zero.eik.bme.hu>
Hey Zoltan,
On 8/20/19 4:50 PM, BALATON Zoltan wrote:
> On Tue, 15 Jan 2019, Philippe Mathieu-Daudé wrote:
>> On 1/15/19 7:29 PM, BALATON Zoltan wrote:
>>> On Thu, 29 Nov 2018, BALATON Zoltan wrote:
>>>> Then I've tried the same with the pll patches posted by Philippe
>>>> Mathieu-Daudé here:
>>>>
>>>> http://lists.nongnu.org/archive/html/qemu-devel/2018-11/msg00191.html
>>>>
>>>> on top of v3.1.0-rc3 which helped to get rid of the cprman warnings
>>>
>>> Will these patches be merged eventually? These seem to at least get rid
>>> of some annoying warnings in Linux boot dmesg.
>>
>> I'll respin this series addressing Peter's comments.
>>
>> Thanks for reminding me ;)
>>
>> Phil.
>
> While you're at raspi patches maybe I remind you again of the above :-)
> I think I haven't seen these being merged yet but correct me if I'm wrong.
You are correct :)
I did address the issue reported by Peter regarding the CPRMAN block.
Guenter tried the series and reported issue with the A2W block (he did
implement it, basically to return 0x10001 for a pair of registers, but I
hadn't implemented it).
Now I have a basic A2W implemented, but I can't reproduce the error
Guenter reported, so I was waiting for more spare time to invest on
this. Anyhow meanwhile I can post my work as RFC.
Regards,
Phil.
next prev parent reply other threads:[~2019-08-20 15:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 20:29 [Qemu-devel] Booting Raspbian on RPi emulation BALATON Zoltan
2018-11-30 0:43 ` Philippe Mathieu-Daudé
2018-11-30 1:27 ` Guenter Roeck
2018-11-30 2:42 ` BALATON Zoltan
2018-11-30 3:39 ` Guenter Roeck
2018-11-30 12:36 ` BALATON Zoltan
2019-01-15 18:29 ` BALATON Zoltan
2019-01-15 18:54 ` Philippe Mathieu-Daudé
2019-03-04 17:58 ` BALATON Zoltan
2019-08-20 14:50 ` BALATON Zoltan
2019-08-20 15:14 ` Philippe Mathieu-Daudé [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-18 21:53 Ben Hekster
2018-12-18 22:34 ` BALATON Zoltan
2018-12-19 13:17 ` Peter Maydell
2018-12-19 17:46 ` Ben Hekster
2018-12-19 18:43 ` Peter Maydell
2018-12-19 19:36 ` Ben Hekster
2018-12-19 19:42 ` Ben Hekster
2018-12-20 2:14 ` BALATON Zoltan
2019-01-27 19:27 ` Peter Maydell
2019-01-27 23:13 ` BALATON Zoltan
2019-01-28 10:24 ` Peter Maydell
2019-01-28 15:30 ` BALATON Zoltan
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=9b099b2c-07d6-9733-fe90-2c2a974efc44@redhat.com \
--to=philmd@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=linux@roeck-us.net \
--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 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).