From: Olof Johansson <olof@lixom•net>
To: Jimi Xenidis <jimix@watson•ibm.com>
Cc: linuxppc-dev@ozlabs•org, paulus@samba•org
Subject: Re: [PATCH] powerpc: MPIC: support more than 256 sources
Date: Thu, 25 Jan 2007 16:16:58 -0600 [thread overview]
Message-ID: <20070125221658.GA22587@lixom.net> (raw)
In-Reply-To: <4E97B8B2-51B5-4914-9203-534006D3F5BD@watson.ibm.com>
On Thu, Jan 25, 2007 at 04:37:31PM -0500, Jimi Xenidis wrote:
> Why is this a flag and not just passed into mpic_alloc()?
I didn't want to make it automatic because the openpic specification says
you only have to support 8-bit vectors. So if there's an implementation
out there with 256 sources and only 8-bit vectors (and we put IPI/timers
above 256), things will break instead of the uppermost sources just not
being usable/valid.
If noone is worried about that, then I'm fine with doing it automatically
instead.
-Olof
next prev parent reply other threads:[~2007-01-25 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 21:38 [PATCH] powerpc: MPIC: support more than 256 sources Olof Johansson
2007-01-25 21:37 ` Jimi Xenidis
2007-01-25 22:16 ` Olof Johansson [this message]
2007-01-26 0:49 ` Michael Ellerman
2007-01-29 2:58 ` Olof Johansson
2007-01-29 5:33 ` [PATCH] [v2] " Olof Johansson
2007-01-29 7:23 ` Michael Ellerman
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=20070125221658.GA22587@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=jimix@watson$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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