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 08FC3C433FE for ; Sat, 9 Apr 2022 02:00:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238197AbiDICCT (ORCPT ); Fri, 8 Apr 2022 22:02:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52456 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229991AbiDICCS (ORCPT ); Fri, 8 Apr 2022 22:02:18 -0400 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E6DECB0A4C; Fri, 8 Apr 2022 19:00:11 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id AC6DA5C0191; Fri, 8 Apr 2022 22:00:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 08 Apr 2022 22:00:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=9lxjt1eCK1sCUN2U3 ZA/uMQai3qIWY0P3RCwD0Y1H10=; b=ImVsVJDYieuJviuvTYfjN3zmcVnC0yBVc gAf3Vp0QRJeXVTBir2b9FRv1iFfcePyIo+zqL6qc87macmxsggOkaXpmTxRaLQzD ZBZD7Gwe+y1JpIbJ2s+dW21UbYcL8DcgJHpNcCkh6wSzpnBrnqOhr4vwh9PuoU4A nAik+VpMvmKlwCSK7KJzkah40P7uFkMqCI8CCJZpwSCbqpoBgaVAcA+n4azJcn9X LKiX2+Kh1Ps+phv0VLnmp8JS4ZO5iLDr+pKOzV+WthoX8YcJsRkiRa5vx3qDV0pD lr6kcjvM6tvT99BAQM4vIc6WvNcgaaYPyY1SLyqwNr1t46Rx52B5A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudekuddggeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffujgfkfhggtgesthdtredttddtvdenucfhrhhomhephfhinhhnucfv hhgrihhnuceofhhthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgheqnecuggftrfgrth htvghrnhepffduhfegfedvieetudfgleeugeehkeekfeevfffhieevteelvdfhtdevffet uedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepfh hthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 8 Apr 2022 22:00:04 -0400 (EDT) Date: Sat, 9 Apr 2022 11:59:57 +1000 (AEST) From: Finn Thain To: Rob Landley cc: Greg Ungerer , 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 Subject: Re: [RFC PULL] remove arch/h8300 In-Reply-To: <8f9be869-7244-d92a-4683-f9c53da97755@landley.net> Message-ID: <3d5cf48c-94f1-2948-1683-4a2a87f4c697@linux-m68k.org> References: <6a38e8b8-7ccc-afba-6826-cb6e4f92af83@linux-m68k.org> <5b7687d4-8ba5-ad79-8a74-33fc2496a3db@linux-m68k.org> <8f9be869-7244-d92a-4683-f9c53da97755@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org 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. > >> 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...)