[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFEAcA8C0WN5FwaW2kfWiRm1T8wML_fWXDKqRXP-Lv_P7ysy8A@mail.gmail.com>
Date: Fri, 24 May 2019 10:08:09 +0100
From: Peter Maydell <peter.maydell@...aro.org>
To: Aaro Koskinen <aaro.koskinen@....fi>
Cc: Philippe Mathieu-Daudé <philmd@...hat.com>,
Thomas Huth <thuth@...hat.com>,
Corentin Labbe <clabbe.montjoie@...il.com>,
Tony Lindgren <tony@...mide.com>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
QEMU Developers <qemu-devel@...gnu.org>,
lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Qemu-devel] Running linux on qemu omap
On Thu, 23 May 2019 at 19:36, Aaro Koskinen <aaro.koskinen@....fi> wrote:
> Cheetah works with serial console. I tried with console on display,
> and it seems to boot up, and the frame buffer window gets correctly
> sized but for some reason it just stays blank.
As a general question, when you're doing these tests are you
using a kernel image that is known to work on real hardware?
One problem we have with some of these older QEMU platforms
is that it turns out that QEMU is only tested with the kernel,
and the kernel support for the platform is only tested with
QEMU, and so you get equal and opposite bugs in QEMU and the
kernel that cancel each other out and don't get noticed...
(On the QEMU side these platforms are all basically orphaned:
if somebody submits patches to fix bugs we'll review them,
but they're unlikely to get a great deal of attention otherwise.
They're also quite near the top of the "maybe we'll just
deprecate and then delete these" list, since we have not
historically had any working guest images to test against.
If there's a real userbase that wants them to continue to
exist that's a different matter, of course.)
thanks
- PMM
Powered by blists - more mailing lists