From: Joshua Lamorie <jpl@xiphos.ca>
To: Andrei Konovalov <akonovalov@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Edge Interrupts (Virtex-II Pro)
Date: Mon, 07 Feb 2005 20:29:50 +0000 [thread overview]
Message-ID: <4207CFBE.2000109@xiphos.ca> (raw)
In-Reply-To: <42035D27.50901@ru.mvista.com>
Andrei Konovalov wrote:
> As this code is not board specific at all,
> I would move it to arch/ppc/syslib/xilinx_pic.c:ppc4xx_pic_init().
> Does it sound reasonable (I'll prepare the patch this weekend then)?
This sounds useful, since I am using a custom developed board using the
Virtex-II Pro. Unfortunately, the patch wouldn't help me much because I
am doing my interrupt setup for most of my custom devices within
modules. You see my hardware has a Virtex-II Pro and a Virtex-II with a
shared (logically) address space (OPB). I have cascaded interrupt
controllers (ask me if anyone wants the code). So it is quite often that
I have a changed hardware and therefore require different drivers.
Rather than downloading to flash the 700k kernel each time while I am
developing, I just download the 6k - 20k modules. Then I store them in
onboard NOR flash.
That's a long way of saying YES, isn't it?
Joshua
--
Xiphos Technologies
(514) 848-9640 x227
(514) 848-9644 fax
www.xiplink.com
_______________________________________________
The information transmitted is intended only for the
person or entity to which it is addressed and may contain
confidential and/or privileged material. If you have
received this in error, please contact the sender and delete
this communication and any copy immediately. Thank you.
prev parent reply other threads:[~2005-02-07 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 2:48 Edge Interrupts (Virtex-II Pro) Joshua Lamorie
2005-02-04 11:31 ` Andrei Konovalov
2005-02-07 20:29 ` Joshua Lamorie [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=4207CFBE.2000109@xiphos.ca \
--to=jpl@xiphos.ca \
--cc=akonovalov@ru.mvista.com \
--cc=linuxppc-embedded@ozlabs.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).