On Wednesday, April 11, 2001, at 09:06 PM, Teman Clark-Lindh wrote:
> However, nothing happens. The handler registration takes place
> successfully
> (no conflicts with touchscreen, etc), but it is never called.
(My recollection is a bit hazy on this, and I haven't looked at the code
lately. Hopefully, someone will step in to debunk any myths that I'm
about to tell.)
When that driver was written, there were promises of a Grand Unified
UCB1200 driver framework which would allow cooperative sharing of that
chip's single interrupt source. As such, absolutely no effort was made
to permit any sort of peaceful coexistance between the sa1100_switches
driver and, say, the touchscreen code. Since you mention that the
UCB1300 switch handler is successfully registered, I might guess that
some other driver is clobbering the interrupt source at the chip.
I've been doing my best not to touch the kernel recently, but if the
UCB1200 code has evolved beyond the old "all-or-nothing" model, I'll be
happy to revisit this driver. Otherwise, I'm afraid the answer to your
question is, "disable anything else having to do with the UCB1200 in
your kernel configuration."
-jd, who took care to ensure that this brain damage didn't make it into
Spot
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
