From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E35EEC433F5 for ; Sat, 9 Apr 2022 04:18:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240794AbiDIEVD (ORCPT ); Sat, 9 Apr 2022 00:21:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36520 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239274AbiDIEVB (ORCPT ); Sat, 9 Apr 2022 00:21:01 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 33A01DCA92 for ; Fri, 8 Apr 2022 21:18:55 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B1DCC60B40; Sat, 9 Apr 2022 04:18:54 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 662C1C385A8; Sat, 9 Apr 2022 04:18:50 +0000 (UTC) Message-ID: <147dc6cc-1fbb-558f-8e6d-29d4327d54b4@linux-m68k.org> Date: Sat, 9 Apr 2022 14:18:48 +1000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [RFC PULL] remove arch/h8300 Content-Language: en-US To: Finn Thain , Rob Landley Cc: Daniel Palmer , Arnd Bergmann , Christoph Hellwig , Linus Torvalds , Yoshinori Sato , Linux Kernel Mailing List , linux-arch , "moderated list:H8/300 ARCHITECTURE" , "open list:TENSILICA XTENSA PORT (xtensa)" , Max Filippov , Linux-sh list , linux-m68k , Damien Le Moal , linux-riscv References: <6a38e8b8-7ccc-afba-6826-cb6e4f92af83@linux-m68k.org> <5b7687d4-8ba5-ad79-8a74-33fc2496a3db@linux-m68k.org> <8f9be869-7244-d92a-4683-f9c53da97755@landley.net> <3d5cf48c-94f1-2948-1683-4a2a87f4c697@linux-m68k.org> From: Greg Ungerer In-Reply-To: <3d5cf48c-94f1-2948-1683-4a2a87f4c697@linux-m68k.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-m68k@vger.kernel.org On 9/4/22 11:59, Finn Thain wrote: > 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 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. FWIW this will do it: qemu-system-m68k -nographic -machine mcf5208evb -kernel vmlinux That will boot an m5208evb_defconfig generated vmlinux. But you will need a user space to get a full boot to login/shell. Regards Greg