New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CHIP GPIO driver #1054

Merged
merged 5 commits into from Sep 13, 2016

Conversation

Projects
None yet
5 participants
@machinekoder
Member

machinekoder commented Sep 1, 2016

GPIO driver for the NextThing CHIP. Drives the CSID pins per memory map.

Mass production has started and so we need a driver. Tested with a self-compiled RT PREEMPT kernel.

@machinekoder

This comment has been minimized.

Show comment
Hide comment
@machinekoder

machinekoder Sep 1, 2016

Member

Can a build system guru please check if the integration is correct.

Member

machinekoder commented Sep 1, 2016

Can a build system guru please check if the integration is correct.

@evanmj

This comment has been minimized.

Show comment
Hide comment
@evanmj

evanmj Sep 3, 2016

Excellent! I was wondering why I bought 2 of these. I am happy to see support for it. Thanks!

evanmj commented Sep 3, 2016

Excellent! I was wondering why I bought 2 of these. I am happy to see support for it. Thanks!

@machinekoder

This comment has been minimized.

Show comment
Hide comment
@machinekoder

machinekoder Sep 3, 2016

Member

@zultron Does this look sane?

Member

machinekoder commented Sep 3, 2016

@zultron Does this look sane?

@ArcEye

This comment has been minimized.

Show comment
Hide comment
@ArcEye

ArcEye Sep 4, 2016

I have patched a branch and built this driver OK using ./configure --with-platform-chip
I assume the distribution will be via SD images, it would not be included in any packages.

Can't do anything else with it on a x86_amd64 rt-preempt system 😄
The build bit works fine.

ArcEye commented Sep 4, 2016

I have patched a branch and built this driver OK using ./configure --with-platform-chip
I assume the distribution will be via SD images, it would not be included in any packages.

Can't do anything else with it on a x86_amd64 rt-preempt system 😄
The build bit works fine.

@machinekoder

This comment has been minimized.

Show comment
Hide comment
@machinekoder

machinekoder Sep 6, 2016

Member

I wonder how the Raspberry GPIO driver is deployed. Does it hurt to add this driver to the armhf package? Would be a lot more convenient to have it in the Machinekit package.

Member

machinekoder commented Sep 6, 2016

I wonder how the Raspberry GPIO driver is deployed. Does it hurt to add this driver to the armhf package? Would be a lot more convenient to have it in the Machinekit package.

@machinekoder

This comment has been minimized.

Show comment
Hide comment
@machinekoder

machinekoder Sep 8, 2016

Member

I found and fixed some issues in the driver.

Member

machinekoder commented Sep 8, 2016

I found and fixed some issues in the driver.

@ArcEye

This comment has been minimized.

Show comment
Hide comment
@ArcEye

ArcEye Sep 13, 2016

Sorry been doing other stuff.

I wonder how the Raspberry GPIO driver is deployed. Does it hurt to add this driver to the armhf package? Would be a lot more convenient to have it in the Machinekit package.

AFAICT the other drivers that are only going to be required on armf platforms like BBB and raspberry, are built by default when the armf platform is selected.

--with-platform-socfpga 
              Build for Socfpga platform (default for ARM arch)
--with-platform-beaglebone
                      Build for Beaglebone platform (default for ARM arch)
--with-platform-raspberry
                      Build for Raspberry platform (default for ARM arch)

Because you copied the configure.ac entries for these to select your CHIP driver, that should also apply to your driver.

I will merge, I know it builds OK and we can check for its presence in the armf packages once completed.

ArcEye commented Sep 13, 2016

Sorry been doing other stuff.

I wonder how the Raspberry GPIO driver is deployed. Does it hurt to add this driver to the armhf package? Would be a lot more convenient to have it in the Machinekit package.

AFAICT the other drivers that are only going to be required on armf platforms like BBB and raspberry, are built by default when the armf platform is selected.

--with-platform-socfpga 
              Build for Socfpga platform (default for ARM arch)
--with-platform-beaglebone
                      Build for Beaglebone platform (default for ARM arch)
--with-platform-raspberry
                      Build for Raspberry platform (default for ARM arch)

Because you copied the configure.ac entries for these to select your CHIP driver, that should also apply to your driver.

I will merge, I know it builds OK and we can check for its presence in the armf packages once completed.

@ArcEye ArcEye merged commit 7aa0c92 into machinekit:master Sep 13, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@ArcEye

This comment has been minimized.

Show comment
Hide comment
@ArcEye

ArcEye Sep 13, 2016

They haven't all finished building yet, but the driver is being included in the armhf packages, so looks OK

$ INTEL-i7:/downloads# dpkg --contents machinekit-xenomai_0.1.1473781726-1mk.travis.master.git7aa0c928~1wheezy_armhf.deb | grep hal_chip

-rw-r--r-- root/root     10312 2016-09-13 17:24 ./usr/lib/linuxcnc/xenomai/hal_chip_gpio.so

ArcEye commented Sep 13, 2016

They haven't all finished building yet, but the driver is being included in the armhf packages, so looks OK

$ INTEL-i7:/downloads# dpkg --contents machinekit-xenomai_0.1.1473781726-1mk.travis.master.git7aa0c928~1wheezy_armhf.deb | grep hal_chip

-rw-r--r-- root/root     10312 2016-09-13 17:24 ./usr/lib/linuxcnc/xenomai/hal_chip_gpio.so
@machinekoder

This comment has been minimized.

Show comment
Hide comment
@machinekoder

machinekoder Sep 16, 2016

Member

Thanks. Btw. we are featured on the CHIP blog.

Member

machinekoder commented Sep 16, 2016

Thanks. Btw. we are featured on the CHIP blog.

@luminize

This comment has been minimized.

Show comment
Hide comment
@luminize

luminize Sep 16, 2016

Member

Nice @Strahlex !

On 16 Sep 2016, at 18:47, Alexander Rössler notifications@github.com wrote:

Thanks. Btw. we are featured on the CHIP blog.

Member

luminize commented Sep 16, 2016

Nice @Strahlex !

On 16 Sep 2016, at 18:47, Alexander Rössler notifications@github.com wrote:

Thanks. Btw. we are featured on the CHIP blog.

@zhivko

This comment has been minimized.

Show comment
Hide comment
@zhivko

zhivko Sep 17, 2016

Very Nice I wonder how this platform compare to BeagleBone Black in
performance - for price I see it is much cheaper.
regards

On Sat, Sep 17, 2016 at 12:25 AM, Bas de Bruijn notifications@github.com
wrote:

Nice @Strahlex !

On 16 Sep 2016, at 18:47, Alexander Rössler notifications@github.com
wrote:

Thanks. Btw. we are featured on the CHIP blog.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1054 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhKBnBdzVTMM1w2mkCRlZfX7umvELqqks5qqxdugaJpZM4JzLFV
.

zhivko commented Sep 17, 2016

Very Nice I wonder how this platform compare to BeagleBone Black in
performance - for price I see it is much cheaper.
regards

On Sat, Sep 17, 2016 at 12:25 AM, Bas de Bruijn notifications@github.com
wrote:

Nice @Strahlex !

On 16 Sep 2016, at 18:47, Alexander Rössler notifications@github.com
wrote:

Thanks. Btw. we are featured on the CHIP blog.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1054 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhKBnBdzVTMM1w2mkCRlZfX7umvELqqks5qqxdugaJpZM4JzLFV
.

@ArcEye

This comment has been minimized.

Show comment
Hide comment
@ArcEye

ArcEye Sep 17, 2016

Thanks. Btw. we are featured on the CHIP blog.

Pity they used a very old Linuxcnc graphic for Axis :(

That's a good blog on the CHIP board.
Now I have finally received all the bits for my Pine64 board, I must look into mmap GPIO on that. The /sys access works fine, just a question of figuring out the memory block location.

ArcEye commented Sep 17, 2016

Thanks. Btw. we are featured on the CHIP blog.

Pity they used a very old Linuxcnc graphic for Axis :(

That's a good blog on the CHIP board.
Now I have finally received all the bits for my Pine64 board, I must look into mmap GPIO on that. The /sys access works fine, just a question of figuring out the memory block location.

@machinekoder

This comment has been minimized.

Show comment
Hide comment
@machinekoder

machinekoder Sep 23, 2016

Member

@zhivko Performance-wise the CHIP can't hold up with the BBB. The CHIP does not feature a PRU or FPGA for offloading signal generation.

Member

machinekoder commented Sep 23, 2016

@zhivko Performance-wise the CHIP can't hold up with the BBB. The CHIP does not feature a PRU or FPGA for offloading signal generation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment