From: Dan Malek <dan@embeddededge.com>
To: akuster@dslextreme.com
Cc: ppc_devel <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC/Patch] ppc4xx_pic
Date: Sun, 14 Jul 2002 22:52:16 -0400 [thread overview]
Message-ID: <3D3238E0.5090306@embeddededge.com> (raw)
In-Reply-To: 3D31F6B2.3010900@dslextreme.com
akuster wrote:
> Basicaly I check to see if a table exists and if so, update the
> interrupt controller during ppc4xx_pic_init with the proper values.
> Since the on-chip devices are all ready setup by the bootrom or at
> least we have been assuming this is the case , I am not going to worry
> about them.
My only suggestion is to make the table always exist (removing the
"if it exists" option), and to represent all interrupts (like openpic
does). It may make the rest of the supporting software easier to
write and will serve as a source of documentation for what the boot rom
may configure. :-)
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-07-15 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 22:09 [RFC/Patch] ppc4xx_pic akuster
2002-07-15 2:52 ` Dan Malek [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=3D3238E0.5090306@embeddededge.com \
--to=dan@embeddededge.com \
--cc=akuster@dslextreme.com \
--cc=linuxppc-dev@lists.linuxppc.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).