From: Greg Ungerer <gerg@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Angelo Dureghello <angelo.dureghello@timesys.com>
Cc: Tom Rini <trini@konsulko.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
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, 7 Feb 2023 00:00:28 +1000 [thread overview]
Message-ID: <d9f468b5-a0b8-697a-05ce-8ab6a8151b68@kernel.org> (raw)
In-Reply-To: <40a0fdd71a65307e33dc3b5d8fd15d655fcb0607.camel@physik.fu-berlin.de>
Hi Adrian,
On 6/2/23 22:25, John Paul Adrian Glaubitz wrote:
> Hi Greg!
>
> On Mon, 2023-02-06 at 22:02 +1000, Greg Ungerer wrote:
>> I wish I had a 54415 based board in my collection. Would make it so
>> much easier to keep the kernel working on it :-(
>
> Maybe we can find one to buy for you. I would be happy to donate for it.
I'll gladly accept any surplus boards anyone has.
I have quite a few of the older ColdFire evaluation boards, but not all.
I only have a single M5475EVB for MMU testing currently though.
Regards
Greg
next prev parent reply other threads:[~2023-02-06 14:01 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
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 [this message]
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=d9f468b5-a0b8-697a-05ce-8ab6a8151b68@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=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