How bad is it to specify 2 drivers but only have the hardware for one LCD connected?
I'm setting up a system that may have a CFontz633 serial or usb connected. So I was thinking of just listing both CFontz633 and CFontzPacket configured for serial and usb respectively. Then letting LCDd figure out which is there so I don't have to try and figure that out by some other means. Is that bad?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-06-08
I may have answered my own question. It doesn't seem good. It seems it's doing double work on the one present lcd.
The heartbeat and cursor are twice as fast and the keyboard's slightly sticky.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LCDd does not support auto-detection for drivers (or displays). For your case use the CFontzPacket driver solely. CFontz633 is deprecated and has been superseded by CFontzPacket driver.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How bad is it to specify 2 drivers but only have the hardware for one LCD connected?
I'm setting up a system that may have a CFontz633 serial or usb connected. So I was thinking of just listing both CFontz633 and CFontzPacket configured for serial and usb respectively. Then letting LCDd figure out which is there so I don't have to try and figure that out by some other means. Is that bad?
I may have answered my own question. It doesn't seem good. It seems it's doing double work on the one present lcd.
The heartbeat and cursor are twice as fast and the keyboard's slightly sticky.
LCDd does not support auto-detection for drivers (or displays). For your case use the CFontzPacket driver solely. CFontz633 is deprecated and has been superseded by CFontzPacket driver.