public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: 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: Tue, 5 Apr 2022 23:07:10 +1000	[thread overview]
Message-ID: <5b7687d4-8ba5-ad79-8a74-33fc2496a3db@linux-m68k.org> (raw)
In-Reply-To: <CAFr9PXkk=8HOxPwVvFRzqHZteRREWxSOOcdjrcOPe0d=9AW2yQ@mail.gmail.com>

Hi Daniel,

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.
> 
> 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.

Regards
Greg


  reply	other threads:[~2022-04-05 15:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Yib9F5SqKda/nH9c@infradead.org>
     [not found] ` <CAK8P3a1dUVsZzhAe81usLSkvH29zHgiV9fhEkWdq7_W+nQBWbg@mail.gmail.com>
     [not found]   ` <YkmWh2tss8nXKqc5@infradead.org>
2022-04-04 13:07     ` [RFC PULL] remove arch/h8300 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 [this message]
2022-04-09  0:24             ` Rob Landley
2022-04-09  1:59               ` Finn Thain
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

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=5b7687d4-8ba5-ad79-8a74-33fc2496a3db@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=damien.lemoal@wdc.com \
    --cc=daniel@0x0f.com \
    --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=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