From: Finn Thain <fthain@fastmail.com.au>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Christoph Hellwig <hch@lst.de>,
Joshua Thompson <funaho@jurai.org>,
"David S. Miller" <davem@davemloft.net>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] m68k/mac: Replace macide driver with generic platform driver
Date: Tue, 27 Apr 2021 13:47:04 +1000 (AEST) [thread overview]
Message-ID: <9650358f-a789-7dbd-4495-1d39ff321ded@nippy.intranet> (raw)
In-Reply-To: <65f01f42-31d9-522a-e690-73d286405a01@gmail.com>
On Tue, 27 Apr 2021, Michael Schmitz wrote:
> On 26/04/21 7:37 pm, Finn Thain wrote:
> > Was macide the only IDE driver in Debian/m68k kernels without a libata
> > alternative? If so, this patch would allow you to finally drop
> > CONFIG_IDE.
> >
> There's still q40ide.c (ISA IDE interface, byte-swapped, so would need
> treatment similar to Falcon IDE). Hasn't been updated to a platform
> device yet.
>
AIUI, q40 support is not included in Debian/m68k kernel builds.
I wonder whether q40 could re-use the pata_falcon driver . I suppose
pata_falcon_set_mode() would be undesirable on q40 (?) It could be made
optional using the data parameter passed to
platform_device_register_resndata().
next prev parent reply other threads:[~2021-04-27 3:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 9:06 [PATCH] m68k/mac: Replace macide driver with generic platform driver Finn Thain
2021-04-25 10:25 ` John Paul Adrian Glaubitz
2021-04-26 7:37 ` Finn Thain
2021-04-26 7:48 ` John Paul Adrian Glaubitz
2021-04-27 1:51 ` Michael Schmitz
2021-04-27 3:47 ` Finn Thain [this message]
2021-04-27 19:54 ` Michael Schmitz
2021-04-28 6:53 ` Geert Uytterhoeven
2021-04-27 8:11 ` Sergei Shtylyov
2021-04-27 8:36 ` John Paul Adrian Glaubitz
2021-04-27 19:29 ` Michael Schmitz
2021-04-25 22:24 ` Michael Schmitz
2021-04-26 7:35 ` Finn Thain
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=9650358f-a789-7dbd-4495-1d39ff321ded@nippy.intranet \
--to=fthain@fastmail.com.au \
--cc=davem@davemloft.net \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
/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