From: Michael Schmitz <schmitzmic@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Christoph Hellwig <hch@infradead.org>,
Michael Schmitz <schmitz@debian.org>,
Sam Creasey <sammy@sammy.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: converting the NCR5380 drivers away from scsi_register
Date: Thu, 31 Jul 2014 17:31:30 +1200 [thread overview]
Message-ID: <53D9D4B2.9080801@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1407301726430.9554@nippy.intranet>
Hi Finn,
> On Tue, 17 Jun 2014, Geert Uytterhoeven wrote:
>
>> Hi Finn,
>>
>> On Tue, Jun 17, 2014 at 10:20 AM, Finn Thain wrote:
>>>> now that you've officially taken over NCR5380 is there a chance to
>>>> look into converting the drivers away from scsi_register to the
>>>> modern scsi_host_alloc/scsi_add_host method?
>>> Have any other conversions taken place? I'm curious to see what was
>>> involved. Hopefully not a re-write, like esp_scsi (?)
>> I did a few of them in 2009:
>>
>> commit c2a24a4ca1137473971842461612e56a654e7edb
>> ("m68k: amiga - A3000 SCSI platform device conversion")
>> commit c1d288a58936cd0654844d807e53a203f4838fb4
>> ("m68k: amiga - GVP Series II SCSI zorro_driver conversion")
>> commit c737e22cde37e4e2ad126316e4aab7349a491ab3
>> ("m68k: amiga - A2091/A590 SCSI zorro_driver conversion")
>>
>> All of them without access to the hardware. So far I haven't heard any
>> complaints ;-)
> Thanks Geert. You do make it look easy to avoid regressions!
>
> sun3x_esp and mac_esp are platform devices so I guess I should convert
> sun3_scsi and mac_scsi to platform devices also. I'm not sure about
> atari_scsi, perhaps there's a different bus that can probe it. Michael?
atari_scsi is only used on TT and Falcon Atari variants. 'Testing' for
hardware presence is just checking bits from a bitmap populated at
arch_init time, that can easily be moved into a platform device setup,
much like I already do for the network drivers. Does that answer your
question?
Cheers,
Michael
>
> I see that the PCI driver (dmx3191d) and the ARM drivers (oak and
> cumana_1) have already been converted. So the remaining NCR5380 drivers
> that still use scsi_register() are the ISA cards: g_NCR5380, dtc,
> pas16 and t128.
>
> I don't have any ISA hardware. I certainly don't mind if those drivers
> ultimately get removed along with scsi_register() itself.
>
> Those ISA drivers depend on functionality in the NCR5380.c core driver
> that was discarded by the other two core driver variants (atari_NCR5380.c
> and sun3_NCR5380.c) such as DONT_USE_INTR, UNSAFE, DMA_WORKS_RIGHT,
> AUTOPROBE_IRQ, USLEEP_POLL, NCR53C400.
>
> If it were not for the ISA cards, we may not need three variations on the
> core driver.
>
next prev parent reply other threads:[~2014-07-31 5:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 14:18 converting the NCR5380 drivers away from scsi_register Christoph Hellwig
2014-06-17 8:20 ` Finn Thain
2014-06-17 8:38 ` Geert Uytterhoeven
2014-07-30 8:32 ` Finn Thain
2014-07-31 5:31 ` Michael Schmitz [this message]
2014-08-01 3:13 ` Finn Thain
2014-08-01 8:15 ` Michael Schmitz
2014-08-02 1:27 ` Finn Thain
2014-08-02 8:51 ` Michael Schmitz
2014-08-03 3:43 ` Finn Thain
2014-08-03 9:07 ` Michael Schmitz
2014-08-04 3:28 ` Finn Thain
2014-08-05 9:06 ` Michael Schmitz
2014-08-06 1:25 ` Sun3 SCSI DMA, was " Finn Thain
2014-08-06 14:42 ` Sam Creasey
2014-08-08 8:46 ` Michael Schmitz
2014-08-11 15:10 ` Sam Creasey
2014-08-13 5:29 ` Finn Thain
2014-08-13 9:14 ` Michael Schmitz
2014-08-14 1:43 ` Finn Thain
2014-08-14 8:57 ` Michael Schmitz
2014-08-15 1:46 ` Finn Thain
2014-08-15 1:51 ` Michael Schmitz
2014-08-15 2:09 ` Finn Thain
2014-08-15 3:03 ` Michael Schmitz
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=53D9D4B2.9080801@gmail.com \
--to=schmitzmic@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sammy@sammy.net \
--cc=schmitz@debian.org \
/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