From: Greg Ungerer <gerg@kernel.org>
To: Angelo Dureghello <angelo.dureghello@timesys.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
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: Mon, 6 Feb 2023 22:02:06 +1000 [thread overview]
Message-ID: <b7d1cfce-3ba3-6621-60c0-9b401a382971@kernel.org> (raw)
In-Reply-To: <CALJHbkAuaGrfiAm2jzTmrAPSM+Gq1z-gVSZ+7hgn8-e_Lr82XQ@mail.gmail.com>
On 6/2/23 18:14, Angelo Dureghello wrote:
> Hi John,
>
> On Sat, Feb 4, 2023 at 4:55 PM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
>>
>> On Mon, 2023-01-30 at 17:22 +0100, John Paul Adrian Glaubitz wrote:
>>> FWIW, m68k is still a very actively maintained architecture in the
>>> Linux kernel and userland with even LLVM and Rust having recently
>>> added support for m68k.
>>>
>>> I also own a Coldfire board myself (not sure which one without
>>> looking), so I can offer to test U-Boot patches in the future.
>>
>> So, I just found my Coldfire board and it's actually a 547x/548x EVB
>> fitted with a 5475 CPU module clocked at 266 MHz.
>>
>> I will get this board set up during the next weeks and I am happy to
>> test any Coldfire kernel patches, and eventually, U-Boot patches if
>> that board is still supported.
>>
>
> thanks a lot.
>
> Actually, i am debugging on a 54415 based board, totally dead
> using current master.
> I cannot printf, so using some gpio's for debug.
> Issue seems to happen at first puts, so, something related
> to serial port initialization. Hope to fix this soon.
I wish I had a 54415 based board in my collection. Would make it so
much easier to keep the kernel working on it :-(
Regards
Greg
>>
>> Adrian
>>
>> --
>> .''`. John Paul Adrian Glaubitz
>> : :' : Debian Developer
>> `. `' Physicist
>> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
>
>
> Regards,
> angelo
>
next prev parent reply other threads:[~2023-02-06 12:02 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 [this message]
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=b7d1cfce-3ba3-6621-60c0-9b401a382971@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