public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Christoph Hellwig <hch@infradead.org>,
	James.Bottomley@SteelEye.com,
	linux scsi <linux-scsi@vger.kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Noah Misch <noah@cs.caltech.edu>,
	linux m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k link error and NCR5380_exit()
Date: Mon, 7 Mar 2005 09:53:22 -0800	[thread overview]
Message-ID: <20050307175322.GA12907@pants.nu> (raw)
In-Reply-To: <Pine.LNX.4.61.0503072333310.27126@loopy.telegraphics.com.au>

On Tue, Mar 08, 2005 at 12:45:28AM +1100, Finn Thain wrote:
> Having qla1280.c as a guide will help, thanks. My next question is, what 
> does a NuBus architecture do in place of pci_(un)register_driver?

Eventually, you should use macio_(un)register_driver. However, I
don't have the support quite finished for mac68k. If I get some
time to work on it, I have most of the code written. It's close
enough that it should work on nubus-pmac, and I passed some
preliminary versions of the code off to them.

> My main reservation about embarking on this is that I don't think mac_scsi 
> ever actually worked under 2.6 (or 2.5?) kernels. I'm not competent enough 
> to submit a good, untested patch for a broken driver. Maybe the best thing 
> is to make it work before worrying about style. At least then I can test 
> my work.

I certainly never got it to work, but I only tried on my IIfx which
doesn't have exactly the same version of the chip anyway.

> To that end, I've included a boot log below. Maybe someone familiar with 
> the NCR5380 driver can make some sense of the failure?

Looks to me like the interrupt came in after the driver already
decided to give up for some reason. I had a big problem with that
while I was trying to fix the driver to use DMA on the IIfx. I
never did get it to give me the interrupt for dma completion
before the scsi mid layer timed out.

	Brad Boyer
	flar@allandria.com


  reply	other threads:[~2005-03-07 17:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.61.0502110155440.7310@loopy.telegraphics.com.au>
     [not found] ` <20050210171518.GA22265@pants.nu>
     [not found]   ` <Pine.LNX.4.61.0502111930340.11381@loopy.telegraphics.com.au>
     [not found]     ` <Pine.LNX.4.61.0502121539440.20941@loopy.telegraphics.com.au>
     [not found]       ` <20050212075645.GA30669@pants.nu>
     [not found]         ` <Pine.LNX.4.61.0502122135230.21876@loopy.telegraphics.com.au>
     [not found]           ` <20050213040948.GA10198@orchestra.cs.caltech.edu>
     [not found]             ` <Pine.LNX.4.61.0502131618470.25204@loopy.telegraphics.com.au>
     [not found]               ` <20050213063225.GA17415@orchestra.cs.caltech.edu>
     [not found]                 ` <Pine.LNX.4.61.0502131736300.25553@loopy.telegraphics.com.au>
     [not found]                   ` <20050213075506.GA18622@orchestra.cs.caltech.edu>
     [not found]                     ` <Pine.LNX.4.61.0502212233290.15372@loopy.telegraphics.com.au>
2005-03-07  6:30                       ` [PATCH] m68k link error and NCR5380_exit() Finn Thain
2005-03-07  6:37                         ` Christoph Hellwig
2005-03-07 13:45                           ` Finn Thain
2005-03-07 17:53                             ` Brad Boyer [this message]
2005-03-07 23:42                               ` Kenn Humborg
2005-03-08 15:16                                 ` mac_scsi boot crash, was " Finn Thain
2005-03-08 17:39                                   ` Brad Boyer
2005-03-09 12:00                                     ` [PATCH] mac_scsi boot crash fix Finn Thain
2005-03-09 12:06                                       ` Kenn Humborg

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=20050307175322.GA12907@pants.nu \
    --to=flar@allandria.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=noah@cs.caltech.edu \
    /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