From: Luben Tuikov <ltuikov@yahoo.com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
"Hammer, Jack" <Jack_Hammer@adaptec.com>,
Al Viro <viro@ftp.linux.org.uk>
Cc: Luben Tuikov <ltuikov@yahoo.com>,
dougg@torque.net, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix idiocy in asd_init_lseq_mdp()
Date: Mon, 25 Sep 2006 12:14:59 -0700 (PDT) [thread overview]
Message-ID: <20060925191459.55364.qmail@web31801.mail.mud.yahoo.com> (raw)
In-Reply-To: <1159206202.3463.62.camel@mulgrave.il.steeleye.com>
--- James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Mon, 2006-09-25 at 18:39 +0100, Al Viro wrote:
> > Far more interesting question: where does the hardware expect to see
> > the
> > upper 16 bits of that 32bit value? Which one it is -
> > LmSEQ_INTEN_SAVE(lseq)
> > ori LmSEQ_INTEN_SAVE(lseq) + 2?
>
> I don't honestly know. The change was made as part of a slew of changes
> by Robert Tarte at Adaptec to make the driver run on Big Endian
> platforms. I've copied Jack Hammer who's now looking after it in the
> hope that he can enlighten us.
Al,
I can see that you addressed your message to me, but Bottomley has
stepped in to answer. I can also see that Bottomley is looking
for an answer from Jack. To save an off the list correspondence,
I'll go ahead and answer your question addressed to me.
LSEQ_INTEN_SAVE is a 32 bit Little-Endian storage, thus
your original, first email on this subject is correct, and your
supposition that if the storage is 32 bit LE, then my version
is correct, is in itself correct.
No such "changes" (in the HW page writing area) are necessary in order
to make the code run in BE platforms. My version of my code
(NOT Bottomley's version of my code) has been extensively tested on
BE (PowerPC) platforms, and is working properly.
The version as seen in my code:
asd_write_reg_dword(asd_ha, LmSEQ_INTEN_SAVE(lseq),
(u32) LmM0INTEN_MASK);
is the correct way.
Good luck!
Luben
P.S. Git tells me that I needed to change two lines only,
in order to make the code run on BE platforms, the git commit
dates Wednesday Sept 28, 2005. That commit is present on
the GIT repo, then present on http://linux.adaptec.com/sas/.
next prev parent reply other threads:[~2006-09-25 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 1:57 Al Viro
2006-09-25 6:52 ` Luben Tuikov
2006-09-25 6:54 ` Luben Tuikov
2006-09-25 14:47 ` Douglas Gilbert
2006-09-25 14:59 ` Al Viro
2006-09-25 17:16 ` Luben Tuikov
2006-09-25 17:39 ` Al Viro
2006-09-25 17:43 ` James Bottomley
2006-09-25 18:29 ` Mike Anderson
2006-09-25 19:14 ` Luben Tuikov [this message]
2006-09-25 19:56 Hammer, Jack
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=20060925191459.55364.qmail@web31801.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=Jack_Hammer@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®