From: Finn Thain <fthain@linux-m68k.org>
To: Rob Landley <rob@landley.net>
Cc: Greg Ungerer <gerg@linux-m68k.org>,
Daniel Palmer <daniel@0x0f.com>, Arnd Bergmann <arnd@arndb.de>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@lists.sourceforge.jp>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [RFC PULL] remove arch/h8300
Date: Sat, 9 Apr 2022 11:59:57 +1000 (AEST) [thread overview]
Message-ID: <3d5cf48c-94f1-2948-1683-4a2a87f4c697@linux-m68k.org> (raw)
In-Reply-To: <8f9be869-7244-d92a-4683-f9c53da97755@landley.net>
On Fri, 8 Apr 2022, Rob Landley wrote:
> On 4/5/22 08:07, Greg Ungerer wrote:
> > On 5/4/22 13:23, Daniel Palmer wrote:
> >> On Mon, 4 Apr 2022 at 22:42, Greg Ungerer <gerg@linux-m68k.org> wrote:
> >>> But we could consider the Dragonball support for removal. I keep it
> >>> compiling, but I don't use it and can't test that it actually works.
> >>> Not sure that it has been used for a very long time now. And I
> >>> didn't even realize but its serial driver (68328serial.c) was
> >>> removed in 2015. No one seems too have noticed and complained.
> >>
> >> I noticed this and I am working on fixing it up for a new Dragonball
> >> homebrew machine. I'm trying to add a 68000 machine to QEMU to make
> >> the development easier because I'm currently waiting an hour or more
> >> for a kernel to load over serial. It might be a few months.
>
> I've been booting Linux on qemu-system-m68k -M q800 for a couple years
> now? (The CROSS=m68k target of mkroot in toybox?)
>
> # cat /proc/cpuinfo
> CPU: 68040
> MMU: 68040
> FPU: 68040
> Clocking: 1261.9MHz
> BogoMips: 841.31
> Calibration: 4206592 loops
>
> It certainly THINKS it's got m68000...
>
Most 68040 processor variants have a built-in MMU and the m68k "nommu"
Linux port doesn't support them. The nommu port covers processors like
68000, Dragonball etc. whereas the m68k "mmu" port covers 680x0 where x is
one of 2,3,4,6 with MMU.
> $ qemu-system-m68k -cpu ?
> cfv4e
> m5206
> m5208
> m68000
> m68010
> m68020
> m68030
> m68040
> m68060
> any
>
> (I'd love to get an m68k nommu system working but never sat down and
> worked out a kernel .config qemu agreed to run, plus compiler and libc.
> Musl added m68k support but I dunno if that includes coldfire?)
>
I could never figure out how to boot a coldfire machine in qemu either.
There was no documentation about that back when I attempted it but maybe
things have improved since.
> >> It looked like 68328serial.c was removed because someone tried to
> >> clean it up and it was decided that no one was using it and it was
> >> best to delete it. My plan was to at some point send a series to fix
> >> up the issues with the Dragonball support, revert removing the serial
> >> driver and adding the patch that cleaned it up.
> >
> > Nice. I will leave all the 68000/68328 code alone for now then.
>
> The q800 config uses CONFIG_SERIAL_PMACZILOG. Seems to work fine?
>
That driver would work on certain 68000 systems e.g. early Macs. (And IIRC
someone did once boot a customized Linux kernel on a Mac SE...)
next prev parent reply other threads:[~2022-04-09 2:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 6:52 [RFC PULL] remove arch/h8300 Christoph Hellwig
2022-03-08 8:19 ` Arnd Bergmann
2022-04-03 12:43 ` Christoph Hellwig
2022-04-04 13:07 ` Arnd Bergmann
2022-04-04 13:09 ` John Paul Adrian Glaubitz
2022-04-04 13:22 ` Geert Uytterhoeven
2022-04-04 23:34 ` Damien Le Moal
2022-04-06 21:25 ` Rob Landley
2022-04-07 7:17 ` Arnd Bergmann
2022-04-07 7:47 ` John Paul Adrian Glaubitz
2022-04-07 7:52 ` Christoph Hellwig
2022-04-07 8:34 ` Finn Thain
2022-04-04 13:41 ` Greg Ungerer
2022-04-05 3:23 ` Daniel Palmer
2022-04-05 13:07 ` Greg Ungerer
2022-04-09 0:24 ` Rob Landley
2022-04-09 1:59 ` Finn Thain [this message]
2022-04-09 4:18 ` Greg Ungerer
2022-04-10 7:26 ` Rob Landley
2022-04-10 8:08 ` Rob Landley
2022-04-14 0:49 ` Greg Ungerer
2022-04-09 3:37 ` Daniel Palmer
2022-04-10 7:13 ` Rob Landley
2022-04-09 4:14 ` Greg Ungerer
2022-04-04 17:57 ` Max Filippov
2022-04-04 19:01 ` Arnd Bergmann
2022-04-04 19:14 ` Max Filippov
2022-04-04 19:35 ` Arnd Bergmann
2022-04-04 19:44 ` Arnd Bergmann
2022-04-04 20:56 ` Max Filippov
2022-04-04 20:48 ` Max Filippov
2022-04-04 23:32 ` Damien Le Moal
2022-04-05 21:26 ` Guenter Roeck
2022-04-05 22:01 ` Arnd Bergmann
2022-04-06 0:12 ` Guenter Roeck
2022-05-06 14:07 ` Geert Uytterhoeven
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=3d5cf48c-94f1-2948-1683-4a2a87f4c697@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=damien.lemoal@wdc.com \
--cc=daniel@0x0f.com \
--cc=gerg@linux-m68k.org \
--cc=hch@infradead.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=rob@landley.net \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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).