diff options
| -rw-r--r-- | module/elmcan.c | 2 | ||||
| -rw-r--r-- | readme.rst | 8 |
2 files changed, 5 insertions, 5 deletions
diff --git a/module/elmcan.c b/module/elmcan.c index 7ae344e..d0b7694 100644 --- a/module/elmcan.c +++ b/module/elmcan.c @@ -1282,7 +1282,7 @@ static int __init elmcan_init(void) { int status; - pr_info("ELM327 based best-effort CAN interface driver\n"); + pr_info("ELM327 based best effort CAN interface driver\n"); pr_info("This device is severely limited as a CAN interface, see documentation.\n"); status = tty_register_ldisc(N_ELMCAN, &elmcan_ldisc); @@ -24,13 +24,13 @@ Introduction ------------- This driver is an effort to turn abundant ELM327 based OBD interfaces -into full-fledged (as far as possible) CAN interfaces. +into full fledged (as far as possible) CAN interfaces. -Since the ELM327 was never meant to be a stand-alone CAN controller, +Since the ELM327 was never meant to be a stand alone CAN controller, the driver has to switch between its modes as quickly as possible in order to fake full-duplex operation. -As such, elmcan is a best-effort driver. However, this is more than +As such, elmcan is a best effort driver. However, this is more than enough to implement simple request-response protocols (such as OBD II), and to monitor broadcast messages on a bus (such as in a vehicle). @@ -118,7 +118,7 @@ Module parameters - ``accept_flaky_uart`` - Try to live with a bad controller or UART line Some adapters and/or their connection are unreliable. Enable this - option to try and work around the situation. This is a best-effort + option to try and work around the situation. This is a best effort workaround, so undefined behavior will likely occur sooner or later. Without this option, the driver will bail on the first unrecognized character it receives from the TTY. |