From: Randy Vinson <rvinson@mvista.com>
To: linuxppc-embedded@lists.linuxppc.org
Cc: benh@kernel.crashing.org, paulus@samba.org
Subject: Guidance Request Regarding openpic_hookup_cascade()
Date: Fri, 23 Apr 2004 13:53:05 -0700 [thread overview]
Message-ID: <40898231.20002@mvista.com> (raw)
Greetings,
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?
Thanks,
Randy Vinson
MontaVista Software.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-04-23 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 20:53 Randy Vinson [this message]
2004-04-24 1:13 ` Guidance Request Regarding openpic_hookup_cascade() Benjamin Herrenschmidt
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=40898231.20002@mvista.com \
--to=rvinson@mvista.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.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).