public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-m68k@lists.linux-m68k.org, linux-scsi@vger.kernel.org
Subject: Re: mac_scsi / mac_NC5380
Date: Sun, 23 Nov 2003 10:54:33 -0800	[thread overview]
Message-ID: <20031123185433.GA2230@pants.nu> (raw)
In-Reply-To: <20031122114135.GA8147@lst.de>

On Sat, Nov 22, 2003 at 12:41:35PM +0100, Christoph Hellwig wrote:
> In mailine mac_scsi uses the generic NC5380 core, not the slightly
> modified copy mac_NC5380.c that someone created for it long time
> ago.  Is it actually working that way in some tree?  I'd love to
> get rid of mac_NC5380 if possible so we're down three from four
> slightly differrent "generic" NC5380 drivers.

I had it working in the 2.2.x tree with the standard NCR5380.[ch]
for PIO, but I was trying to get DMA working (for the IIfx) and
had to make a lot of changes to properly support DMA. I never
got the interrupt handling fixed, so I'm not sure if I actually
fixed all of it. It didn't used to compile when configured to
use REAL_DMA.

In fact, the 2.2 tree I have only has two different versions of
the core 5380 support. The atari version has to add some hooks
in odd places to make their DMA engine happy.

None of the trees I have checked out (2.2, 2.4, 2.6) actually
seem to use mac_NCR5380.c, even if it is there, but 2.4 was
never really supported for mac68k.

> If someone looked into porting the other drivers to main generic
> one that would of course be cool, especially as it got some major
> work from Alan lately and does proper looking, error handling, etc..

I'll try to look at mac_scsi again, but my list is pretty long now.

	Brad Boyer
	flar@allandria.com


      reply	other threads:[~2003-11-23 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22 11:41 mac_scsi / mac_NC5380 Christoph Hellwig
2003-11-23 18:54 ` Brad Boyer [this message]

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=20031123185433.GA2230@pants.nu \
    --to=flar@allandria.com \
    --cc=hch@lst.de \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-scsi@vger.kernel.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