linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MESH problems in 2.2.x
Date: Thu, 3 Jun 1999 15:46:12 +1000	[thread overview]
Message-ID: <199906030546.PAA00546@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.10.9906021030230.17255-100000@mercator.cs.kuleuven.ac.be> (message from Geert Uytterhoeven on Wed, 2 Jun 1999 10:47:18 +0200 (CEST))


Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:

> During boot up I now see the message:
> 
>     scsi1: device driver called scsi_done() for a syncronous reset

The reset and abort handling in the mesh driver needs to be updated;
the way the scsi mid-layer expects them to work changed during the 2.1
series but I haven't updated the mesh driver to the new way yet,
partly because I don't know exactly what the new way is. :-)

> Since the message mentions `syncronous reset' and since the old Conner doesn't
> seem to do synchronous mode, this makes me think the mesh driver fails with
> synchronous devices in 2.2.x. Is this correct? Does anyone else see this
> problem?

It's working OK for me now with a 2.3.4 kernel, having fixed ioremap
(the fix is now in vger for both the 2.2 and 2.3 branches).

If you want to disable sync mode, you could change the initializer for
mesh_sync_targets in drivers/scsi/mesh.c from 0xff to 0.

Regards,
Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-06-03  5:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-02  8:47 MESH problems in 2.2.x Geert Uytterhoeven
1999-06-03  5:46 ` Paul Mackerras [this message]
1999-06-07 11:10   ` Geert Uytterhoeven
1999-06-22 13:00     ` Geert Uytterhoeven
1999-06-23 12:13       ` Michel Lanners
1999-06-24  7:53         ` Geert Uytterhoeven
1999-06-24 21:44           ` Michel Lanners
1999-07-13 13:45       ` Geert Uytterhoeven
1999-07-14  5:09         ` Paul Mackerras
1999-07-14  8:03           ` Geert Uytterhoeven
1999-07-15  8:45           ` Geert Uytterhoeven
1999-08-02 11:14             ` Geert Uytterhoeven

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=199906030546.PAA00546@tango.anu.edu.au \
    --to=paulus@cs.anu.edu.au \
    --cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).