From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Zang Roy-r61911 <tie-fei.zang@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>
Subject: Re: [PATCH ] powerpc: Add tsi108/9 and non standard mpic support
Date: Thu, 24 Aug 2006 20:54:17 +1000 [thread overview]
Message-ID: <1156416857.8433.244.camel@localhost.localdomain> (raw)
In-Reply-To: <1156413135.6591.14.camel@localhost.localdomain>
> > The table should still contain the entries for a normal MPIC. One can
> > build a kernel that will boot both machines with the "weird" one and
> > with the normal one. Thus CONFIG_MPIC_WEIRD shall not exclude normal
> > MPICs, though not having it does exclude weird ones. I thus would
> > suggest to keep the table as it was in your earlier patches, that is
> > with the normal MPIC mapping at 0.
> >
> > I intend to re-use that to handle another weird MPIC from some other
> > project :)
>
> That is also my target. I hope the imported mpic_info table can support
> more non-standard mpic structure.
> The following patch adds the standard MPIC entry to the table.
> I post it here.
Looks good. I still need to test it, hopefully tomorrow, then it can go
in though I'm not sure it can get into 2.6.18, we'll see.
Ben.
next prev parent reply other threads:[~2006-08-24 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 10:07 [PATCH ] powerpc: Add tsi108/9 and non standard mpic support Zang Roy-r61911
2006-08-22 17:15 ` Adrian Cox
2006-08-23 1:20 ` Zang Roy-r61911
2006-08-24 5:42 ` Zang Roy-r61911
2006-08-24 5:54 ` Benjamin Herrenschmidt
2006-08-24 9:52 ` Zang Roy-r61911
2006-08-24 10:54 ` Benjamin Herrenschmidt [this message]
2006-08-24 11:04 ` Zang Roy-r61911
2006-08-24 11:13 ` Benjamin Herrenschmidt
2006-08-25 1:37 ` Zang Roy-r61911
2006-08-25 8:43 ` [PATCH ] powerpc: mpc7448hpc2 device tree source file Zang Roy-r61911
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=1156416857.8433.244.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Xin-Xin.Yang@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tie-fei.zang@freescale.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 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).