From: James Bottomley <James.Bottomley@steeleye.com>
To: Andrew Vasquez <praka@users.sourceforge.net>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: qla1280 endiannes and 64/32bit fixes
Date: 18 Jan 2004 09:35:40 -0500 [thread overview]
Message-ID: <1074436541.1756.8.camel@mulgrave> (raw)
In-Reply-To: <20040118062157.GA11083@praka.local.home>
On Sun, 2004-01-18 at 01:21, Andrew Vasquez wrote:
> That NVRAM setting really has no functional meaning for the card or
> Linux driver. I believe it was an artifact from some ancient
> (non-linux) driver. In essence, the ha flag simply indicates the
> which type of IOCBs are used to initiate the CDB transfer.
Well, since there are still no published specs, I had to guess...
> Here's a small patch, not sure if its going to solve your problem
> though. I'll look some more tomorrow.
I tried the patch, but the behaviour is still the same.
What I see is that the returned data from actual data transfer
instructions is full of NULLs (presumably either because there was no
transfer, or the transfer was to the wrong location---although the fact
that the IOMMU doesn't halt the machine does tend to deny the latter).
I'm also using a qla1280 (not a 12160) if that helps.
James
next prev parent reply other threads:[~2004-01-18 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 23:40 qla1280 endiannes and 64/32bit fixes James Bottomley
2004-01-18 2:43 ` Jeremy Higdon
2004-01-18 3:16 ` James Bottomley
2004-01-18 6:21 ` Andrew Vasquez
2004-01-18 7:33 ` Jeremy Higdon
2004-01-18 14:54 ` James Bottomley
2004-01-18 21:59 ` Jes Sorensen
2004-01-19 17:40 ` Christoph Hellwig
2004-01-19 21:13 ` Jes Sorensen
2004-01-18 14:35 ` James Bottomley [this message]
2004-01-19 8:54 ` Jes Sorensen
2004-01-18 7:08 ` Jeremy Higdon
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=1074436541.1756.8.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=praka@users.sourceforge.net \
/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.