public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Michael Schmitz <schmitzmic@gmail.com>
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: Sun, 3 Aug 2014 13:43:46 +1000 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1408031314200.545@nippy.intranet> (raw)
In-Reply-To: <53DCA6AE.5060801@gmail.com>


On Sat, 2 Aug 2014, Michael Schmitz wrote:

> > I'm not particularly concerned about atari_scsi.c. I am concerned 
> > about the three forks of the core driver (not least because of the 
> > shared header) that's why I've sent patches for sun3_NCR5380 and 
> > atari_NCR5380 in the past.
> >   
> 
> OK, forget about atari_scsi.c for now. From memory, the major difference 
> between atari_NCR5380.c and the others is handling of the ST-DMA/shared 
> interrupt locking.

Yes, sun3_NCR5380.c and NCR5380.c lack support for the ST-DMA chip.

And both NCR5380.c and sun3_NCR5380.c dropped the code to support ISA 
cards, as I mentioned.

Both NCR5380.c and sun3_NCR5380.c lack merge_contiguous_buffers().

NCR5380.c lacks support for tagged queueing, while sun3_NCR5380.c and 
atari_NCR5380.c have divergent implementations of this.

sun3_NCR5380.c and atari_NCR5380.c have divergent implementations of 
NCR5380_transfer_dma().

sun3_NCR5380.c and atari_NCR5380.c share the same implementation of the 
NCR5380_main() co-routine, but it differs significantly from the algorithm 
in NCR5380.c.

Each of sun3_NCR5380.c, atari_NCR5380.c and NCR5380.c have had some clean 
up and modernization work that does not appear in any of the others.

Despite all of that, I have a patch series that attempts to unify 
atari_NCR5380.c and sun3_NCR5380.c. This seems like a sensible idea (in 
theory) given that probably only the ISA cards actually need NCR5380.c.

At some point I'll send some patches for comment, so that we might discuss 
the issues with everyone on the same page. Until then, I'd prefer to focus 
on the scsi_register() conversion.

> We need to preserve that pretty much as is, or risk serious regressions. 
> I mean, more serious trouble than I already have with the current driver 
> because of the tendency of my Falcon to muck up the SCSI chip's clock 
> signal under heavy load. Also note that there is still one of my patches 
> unmerged (under review since early this year) that is necessary to avoid 
> 'scheduling in interrupt' style panic.

Can you re-send it please?

> The rest of the differences were tweaks added by the Atari SCSI author 
> to make the driver behave with borderline standards compliant hardware 
> (long reset delay for some CD drives, tweaks to bus settle delays). 
> Probably not that critical in the first instance.
> 
> > > Might need another platform device for the ST-DMA as well ...
> > >     
> >
> > I don't think that relates to scsi_register() deprecation.
> >   
> 
> Not at all - just to the platform device conversion. Not sure I fully 
> understand what you have in mind, though.

With regards to scsi_register() conversion I'll send some patches for you 
to review once complete and tested (in mac_scsi). They will probably need 
revision after review; I'm fine with that.

-- 

  reply	other threads:[~2014-08-03  3:44 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
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 [this message]
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=alpine.LNX.2.00.1408031314200.545@nippy.intranet \
    --to=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 \
    --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