From: "Eno 3 Compton" <one@ecom.com>
To: linuxppc-dev@ozlabs.org
Subject: irq identification has changed from 2.6.10 to 2.6.23. an explanation is requested
Date: Wed, 10 Oct 2007 14:39:45 -0600 [thread overview]
Message-ID: <f6c0dc290710101339t30a15881t3ffbe02324006b28@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
Dear All,
I had a driver working under 2.6.10 on a mpc8248. The kernel got changed
under me to 2.6.23. Now, when I call request_irq with SIU_INT_IRQ5, which is
defined in asm-powerpc/irq.h, and once compiled and worked properly, I get
compilation errors. The compiler can't find the symbol definition because
CONFIG_PPC_MERGE is defined. I suspect the kernel guys have migrated things
to a new arrangement, which I've been unable to discern.
An explanation or advice on where to find information about this would be
hugely appreciated.
Eno Compton
[-- Attachment #2: Type: text/html, Size: 588 bytes --]
next reply other threads:[~2007-10-10 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 20:39 Eno 3 Compton [this message]
2007-10-10 20:47 ` irq identification has changed from 2.6.10 to 2.6.23. an explanation is requested Scott Wood
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=f6c0dc290710101339t30a15881t3ffbe02324006b28@mail.gmail.com \
--to=one@ecom.com \
--cc=linuxppc-dev@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).