From: Ben Dooks <ben@fluff.org.uk>
To: Maxin John <maxin.john@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need help on mach-ep93xx
Date: Tue, 13 Mar 2007 11:24:11 +0000 [thread overview]
Message-ID: <20070313112411.GA24508@fluff.org.uk> (raw)
In-Reply-To: <9debc4410703122224n5def90e7g4767b95b176941c0@mail.gmail.com>
On Tue, Mar 13, 2007 at 10:54:08AM +0530, Maxin John wrote:
> Hi,
>
> I have one question mach-ep93xx.
>
> In EP93xx IRQ handling part in core.c, the 2.6.19.2 kernel and
> newer kernels are configuring the 16 interrupts of the ports A & B
> together. The code is not using the interrupt capability of the port
> F which can provide 3 interrupts.
>
> Why the port F is not configured for interrupts ?
>
> Thanks in advance,
subscribe to the linux-arm-kernel list and ask
the question there, you'll find more ARM people there.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2007-03-13 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 5:24 Need help on mach-ep93xx Maxin John
2007-03-13 11:24 ` Ben Dooks [this message]
2007-03-14 9:43 ` Maxin John
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=20070313112411.GA24508@fluff.org.uk \
--to=ben@fluff.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maxin.john@gmail.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 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).