From: "S. Fricke" <silvio.fricke@googlemail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: request_irq fails to get interrupt 12
Date: Mon, 22 Oct 2007 19:21:46 +0200 [thread overview]
Message-ID: <20071022172146.GD11556@sfrouter> (raw)
In-Reply-To: <bfa0697f0710220947t657b209ek6f6a011cd1e6e5cf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
Hello,
> Freescale experts. Why on earth can't I request the IRQ for Timer1?
Please consule my question on [1] and the answers.
[1] http://ozlabs.org/pipermail/linuxppc-dev/2007-September/042061.html
bye
Silvio Fricke
--
-- S. Fricke ----------------------------- MAILTO:silvio.fricke@gmail.com --
Diplom-Informatiker (FH)
Linux-Entwicklung
----------------------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-22 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 16:47 request_irq fails to get interrupt 12 Alan Bennett
2007-10-22 17:21 ` S. Fricke [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 19:55 Alan Bennett
2007-10-22 20:33 ` 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=20071022172146.GD11556@sfrouter \
--to=silvio.fricke@googlemail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=silvio.fricke@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).