linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 on FSL boards
Date: Fri, 17 Aug 2007 07:50:29 -0500	[thread overview]
Message-ID: <D6CFE4FC-5112-450B-B13F-2DC40165EB71@kernel.crashing.org> (raw)
In-Reply-To: <18117.22358.723442.148999@cargo.ozlabs.ibm.com>


On Aug 17, 2007, at 3:07 AM, Paul Mackerras wrote:

> Kumar Gala writes:
>
>> The interrupt routing in the device trees for the ULI M1575 was
>> inproperly using the interrupt line field as pci function.  Fixed
>> up the device tree's to actual conform for to specification and
>> changed the interrupt mapping code so it just uses a static mapping
>> setup as follows:
>
> This is a big patch to be going in post -rc3.  Is it really fixing a
> regression or a serious bug?

Its a regression in that the ULI M1575 doesn't really work properly  
on some of these boards in certain situations.

- k

  reply	other threads:[~2007-08-17 12:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  5:03 [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 on FSL boards Kumar Gala
2007-08-17  8:07 ` Paul Mackerras
2007-08-17 12:50   ` Kumar Gala [this message]
2007-08-17 23:53     ` Paul Mackerras
2007-08-18  5:30       ` Kumar Gala
2007-09-11 17:20 ` Olof Johansson
2007-09-11 18:00   ` Kumar Gala
2007-09-11 18:22     ` Olof Johansson
2007-09-11 18:33       ` Kumar Gala
2007-09-11 18:43         ` Becky Bruce
2007-09-11 19:08           ` Kumar Gala
2007-09-11 19:22             ` Becky Bruce
2007-09-11 19:38               ` Josh Boyer
2007-09-11 19:45               ` Olof Johansson
2007-09-11 19:47               ` Kumar Gala
2007-09-11 19:36           ` Olof Johansson
2007-09-12  6:33 ` [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 onFSL boards Swarthout Edward L-SWARTHOU

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=D6CFE4FC-5112-450B-B13F-2DC40165EB71@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).