From: Richard Hirst <rhirst@linuxcare.com>
To: Matthew van de Werken <mvdw73@one.net.au>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: FW: [parisc-linux] How do I use the FW scsi on 735?
Date: Wed, 25 Apr 2001 09:12:04 +0100 [thread overview]
Message-ID: <20010425091204.J985@linuxcare.com> (raw)
In-Reply-To: <002301c0cd1d$a6d3add0$1401a8c0@peewee>; from mvdw73@one.net.au on Wed, Apr 25, 2001 at 10:21:17AM +1000
On Wed, Apr 25, 2001 at 10:21:17AM +1000, Matthew van de Werken wrote:
> Hi Richard:
>
> I added the patch (I assume I added it correctly - the resulting vmlinux was
> different), and ran the new kernel, with no change. The FW scsi is still not
> recognised.
Shame :( The Zalon driver is the one you are interested in. My B180
with a Bluefish (Zalon based) FWD card runs the sim700, zalon, and
sym53c8xx drivers all at the same time, no problem.
It's possible I got the parameters wrong in my patch; the aim is to
cause drivers/scsi/zalon7xx.c:zalon_scsi_callback() to get called
for your interface. It could be that is getting called but failing
for some reason. If it is called, you should at least be getting
a line
......: Zalon vers field is ......
output on boot.
If you don't see that, perhaps you can investigate by adding a few
printk()'s to see what I got wrong.
zalon7xx_detect() is surely getting called, and that uses register_driver()
in arch/parisc/kernel/drivers.c to try and match your cards parameters
against one of the entries in zalon_scsi_drivers[]. Try and figure out
why that match is not succeeding for your scsi interface.
Richard
next prev parent reply other threads:[~2001-04-25 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 23:08 FW: [parisc-linux] How do I use the FW scsi on 735? van de Werken, Matthew (DEM, PH)
2001-04-23 16:02 ` Richard Hirst
2001-04-23 17:51 ` Matthew Wilcox
2001-04-23 19:50 ` Richard Hirst
2001-04-23 21:08 ` Richard Hirst
2001-04-25 0:21 ` Matthew van de Werken
2001-04-25 8:12 ` Richard Hirst [this message]
2001-04-25 9:48 ` Matthew van de Werken
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=20010425091204.J985@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=mvdw73@one.net.au \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.