GPIO_WriteOE

There is a new call GPIO_WriteOE. Previously Output Enable was set inside GPIO_WriteData and cleared inside GPIO_ReadData. So need existing programs be changed?

https://www.riscosopen.org/wiki/documentation/show/GPIO%20for%20Raspberry%20Pi

https://www.riscosopen.org/wiki/documentation/show/GPIO%20SWI%20Calls

There is a new call GPIO_WriteOE

I think you’ll find that there is a newer module, and replacements of the SWIs. So programs written using the old module (pre-2019) will need revision.

So programs written using the old module (pre-2019) will need revision.

Good Grief! Who made that decision? And, Why?

I think you’ll find that there is a newer module, and replacements of the SWIs.

Which newer module are you referring to? As far as I can tell, the most recent change to the git repository for the GPIO module is from 2017, and the GPIO_WriteOE SWI has been present since the original import in 2014.

Indeed. Checking my CPUClock module, it has been using the WriteOE and ReadOE SWIs for some time.

So programs written using the old module (pre-2019) will need revision.
Good Grief! Who made that decision? And, Why?

So I might be mis-remembering, but I think there was a GPIO module produced by Tank, and that later GPIO was built into the main distro. That built-in module was different from Tanks’ initial one.

It’s possible I’m confusing this with another part of the system though.

GPIO_WriteOE has always been part of the module. When I originally wrote it for the Beagle the OE register was individual. On the PI, the OE call just sets the “mode” as the I/O is part of that register. This was kept in the new module, so any software that used the base calls would still work unchanged.