Originally created by @therealprof on GitHub (Aug 9, 2018).
Originally assigned to: @berkus on GitHub.
As pointed out by @JohnDoneth, @kunerd crate HD44780 is doing custom bitbanging via sysfs instead of using the embedded-hal traits which means that this driver does not fulfil the criteria for a "driver crate" as mentioned on the page:
Platform agnostic crates to interface external components. These crates use the embedded-hal interface to support all the devices and systems that implement the embedded-hal traits.
We could move it down a section to the no_std crates.
@kunerd What do you think?
Originally created by @therealprof on GitHub (Aug 9, 2018).
Originally assigned to: @berkus on GitHub.
As pointed out by @JohnDoneth, @kunerd crate [HD44780](http://github.com/kunerd/clerk) is doing custom bitbanging via sysfs instead of using the `embedded-hal` traits which means that this driver does not fulfil the criteria for a "driver crate" as mentioned on the page:
> Platform agnostic crates to interface external components. These crates use the embedded-hal interface to support all the devices and systems that implement the embedded-hal traits.
We could move it down a section to the `no_std` crates.
@kunerd What do you think?
I have started porting the lib to use the embedded-hal traits some time ago, but had some issues and some discussions started on how to handle parallel ports within embedded-hal. After that I unfortunately haven't had enough time to do further work on this. I also haven't tracked the discussions on parallel ports, so I don't know the current state on that. But, I have no problem with clerk being moved to no_std.
@kunerd commented on GitHub (Aug 9, 2018):
I have started [porting](https://github.com/kunerd/clerk/issues/32) the lib to use the `embedded-hal` traits some time ago, but had some issues and some discussions started on how to handle parallel ports within `embedded-hal`. After that I unfortunately haven't had enough time to do further work on this. I also haven't tracked the discussions on parallel ports, so I don't know the current state on that. But, I have no problem with `clerk` being moved to `no_std`.
It's in the "WIP drivers" section, asking for help in porting, so it seems to be in the right spot for now.
@berkus commented on GitHub (Nov 22, 2024):
It's in the "WIP drivers" section, asking for help in porting, so it seems to be in the right spot for now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @therealprof on GitHub (Aug 9, 2018).
Originally assigned to: @berkus on GitHub.
As pointed out by @JohnDoneth, @kunerd crate HD44780 is doing custom bitbanging via sysfs instead of using the
embedded-haltraits which means that this driver does not fulfil the criteria for a "driver crate" as mentioned on the page:We could move it down a section to the
no_stdcrates.@kunerd What do you think?
@kunerd commented on GitHub (Aug 9, 2018):
I have started porting the lib to use the
embedded-haltraits some time ago, but had some issues and some discussions started on how to handle parallel ports withinembedded-hal. After that I unfortunately haven't had enough time to do further work on this. I also haven't tracked the discussions on parallel ports, so I don't know the current state on that. But, I have no problem withclerkbeing moved tono_std.@therealprof commented on GitHub (Aug 11, 2018):
@kunerd Would you mind creating a PR for the move between sections?
@berkus commented on GitHub (Nov 22, 2024):
It's in the "WIP drivers" section, asking for help in porting, so it seems to be in the right spot for now.