[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.21.1906040954330.40@nippy.intranet>
Date: Tue, 4 Jun 2019 10:05:44 +1000 (AEST)
From: Finn Thain <fthain@...egraphics.com.au>
To: Michael Schmitz <schmitzmic@...il.com>
cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
scsi <linux-scsi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: [PATCH 5/7] scsi: mac_scsi: Fix pseudo DMA implementation, take
2
On Tue, 4 Jun 2019, Michael Schmitz wrote:
> Hi Finn,
>
> On 3/06/19 7:40 PM, Finn Thain wrote:
> >
> > > There are several other drivers that contain pieces of assembler code.
> > >
> > Does any driver contain assembler code for multiple architectures? I was
> > trying to avoid that -- though admittedly I don't yet have actual code for
> > the PDMA implementation for mac_scsi for Nubus PowerMacs.
> >
> I've seen that once, for one of the ESP drivers that were supported on both
> m68k and ppc (APUS, PPC upgrade to Amiga computers). But that driver was
> removed long ago (after 2.6?).
>
> In that case, the assembly file did reside in drivers/scsi/. That still
> appears to be current practice (see drivers/scsi/arm/acornscsi-io.S).
>
The presence of that file would be an argument for adding
drivers/scsi/m68k/. This seems to be begging the question.
Since there's no clear policy, I'll combine the two files and avoid the
question for now.
--
> Cheers,
>
> ??? Michael
>
>
>
Powered by blists - more mailing lists