From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: [Fwd: Re: hda: lost interrupt starting with 2.6.8]
Date: Sun, 13 Mar 2005 18:49:56 +1100 [thread overview]
Message-ID: <1110700196.5787.114.camel@gaston> (raw)
-------- Forwarded Message --------
From: Vince Weaver <vince@deater•net>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: debian-powerpc@lists•debian.org <debian-powerpc@lists•debian.org>
Subject: Re: hda: lost interrupt starting with 2.6.8
Date: Sun, 13 Mar 2005 02:46:37 -0500 (EST)
> Can you tell me what is the value of CONFIG_NR_CPUS in your .config,
> also, is this file including include/linux/threads.h before
> include/linux/cpumask.h, and finally, send me privately the resulting
> binary vmlinux.
There is no CONFIG_NR_CPUS in my .config. Is that a problem? My tree is
a 2.6.4 tree that was patched incrementally, with "make oldconfig" run at
each release.
With the following patch I've managed to get 2.6.11 to boot on my
iBook2... do you still want a copy of a broken vmlinux?
Vince
--- linux/arch/ppc/syslib/open_pic.c.2.6.11 2005-03-13 01:57:00.000000000 -0500
+++ linux/arch/ppc/syslib/open_pic.c 2005-03-13 01:58:17.000000000 -0500
@@ -313,6 +313,7 @@
u_int t, i;
u_int timerfreq;
const char *version;
+ cpumask_t cpu0=CPU_MASK_CPU0;
if (!OpenPIC_Addr) {
printk("No OpenPIC found !\n");
@@ -405,7 +406,7 @@
openpic_initirq(i, 8, i+offset, (sense & IRQ_POLARITY_MASK),
(sense & IRQ_SENSE_MASK));
/* Processor 0 */
- openpic_mapirq(i, CPU_MASK_CPU0, CPU_MASK_NONE);
+ openpic_mapirq(i, cpu0, CPU_MASK_NONE);
}
/* Init descriptors */
--
Benjamin Herrenschmidt <benh@kernel•crashing.org>
next reply other threads:[~2005-03-13 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 7:49 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 6:47 [Fwd: Re: hda: lost interrupt starting with 2.6.8] 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=1110700196.5787.114.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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