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 6C992C433F5 for ; Sat, 9 Apr 2022 03:38:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238458AbiDIDkF (ORCPT ); Fri, 8 Apr 2022 23:40:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42928 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229549AbiDIDjy (ORCPT ); Fri, 8 Apr 2022 23:39:54 -0400 Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 82853BBA for ; Fri, 8 Apr 2022 20:37:48 -0700 (PDT) Received: by mail-qv1-xf32.google.com with SMTP id t4so2929465qvl.8 for ; Fri, 08 Apr 2022 20:37:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=0x0f.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZPMboYNoi1Tq9s1o8EjnHiPJyfdvsa8XEDzwclG05nU=; b=ZSBY1RFuqn8ZwYn/HjI0d5AJ0GZqGT3Hv1VZHxXSu+MglJWtwv8mjtrMn7Wh8GSv0y C4FRuIwfEb9kASwqWhWnwoVm65oVzbnB2dRJSLcgX9+3EAkDZRixb2gtkR1DSWR5D82u oZl1VV9b4yJeD07+AStdFPt1TKOpNhUvl3f8U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZPMboYNoi1Tq9s1o8EjnHiPJyfdvsa8XEDzwclG05nU=; b=VEwwb/aPOvNQDJBhWIC8nvBvfOeBXxbMTndit3mlNXEIsULZplkmcS4dInlTd99rCO +9yjx2UhsTor2ntXHFfQInroWpeEWbmeQRADHAZqussVRoSUvCW+b9U2jtZHZDLcRA8p PdUtooULfaVm2V0qWVF9nVxO4UGafqmIa5Lysw5kIGsprTfqCmwl5uOULQOA1fggfDXM 4S0sHACLaigVppdAZV3ixTE/Rylg3/wi9op3MjrJ77nyqYpbY/2X54FQXYyN5i0S36SY 7QEjnOH3zVI1HDROg4wDVSEHx5/1/VQDTz+Pqh+fzl8iwgFyhAe/DYW5rpH/8/6/Ot0e QEvQ== X-Gm-Message-State: AOAM533ce9L1JHWW8WgD6v50T5/0vIeR6ayxxDgWSj/xA1QQvXBG5UZZ QNLULbgSuEFSGQNuF/vEV9kt5lmP4VfkEZVQ6f0rIg== X-Google-Smtp-Source: ABdhPJx2skHaFGBmVPuWh026ZrD9+x9YgR9mbH2KjPOfAg+qXm2Dy1h2UjyHmuuULVBn29BLaloUhjCyxN7D3zqhYTA= X-Received: by 2002:ad4:5743:0:b0:441:6da8:dc5e with SMTP id q3-20020ad45743000000b004416da8dc5emr18980082qvx.13.1649475467635; Fri, 08 Apr 2022 20:37:47 -0700 (PDT) MIME-Version: 1.0 References: <6a38e8b8-7ccc-afba-6826-cb6e4f92af83@linux-m68k.org> <5b7687d4-8ba5-ad79-8a74-33fc2496a3db@linux-m68k.org> <8f9be869-7244-d92a-4683-f9c53da97755@landley.net> In-Reply-To: <8f9be869-7244-d92a-4683-f9c53da97755@landley.net> From: Daniel Palmer Date: Sat, 9 Apr 2022 12:37:36 +0900 Message-ID: Subject: Re: [RFC PULL] remove arch/h8300 To: Rob Landley Cc: Greg Ungerer , 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, On Sat, 9 Apr 2022 at 09:20, Rob Landley wrote: > 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... I couldn't work out how to define a mc68000 machine on the command line alone. There might be a way but it didn't seem like it. > (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?) Once I get QEMU to emulate a simple mc68000 system my plan is to get u-boot going (I managed to get it to build for plain mc68000 but I didn't get far enough with the QEMU bit to try booting it yet) then put together the buildroot configs to build qemu, u-boot, a kernel and rootfs that just work. Then I can hook it into CI and have it build and boot test automatically and it won't bit rot anymore. > >> 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? Dragonball uses a weird UART that doesn't seem to be compatible with any of the common ones so it needs its own driver. Cheers, Daniel