linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ayman El-Khashab <ayman@elkhashab.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: help with unhandled IRQ error with mpt2sas driver and powerpc 460EX
Date: Fri, 06 Nov 2009 20:47:44 -0600	[thread overview]
Message-ID: <4AF4DFD0.3080604@elkhashab.com> (raw)
In-Reply-To: <1256689358.11607.139.camel@pasglop>

On 10/27/2009 7:22 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2009-10-27 at 12:27 -0500, Ayman El-Khashab wrote:
>   
>> The first problem I noticed is that the physical address is read into a 
>> 32 bit variable, but the 460ex has a 36 bit bus so the ioremap would 
>> always fail.  I've change the defn of chip_phys in mpt2sas_base.h to u64 
>> and that cleared up that issue.
>>     
>
> That looks indeed like a common driver bug. Please make sure you submit
> the fix upstream. The "right" type to use is resource_size_t in fact.
>
>   
Thank you Benjamin for your help.  The info was passed onto the 
maintainer and they were able to use it
to improve their driver.  In the background, the mpt2sas was brought up 
on the canyonlands/460ex.  The
biggest thing turned out to be an #ifdef in the code that referred to 
BITS_32 to determine whether to prog
the high and low of the DMA addresses.  Once that was adjusted, it did 
function and detect the sas drive.

      reply	other threads:[~2009-11-07  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 17:27 help with unhandled IRQ error with mpt2sas driver and powerpc 460EX Ayman El-Khashab
2009-10-28  0:22 ` Benjamin Herrenschmidt
2009-11-07  2:47   ` Ayman El-Khashab [this message]

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=4AF4DFD0.3080604@elkhashab.com \
    --to=ayman@elkhashab.com \
    --cc=linuxppc-dev@lists.ozlabs.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).