#331 Can't reserve irqs > 15

[Jochen Scharrlach]

I want to exclude irq 42 on an iPAQ, but the
corresponding code in rsrc_mgr.c looks like this:

[...]
static int adjust_irq(adjust_t *adj)
{
#ifdef CONFIG_PCMCIA_PROBE
int irq;
irq_info_t *info;

irq = adj->resource.irq.IRQ;
if ((irq < 0) || (irq > 15))
return CS_BAD_IRQ;
[...]

Shouldn't "irq > 15" be replaced with "irq >= NR_IRQS" ?

[David Hinds]

Logged In: YES
user_id=7760

The interrupts managed here are ISA bus interrupts, and
interrupts greater than 15 are not meaningful. Your iPAQ
does not have ISA bus interrupts. Perhaps you should give
more background: what PCMCIA bridge are you using, and why
do you think excluding (probably) the only interrupt this
bridge can actually use, would be a good idea?

(on systems that do not have an ISA bus, in all cases I know
of, the PCMCIA socket is wired to one host interrupt, and
cannot be reconfigured)

-- Dave

[Jochen Scharrlach]

Logged In: YES
user_id=822331

My problem is that I seems that I am losing interrupts on my
PCMCIA-NIC (orinoco-based) about once per second on high
load. Additionally the screen flickers when sending out much
data, so my wild guess was that there is an irq-conflict - I
would have expected that it would be possible to use another
interrupt, but it is quite possible that it is really
hard-wired. I am not quite sure what the bridge is like, it
seems to be a proprietary interface by Compaq (I think the
driver is called h3600_sleeve).

My patch didn't do anything anyway, so it isn't a bug at
all, sorry about that :)

[David Hinds]

Logged In: YES
user_id=7760

I'm pretty sure you can't change the interrupt assignment. If
you are losing interrupts, I'd first verify that you have the latest
version of the orinoco driver. Maybe check that you have a
current firmware. And report the problem on the orinoco
mailing list; someone with more experience with that driver
might have some suggestions.

I'm not sure what to make of the screen flicker. Maybe the
card is drawing too much power for the iPAQ??

I'll close this bug as the original description does not apply.

-- Dave