From: Dave H. <dhy...@gm...> - 2006-11-13 06:28:37
|
What about after? On 11/12/06, Michal 'LaHcIm' Zygmunt <la...@fa...> wrote: > # modprobe proc_gpio > for pin in 46 47 69 70 72 73 81 82 83 84; do cat /proc/gpio/GPIO$pin; done > # for pin in 46 47 69 70 72 73 81 82 83 84; do cat /proc/gpio/GPIO$pin; done > 46 AF2 in clear > 47 AF1 out set > 69 AF2 out clear > 70 AF2 out clear > 72 AF2 out clear > 73 AF2 out clear > 81 GPIO in clear > 82 GPIO in clear > 83 GPIO in clear > 84 GPIO in clear Mine looks like this: # for pin in 46 47 69 70 72 73 81 82 83 84; do cat /proc/gpio/GPIO$pin; done 46 AF2 in clear 47 AF1 out set 69 AF2 out clear 70 AF2 out clear 72 AF2 out clear 73 AF2 out clear 81 GPIO in set 82 GPIO in set 83 GPIO in set 84 GPIO in clear # insmod /rs/robostix_drv.ko Robostix Driver: SVN: 1093 Compiled: Sep 22 2006 at 10:20:11 # for pin in 46 47 69 70 72 73 81 82 83 84; do cat /proc/gpio/GPIO$pin; done 46 AF2 in clear 47 AF1 out set 69 AF2 out clear 70 GPIO out set 72 GPIO out clear 73 GPIO out clear 81 GPIO out set 82 GPIO out set 83 GPIO out set 84 GPIO in clear The fact that 81 thru 84 is different isn't relevant since both sides treat the pins as inputs, so the lines are basically indeterminant. Also, when it did reset when you did it manually, was it 70 or 72 that caused it to reset. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |