linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: Olof Johansson <olof@lixom.net>,
	linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	blackluck@ktk.bme.hu
Subject: Re: sym scsi driver problem with 2.6.26 or newer debian kernel on p610 (fwd)
Date: Wed, 24 Jun 2009 15:56:59 +1000	[thread overview]
Message-ID: <1245823019.10356.69.camel@pasglop> (raw)
In-Reply-To: <1245822826.9237.62.camel@concordia>

On Wed, 2009-06-24 at 15:53 +1000, Michael Ellerman wrote:
> Doesn't fix my machine :/
> 
That doesn't make sense ... What if you remove the bit inside the ifdef
CONFIG_MPIC_BROKEN_REGREAD in _mpic_read() ?

If that makes a difference, then it would be interesting to add a printk
in there that prints what the original value "val" is and what we have
in the shadow...

Cheers,
Ben.

  reply	other threads:[~2009-06-24  5:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14  9:10 sym scsi driver problem with 2.6.26 or newer debian kernel on p610 (fwd) Guennadi Liakhovetski
2009-06-17  9:33 ` Laszlo Fekete
2009-06-22  9:10   ` Laszlo Fekete
2009-06-23  1:18     ` Benjamin Herrenschmidt
2009-06-23  2:30       ` Benjamin Herrenschmidt
2009-06-23 21:57         ` Benjamin Herrenschmidt
2009-06-23 23:29           ` Benjamin Herrenschmidt
2009-06-24  5:53             ` Michael Ellerman
2009-06-24  5:56               ` Benjamin Herrenschmidt [this message]
2009-06-24  6:19                 ` Michael Ellerman
2009-06-24  9:31                   ` Benjamin Herrenschmidt
2009-06-27 17:46                   ` Laszlo Fekete
2009-06-27 22:54                     ` Benjamin Herrenschmidt
2009-07-06  9:05                       ` Michael Ellerman
2009-06-23  2:31 ` Benjamin Herrenschmidt

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=1245823019.10356.69.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=blackluck@ktk.bme.hu \
    --cc=debian-powerpc@lists.debian.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=olof@lixom.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 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).