Hi John,
Then perhaps gpioctl and gpio-dev should be marked as ¨obsolete¨ in the
config or removed entirely? As is, it´s broken - better to have old but
working code?
Regards,
Jeroen
On 04/12/2012 01:03 AM, John Crispin wrote:
On 12/04/12 08:59, Jeroen van Bemmel wrote:
Hello,
I needed to determine which GPIO pin was connected to the reset button,
so I figured I´d use gpioctl to pull the status. However, /dev/gpio did
not exist; I traced this and found that the probe function was not being
called. Adding a platform_device called "GPIODEV" fixes this:
static struct platform_device bcm63xx_gpiodev_device = {
.name = "GPIODEV",
.id = 0,
.dev.platform_data = 0,
};
[...]
platform_device_register(&bcm63xx_gpiodev_device);
Not sure to what extend gpioctl is broken on other targets; I found
several bug reports, but most had the status "fixed".
Would you like me to submit a patch to add this?
Hi,
gpioctl is eons old and was made for 2.6.16 when gpio did not exist.
please use the generic gpio sysfs api to control gpios.
gpioctl is obseleted and we strongly suggest to not use this ancient api
John
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
