linux-mips
[Top] [All Lists]

Re: wd33c93 question

To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: wd33c93 question
From: Florian Lohoff <flo@rfc822.org>
Date: Mon, 4 Jun 2001 14:34:09 +0200
Cc: Linux/MIPS Development <linux-mips@oss.sgi.com>
In-reply-to: <Pine.LNX.4.05.10106041132520.28388-100000@callisto.of.borg>; from geert@linux-m68k.org on Mon, Jun 04, 2001 at 11:34:14AM +0200
Organization: rfc822 - pure communication
References: <20010603154706.D4043@paradigm.rfc822.org> <Pine.LNX.4.05.10106041132520.28388-100000@callisto.of.borg>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.3.15i
On Mon, Jun 04, 2001 at 11:34:14AM +0200, Geert Uytterhoeven wrote:
> > drivers/scsi/sgiwd93.c
> 
>     [...]
> 
> > So we have an incompatibility with the sgiwd93.c from the mips tree
> > and the wd33c93.c from the linus tree where we dont want the generic part
> > of the wd33c93.c to (re)write the length of the current transfer block
> > (scatter gather part) as we want it to do the whole transfer in one
> > part (From the generic wd33c93.c we dont do scatter gather).
> 
> So it's OK to protect the above lines using #ifndef CONFIG_SGIWD93_SCSI?

I guess so - I will have a look if thats probably the cause of
the fs corruption we see on SGIs with that scsi driver. From just guessing
the order of setting the values is different on SGI.

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?


<Prev in Thread] Current Thread [Next in Thread>