From: Greg Ungerer <gerg@kernel.org>
To: Tom Rini <trini@konsulko.com>, Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Eero Tamminen <oak@helsinkinet.fi>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Angelo Dureghello <angelo.dureghello@timesys.com>,
linux-m68k@lists.linux-m68k.org,
Joshua Thompson <funaho@jurai.org>,
Philip Blundell <philb@gnu.org>,
u-boot@lists.denx.de, Huan Wang <alison.wang@nxp.com>
Subject: Re: U-Boot support for M68K removal
Date: Tue, 31 Jan 2023 07:50:45 +1000 [thread overview]
Message-ID: <b3480cff-970b-bae3-4b8d-01cd587dcb94@kernel.org> (raw)
In-Reply-To: <Y9ga+bN+wHEI7w0m@bill-the-cat>
Hi Tom,
On 31/1/23 05:31, Tom Rini wrote:
> On Mon, Jan 30, 2023 at 08:10:36PM +0100, Geert Uytterhoeven wrote:
>> Hi Eero,
>>
>> On Mon, Jan 30, 2023 at 8:02 PM Eero Tamminen <oak@helsinkinet.fi> wrote:
>>> On 30.1.2023 18.34, Tom Rini wrote:
>>>> That's great to hear. While I started my life on m68k machines, I never
>>>> did get Linux up on one. Do the coldfire platforms you have run U-Boot
>>>> today? If so, are they already supported upstream? One of my biggest
>>>> concerns about the architecture, in U-Boot, is that I've just not heard
>>>> of anyone using it in quite some time, and we don't have any emulated
>>>> platforms either (can it be done in QEMU? We have other plaforms in CI
>>>> via QEMU) so I worry it's not working.
>>>
>>> Qemu supports both m68k and ColdFire nowadays:
>>> https://www.qemu.org/docs/master/system/target-m68k.html
>>>
>>>
>>> - Eero
>>>
>>> PS. For m68k there are also a lot of other emulators that emulate
>>> specific platforms.
>>>
>>> Aranym, 68040 Atari "clone", used a lot by Debian m68k port before Qemu
>>> got m68k support.
>>>
>>> WinAUE, 68000-68040 Amiga emulation. Unlike Aranym or Qemu, this
>>> emulates also CPU cache.
>>>
>>> Hatari, 68000-68040 Atari emulation (based on WinUAE CPU core).
>>>
>>> Previous, 68030 NeXT emulator (based on Hatari).
>>
>> But none of the platforms listed above boot using U-Boot, which is
>> what Tom is interested in...
>>
>> "qemu-system-m68k -machine help" lists a.o.:
>>
>> an5206 Arnewsh 5206
>> mcf5208evb MCF5208EVB (default)
>>
>> U-Boot still contains include/configs/M5208EVBE.h, but there are no
>> actual users...
>>
>> Angelo: so support for amcore in qemu would be nice ;-)
>
> I did a little searching after sending and I see there's been some
> patches for mcf5208evb and U-Boot, in QEMU but the last message (2019)
> was that the CPU emulation wasn't quite complete enough. But yes, one
> way or another, it would be really great to get a virtualized platform
> in CI to prevent future breakage.
FWIW the QEMU emulation of the m5208evb is good enough to run Linux.
I do a lot of kernel testing (and development!) using that.
Regards
Greg
next prev parent reply other threads:[~2023-01-30 21:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 13:49 U-Boot support for M68K removal Tom Rini
2023-01-27 14:44 ` Geert Uytterhoeven
[not found] ` <CALJHbkBqdvJu8KGKbJ2eayhiP_t607AvuwgYidhLTPY7=Mt4Hg@mail.gmail.com>
2023-01-30 16:14 ` Tom Rini
2023-01-30 16:22 ` John Paul Adrian Glaubitz
2023-01-30 16:34 ` Tom Rini
2023-01-30 18:56 ` Eero Tamminen
2023-01-30 19:10 ` Geert Uytterhoeven
2023-01-30 19:31 ` Tom Rini
2023-01-30 21:50 ` Greg Ungerer [this message]
2023-01-30 22:04 ` Tom Rini
2023-01-31 7:25 ` Angelo Dureghello
2023-01-30 19:25 ` Angelo Dureghello
2023-02-04 15:55 ` John Paul Adrian Glaubitz
2023-02-06 8:14 ` Angelo Dureghello
2023-02-06 12:02 ` Greg Ungerer
2023-02-06 12:25 ` John Paul Adrian Glaubitz
2023-02-06 12:30 ` John Paul Adrian Glaubitz
2023-02-06 13:47 ` Greg Ungerer
2023-02-06 14:00 ` Greg Ungerer
2023-02-06 12:59 ` Angelo Dureghello
2023-02-06 13:49 ` Greg Ungerer
[not found] ` <CALJHbkCTbhBrn5_XLPBADswOdhwah7vz7eke_YOr-D1spVRmyQ@mail.gmail.com>
2023-01-30 19:32 ` Tom Rini
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=b3480cff-970b-bae3-4b8d-01cd587dcb94@kernel.org \
--to=gerg@kernel.org \
--cc=alison.wang@nxp.com \
--cc=angelo.dureghello@timesys.com \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=oak@helsinkinet.fi \
--cc=philb@gnu.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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