Hi Marc,
On Wed, Sep 28, 2011 at 10:05:31PM +0200, Marc Balmer wrote:
Marc
sorry :-D
On Sun, Sep 25, 2011 at 11:42:11AM +0200, Marc Balmer wrote:
I'd like to be able to set the PWM indepentently for each pin! say
specifying
70/256 on and otherwise off.
That is what gpiopwm(4)
Am 29.09.11 09:39, schrieb Reinoud Zandijk:
Hi Marc,
On Wed, Sep 28, 2011 at 10:05:31PM +0200, Marc Balmer wrote:
Marc
sorry :-D
On Sun, Sep 25, 2011 at 11:42:11AM +0200, Marc Balmer wrote:
I'd like to be able to set the PWM indepentently for each pin! say
specifying
70/256 on
Hi Mark, hi folks,
On Sun, Sep 25, 2011 at 11:42:11AM +0200, Marc Balmer wrote:
attached to an individual pin. gpioctl(8) will keep the pulse keyword,
as this is needed for hardware pulsating devices. The interface to the
gpiopwm(4) driver could be realized using three sysctl variables:
Am 28.09.11 16:08, schrieb Reinoud Zandijk:
Hi Mark, hi folks,
Marc
On Sun, Sep 25, 2011 at 11:42:11AM +0200, Marc Balmer wrote:
attached to an individual pin. gpioctl(8) will keep the pulse keyword,
as this is needed for hardware pulsating devices. The interface to the
gpiopwm(4)
I recently added code to gpio(4) on jak's request to pulse a pin in
software. The idea is, that when the hardware supports it, a pin is
pulsed by the hardware, if the underlying hardware has no pulsate
support, it can be done in software. While the current code works, I
think it is done wrong,
# Marc Balmer 2011-09-25:
I recently added code to gpio(4) on jak's request to pulse a pin in
software. The idea is, that when the hardware supports it, a pin is
pulsed by the hardware, if the underlying hardware has no pulsate
support, it can be done in software. While the current code
On 09/25/11 16:50, Jachym Holecek wrote:
# Marc Balmer 2011-09-25:
I recently added code to gpio(4) on jak's request to pulse a pin in
software. The idea is, that when the hardware supports it, a pin is
pulsed by the hardware, if the underlying hardware has no pulsate
support, it can be done
the user has to use gpioctl(8) for HW support and gpiopwm(4) for SW
implementation
Couldn't gpiopwm(4) just use the HW version if that is available?
On 09/25/11 18:59, Edgar Fuß wrote:
the user has to use gpioctl(8) for HW support and gpiopwm(4) for SW
implementation
Couldn't gpiopwm(4) just use the HW version if that is available?
if the HW supports pulsating, there is no need to attach the gpiopwm(4)
driver.
