From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Randy Vinson <rvinson@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Guidance Request Regarding openpic_hookup_cascade()
Date: Sat, 24 Apr 2004 11:13:48 +1000 [thread overview]
Message-ID: <1082769227.6442.40.camel@gaston> (raw)
In-Reply-To: <40898231.20002@mvista.com>
On Sat, 2004-04-24 at 06:53, Randy Vinson wrote:
>
> In updating some of the boards for 2.6, I've encountered one
> without an 8259. I can either stub-out the call to i8359_irq() in
> my board-specific code or pull the openpic_hookup_cascade() support
> forward from 2.4. I've been told that the cascade approach is no
> longer in favor, but I have not been able to locate an alternative.
> So, does anyone have a recommendation on how to proceed?
Yes, we wanted to do better but never found the time to do so. I
suppose pulling the 2.4 approach in 2.6 is the best solution at this
point.
Ben
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-24 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 20:53 Guidance Request Regarding openpic_hookup_cascade() Randy Vinson
2004-04-24 1:13 ` Benjamin Herrenschmidt [this message]
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=1082769227.6442.40.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=rvinson@mvista.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.