On Monday 24 February 2020 08:35:38 andy pugh wrote:
> On Sat, 15 Feb 2020 at 16:27, Gene Heskett
> wrote:
>
> Quit trying to use it. For normal operation its not needed as far as I
>
> > know. I am not. I think you'll find warning in the docs about it
> > being unusable.
>
> hal_pi_gpio was impo
On Sun, 16 Feb 2020 at 16:08, Thomas J Powderly wrote:
> I now have linuxcnc 2.9 with a good hal_pi_gpio.(doesnt break on newest
> Pi revision code c03112 )
>
I feel we can add this to 2.8, as that is (still) not released and the
driver is new in that version.
I am not sure what "rev" should be
On Sat, 15 Feb 2020 at 16:27, Gene Heskett wrote:
Quit trying to use it. For normal operation its not needed as far as I
> know. I am not. I think you'll find warning in the docs about it being
> unusable.
hal_pi_gpio was imported from Machinekit recently. It's a GPIO driver, are
you confusing
I now have linuxcnc 2.9 with a good hal_pi_gpio.(doesnt break on newest
Pi revision code c03112 )
The driven pins scope out clean when running.
These pins controlled by software stepgen.
To do this , I installed a rip ( so I could make new .c components ).
I edited hal_pi_gpio.c , adding a ca
On Saturday 15 February 2020 05:55:18 Thomas J Powderly wrote:
> Hello
> I have a raspberry pi 4, 4G
> /proc/cpuinfo shows
>
> Hardware : BCM2835
> Revision : c03112 << THIS IS A PROBLEM
> Serial : 10007ef4bf9c
> Model : Raspberry Pi 4 Model B Rev 1.2
>
Hello
I have a raspberry pi 4, 4G
/proc/cpuinfo shows
Hardware : BCM2835
Revision : c03112 << THIS IS A PROBLEM
Serial : 10007ef4bf9c
Model : Raspberry Pi 4 Model B Rev 1.2
and those values will fail trying to load the hal_pi_gpio module.
When I tried
