diff options
| author | Romain Porte <microjoe@microjoe.org> | 2020-06-29 18:17:13 +0200 |
|---|---|---|
| committer | Romain Porte <microjoe@microjoe.org> | 2020-06-29 18:17:13 +0200 |
| commit | 68fb403e67a3511709eabaef8a6b4c372cb332a1 (patch) | |
| tree | 800e65118b171a59ce990c668751c1d38199dece | |
| parent | 11225be155ef967e7e5af613d9835156d39eb4c2 (diff) | |
| download | charlcd-68fb403e67a3511709eabaef8a6b4c372cb332a1.tar.gz charlcd-68fb403e67a3511709eabaef8a6b4c372cb332a1.zip | |
README.md: fix small typos
| -rw-r--r-- | README.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -27,8 +27,8 @@ protocol to interact with the screen over and over. This approach seems just wrong if you consider what the Linux kernel can provide in comparison. Indeed, it is the role of device drivers to properly -abstract the access to the hardware from userspace perspective. For this, -the Linux kernel uses an absraction mechanism to declare the hardware: +abstract the access to the hardware from userspace perspective. For this, +the Linux kernel uses an abstraction mechanism to declare the hardware: the *device-tree*. The *device-tree* nodes for a screen behind an I2C GPIO expander would look @@ -63,7 +63,7 @@ auxdisplay: auxdisplay { }; ``` -Once the device-tree is correctly configured, the `charlcd` driver will +Once the *device-tree* is correctly configured, the `charlcd` driver will create a `/dev/lcd` character device. The role of this library is to provide an astraction over this character @@ -74,7 +74,7 @@ with the screen — instead of going from scratch and using ioctl over # Known bugs The charlcd driver is currently not able to report screen size to userspace. -This is mitigated in the library by having a look at the device-tree entries +This is mitigated in the library by having a look at the *device-tree* entries directly. # Going further |