From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org, linux-ide@vger.kernel.org
Subject: RE: locking problem in sata_sil24?
Date: Tue, 04 Mar 2008 09:58:15 +1100 [thread overview]
Message-ID: <1204585095.21545.37.camel@pasglop> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B0410A575@ismail.innsys.innovsys.com>
On Mon, 2008-03-03 at 16:44 -0600, Rune Torgersen wrote:
> Benjamin Herrenschmidt wrote:
> > On Mon, 2008-03-03 at 16:10 -0600, Rune Torgersen wrote:
> >> Hi I am trying to get PREEMPT_RT pach to wokr on my 2.6.24 kernel,
>
> > What core is in the 8280 ? At this stage, I wouldn't rule out a bug in
> > the lockdep patches, I need to do more work on them.
>
> Should be an 603e
> adn revision (from u-boot)
> CPU: MPC8280 (HiP7 Rev 14, Mask 1.0 1K49M) at 447.897 MHz
>
>
>
> I am currently compiling a LOCKDEP kernel for my x86 desktop, as it has
> the exact same SiliconImage controller on a card, so I'll see if it gets
> a similar detection.
In fact, I remember working on 64 bits lockdep, based on patches from
Johannes, but I didn't do 32 bits. I think somebody worked on it, but
now I can't find the patches...
Whoever did it can bounce them back to me ? I intend to do some more
work on this soon.
Cheers,
Ben.
next prev parent reply other threads:[~2008-03-03 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 22:10 locking problem in sata_sil24? Rune Torgersen
2008-03-03 22:10 ` Rune Torgersen
2008-03-03 22:37 ` Benjamin Herrenschmidt
2008-03-03 22:44 ` Rune Torgersen
2008-03-03 22:44 ` Rune Torgersen
2008-03-03 22:58 ` Benjamin Herrenschmidt [this message]
2008-03-03 23:13 ` Rune Torgersen
2008-03-03 23:13 ` Rune Torgersen
2008-03-03 23:28 ` Johannes Berg
2008-03-03 23:28 ` Johannes Berg
2008-03-04 14:39 ` Rune Torgersen
2008-03-04 14:39 ` Rune Torgersen
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=1204585095.21545.37.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.com \
/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.