8000 switch from libugpio to libgpiod · Issue #109 · lcdproc/lcdproc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

switch from libugpio to libgpiod #109

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Closed
haraldg opened this issue Oct 3, 2018 · 0 comments
Closed

switch from libugpio to libgpiod #109

haraldg opened this issue Oct 3, 2018 · 0 comments

Comments

@haraldg
Copy link
Collaborator
haraldg commented Oct 3, 2018

The old sysfs gpio interface of the linux kernel is deprecated in favor of a new ioctl based API. Thus libugpio is discontinued. There is a new library libgpiod that makes interfacing the new API easier. Thus we should switch from one library to the other.

Since the addressing scheme of GPIOs is entirely different now, also driver configuration well need changes, but since the libugpio based connection type never saw much use (likely my bad for pushing libugpio shortly before it was deprecated) this shouldn't be much of a problem.

I kind of feel responsible for this situation and will look into it during the cold season. But if somebody wants to work on it sooner, just leave a note here an feel free to take it over. Should be fairly easy and beginner friendly topic to work on!
haraldg added a commit to haraldg/lcdproc that referenced this issue Apr 18, 2019
@haraldg
hd44780-gpio: switch from libugpio to libgpiod
23b320a 
libugpio used the legacy sysfs interface, which isn't safe to use on
systems with multiple gpio controllers and has other shortcomings like
needing root permission to "unexport" GPIOs. libgpiod OTOH uses the new
official ioctl interface and thus expected to stay around for a long time.
Also libgpiod is supported by more linux distributions.

On systems with only one gpio controller only a single line (the
gpiochip parameter) needs to be added to LCDd.conf. On systems with
multiple gpio controllers the gpio numbers need to be edited carefully.
However such systems weren't properly supported in the past anyway.

This closes issue lcdproc#109.

Signed-off-by: Harald Geyer <harald@ccbib.org>
@haraldg haraldg mentioned this issue Apr 18, 2019
Closed
haraldg added a commit to haraldg/lcdproc that referenced this issue Aug 23, 2021
@haraldg
Add new hd44780 connection type gpiod
62a7120 
* Add a new connection type based on libgpiod. This should be the new
  standard for anything GPIO related. However the current implementation
  only supports gpio lines on the same chip.
* Since this is a new restriction, use the new ugpio CT (previous commit)
  as fallback for the removed gpio CT.

Closes lcdproc#109, lcdproc#119.

Signed-off-by: Harald Geyer <harald@ccbib.org>
haraldg added a commit to haraldg/lcdproc that referenced this issue Aug 23, 2021
@haraldg
Add new hd44780 connection type gpiod
d9d233c 
* Add a new connection type based on libgpiod. This should be the new
  standard for anything GPIO related. However the current implementation
  only supports gpio lines on the same chip.
* Since this is a new restriction, use the new ugpio CT (previous commit)
  as fallback for the removed gpio CT.
* Rename some macros to avoid collisions.

Closes lcdproc#109, lcdproc#119.

Signed-off-by: Harald Geyer <harald@ccbib.org>
@hn hn mentioned this issue Sep 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haraldg
0