Right - I _think_ this issue is caused be a hardware problem.
I tried to do some more work on it yesterday, but the motherboard I was using refused to POST. I went out and bought a new machine and everything is working OK (without adding the function calls that Pei Lin suggested).
The new machine has totally different hardware to the old one, so it may not have been a hardware fault, but since the old hardware is unusable now I guess we'll never know...
Thanks muchly for your help.
-Al
--- On Mon, 4/20/09, Rajat Jain <Rajat.Jain@xxxxxxxxxxxx> wrote:
From: Rajat Jain <Rajat.Jain@xxxxxxxxxxxx>
Subject: RE: request_irq returns -ENOSYS
To: asmallcheesebox@xxxxxxxxx, kernelnewbies@xxxxxxxxxxxx
Date: Monday, April 20, 2009, 5:16 AM
Hi,
> I'm sure this has been working in the past, but now I get -38
> (-ENOSYS) returned from my call to request_irq. I can't for
> the life of me figure out why, although I've dug a bit and
> found that this is being returned by the following lines in
> kernel/irq/manage.c:
>
> 404: if (desc->chip == &no_irq_chip)
> 405: return -ENOSYS;
>
> I think this is telling me that the kernel doesn't know how
> to handle IRQs that my card signals, because the IRQ handling
> hardware isn't supported. Am I wrong?
Right. Basically this tells you that no interrupt controller in the
system has specified that it will be sending IRQ num "X" to the CPU.
What did you change since it was last known to be working?
Thanks,
Rajat
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
