For a very short period of time today I was absolutely convinced that there
was a sound conflict (since they are on the same chip, and I had it working
for about 15 minutes after I disabled sound). After further work, however, I
was unable to isolate it. (A recompile later in the day without sound didn't
work either).

I did a quick hack of the touch screen to get 9 "buttons", which should do
for the moment.  Any future efforts on my part for buttons will probably be
through modifications on the touchscreen driver.

The only other thing that'd I'd be suspicious about is the supposed big
capacitor on the Assabet. Could that possibly cause initialization side
effects on the UCB1300? The touchscreen driver seems to have a more
elaborate initialization procedure to start communicating with the UCB,
perhaps that's why it works better.

thanks for all the suggestions,
Teman

----- Original Message -----
From: "Nicolas Pitre" <[EMAIL PROTECTED]>
To: "John Dorsey" <[EMAIL PROTECTED]>
Cc: "Teman Clark-Lindh" <[EMAIL PROTECTED]>; "Linux Arm Mailing List"
<[EMAIL PROTECTED]>
Sent: Thursday, April 12, 2001 7:13 PM
Subject: Re: Assabet /dev/switches


>
>
> On Wed, 11 Apr 2001, John Dorsey wrote:
>
> > (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.
>
> That should be a myth now.
>
>
> Nicolas
>
>
> _______________________________________________
> http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
> Please visit the above address for information on this list.
>


_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.

Reply via email to