Re: MtxOrb older models not supported (anymore ! ?)
Ethan Dicks <[email protected]> Mon, 5 Mar 2012 13:27:43 -0500
| Newsgroups | gmane.comp.sysutils.lcdproc |
|---|---|
| Message-ID | <CAALmimkNBFPBCT3nc=MyyqY6-hSu+0=fCwCdevDB=OMy-wvBcw@mail.gmail.com> |
On Mon, Mar 5, 2012 at 12:39 PM, Markus Dolze <[email protected]> wrote: > On 05.03.2012 13:21, Liselore Vermeulen wrote: >> I'm using LCDproc at my workplace for some time (a customised version of 0.4-pre9) >> where the Matrix Orbital 2041 display is the only visualisation available. >> >> We have a large number of these devices. They are MtxOrb 2041 Rev. 1.3 devices, > > Matrix Orbital displays are the reason why LCDproc exists. Therefore I > guess we will support even older devices. There has been a lot of work > at the end of the 0.4-series on the MtxOrb driver and I do not guarantee > that everything went into 0.5. As someone who was working on the code back to 3.x, even I have no idea if all the work from late 0.4 made it into 0.5. There weren't very many MtxOrb owners left by then. Most people moved to Crystal Fontz or other devices. > Two settings in LCDd.conf are important when using older devices: > > Type = lcd > hasAdjustableBacklight = no Yes. It's essential to get those right no matter what Matrix Orbital device you have. I have had a Matrix Orbital VKD204 for a long time (13 years or so). It's a VFD, not an LCD, so I can only test certain aspects of the MtxOrb driver. Having been through some driver testing about 5 years ago, I know that we tested against my VFD and had to make some assumptions about LCDs. I'm always willing to run regression tests against my ancient VFD. I keep it within a serial-cable reach of my desk. I would do the same for an LCD, but I have no older ones (just a newer Matrix Orbital model with an RGB LED backlight) -ethan