Hi, the answers go down,.
Thank you so much for helping,
Cheers,
2012/11/30 ltynd...@tyndaleweb.com
Hi,
How much memory is in your desktops? If they're low on memory (512MB or
less) it could be something as simple as a resource / memory issue,
especially if there is something running
Hi again all,
So I finally managed to test the driver under Debian Squeeze kernel
version 3.2.0-4-amd64.
With the patch files I attached before things got compiled and installed
seemingly ok.
I now have a /dev/gpio0.
Unfortunately I can't run gpitest as I get a simple error message box
On Friday 30 November 2012 02:37:15 pm Wayne Merricks wrote:
Unable to open GPIO device.
Any pointers would be really appreciated before the PCs end up through
the nearest windows ;)
Is root running that test ?
Could be a simple permissioning problem.
If not, then just getting it to
Yep tried with root/sudo. I also have a startup script giving a+rw
permissions to /dev/gpio0 which means my normal riv users can use it
without issues.
Its all fun and games,
Wayne Merricks
The Voice Asia
On 30/11/12 19:41, Cowboy wrote:
On Friday 30 November 2012 02:37:15 pm Wayne Merricks
The only thing I can find that might be useful is the following link:
https://lkml.org/lkml/2008/1/8/213
It mentions that as well as switching ioctl in file ops to
unlocked_ioctl you need to have an explicit lock_kernel() and
unlock_kernel() between the access to the gpio card.
Its out of my
On Friday 30 November 2012 02:52:19 pm Wayne Merricks wrote:
It mentions that as well as switching ioctl in file ops to
unlocked_ioctl you need to have an explicit lock_kernel() and
unlock_kernel() between the access to the gpio card.
Its out of my rudimentary C comfort zone unfortunately.
