From: Kumar Gala <galak@kernel.crashing.org>
To: David Updegraff <dave@cray.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: swizzling pci irqs
Date: Wed, 22 Mar 2006 16:28:52 -0600 [thread overview]
Message-ID: <E895715F-A853-4A27-8076-90A1973273E2@kernel.crashing.org> (raw)
In-Reply-To: <dvsds7$ta0$1@sea.gmane.org>
On Mar 22, 2006, at 2:59 PM, David Updegraff wrote:
> Hi.
>
> If there were a noswizzle option to the kernel command line that
> resulted in pci scan simply trusting that the bootrom/u-boot had
> already
> correctly assigned the PCI irqs.... every tom,dick,harry, and
> yours-truly wouldn't have to make a new platform to define the
> swizzle-o-the-day. Or have I already missed this argument?
Sure, I do this now. Just don't build pci_auto into your pci support
and don't explicitly rescan in your pci setup. The 83xx pci code
under arch/powerpc should effective do this.
- kumar
next prev parent reply other threads:[~2006-03-22 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 20:59 swizzling pci irqs David Updegraff
2006-03-22 22:28 ` Kumar Gala [this message]
2006-03-23 16:40 ` David Updegraff
2006-03-23 17:15 ` Kumar Gala
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=E895715F-A853-4A27-8076-90A1973273E2@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dave@cray.com \
--cc=linuxppc-embedded@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).