dave_w_hawkins wrote:
> I think this is 2.6 kernel specific too.
>
> Adding addition /dev/ nodes or /proc nodes is the way
> to go. In 2.6 you'd use sysfs /sys nodes.
The board is running a 2.4 kernel so if some of the suggestions are specific
for 2.6, I couldn't use them. Adding /proc nodes was the easier method.
> So did you end up adding a spinlock to protect the
> resource, or queue I/O requests and let the ISR
> update the I/O pins?
No spinlocks. I just write to a /proc node and the value is saved to an
internal variable. This variable is then used by the ISR when it updates the
I/O pins. The 500uS to 1mS delay between the proc write and the change of
state in the I/O pins is not a problem for my app.
--
Cheers!
Kevin.
http://www.ve3syb.ca/ |"What are we going to do today, Borg?"
Owner of Elecraft K2 #2172 |"Same thing we always do, Pinkutus:
| Try to assimilate the world!"
#include <disclaimer/favourite> | -Pinkutus & the Borg
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|