From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Patch Preview for MVME2100
Date: Mon, 05 Apr 2004 20:06:28 +0200 [thread overview]
Message-ID: <4071A024.6020005@fh-landshut.de> (raw)
In-Reply-To: <20040405172348.GS31152@smtp.west.cox.net>
- The stuff in arch/ppc/boot/mvme2100 can go.
Figured that out today, too. It won't compile anyway. Thanks.
>- The open_pic.c change shouldn't be needed either.
>
>
Maybe the CONFIG_EPIC_SERIAL_MODE should be set, shouldn't it? Will add
it tomorrow. Should I add that cascade hookup stuff even if there is no
cascaded 8259?
>- Your openpic_initsenses table looks wrong, and is probably the cause
> of the uart slowness you found. What you do is only list the IRQs for
> which you have something, and use openpic_set_sources calls to skip
> over the gaps. Look at lopec_init_IRQ and ask if you still have
> problems. I hoped to have documented that one well the first time
> around. :)
>
>
There is one problem - in the LoPEC manual all interrupts are documented
- even if marked unused (I refer to polarity and level/edge). In the
MVME2100 information about that interrupts is N/A. So should I leave
those to 0 still in the initsenses struct?
Thanks for the help,
Oliver Korpilla
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-05 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 11:27 Patch Preview for MVME2100 Oliver Korpilla
2004-04-05 17:23 ` Tom Rini
2004-04-05 18:06 ` Oliver Korpilla [this message]
2004-04-05 18:30 ` Tom Rini
2004-04-06 17:29 ` Oliver Korpilla
2004-04-06 18:47 ` Tom Rini
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=4071A024.6020005@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).