On Tue, 9 Feb 2021 at 15:59, Thomas J Powderly wrote:
> and < and > are handy for in and out
Yes but which is which?
It might be obvious to you.
I can guess which way you have defined it, possibly even correctly,
but it might not be obvious to someone who uses a right-to-left script
natively.
Hi Andy,
On 2/9/21 9:35 PM, andy pugh wrote:
On Tue, 9 Feb 2021 at 13:28, Thomas J Powderly wrote:
loadrt hal_pi_gpio pi_pins={,,,}{,,,}{,,,}
each 'quad' consists of braces enclosed data
I think that the modparam handling struggles with embedded commas
inside a single element.
I would
Anno domini 2021 Tue, 9 Feb 20:27:56 +0700
Thomas J Powderly scripsit:
> I have been working on a new version of hal_pi_gpio.
> It uses an array of structures to hold the features for each pin.
> struct pinfo
> {
> hal_bit_t pval; // the last read value for inputs, the
> desired
On Tue, 9 Feb 2021 at 13:28, Thomas J Powderly wrote:
> loadrt hal_pi_gpio pi_pins={,,,}{,,,}{,,,}
> each 'quad' consists of braces enclosed data
I think that the modparam handling struggles with embedded commas
inside a single element.
I would suggest:
loadrt hal_gpio config=12or0,1i,23i,...
On Tuesday 09 February 2021 08:27:56 Thomas J Powderly wrote:
> I have been working on a new version of hal_pi_gpio.
> It uses an array of structures to hold the features for each pin.
> struct pinfo
> {
> hal_bit_t pval; // the last read value for inputs, the
> desired output value
I have been working on a new version of hal_pi_gpio.
It uses an array of structures to hold the features for each pin.
struct pinfo
{
hal_bit_t pval; // the last read value for inputs, the
desired output value for outputs
char pnum; // the rpi header pin number
char
