LCDproc development and user support list

Text archives Help

[Lcdproc] [PATCH] MtxOrb.c - patch 3

Chronological Thread 
  • From: joris AT (Joris Robijn)
  • Subject: [Lcdproc] [PATCH] MtxOrb.c - patch 3
  • Date: Wed Sep 29 21:05:01 2004

> > The past has shown that it appears to be easier to merge small
> > changes...
> I didn't mean I would do the merging later. I was more thinking that I
> would see the 0.5 version of the driver as a blank page. But I guess
> there's the danger that times will change and I will no longer have the
> time available to work on LCDproc - and then, like you say, the two
> versions would have grown wider apart. OK, you've twisted my arm, I will
> try to do the same fix on both versions.

Maybe it's benifitial in some areas to start from scratch, while in other
areas you will keep most from the old driver. I don't consider it a bad
idea to rewrite some driver things. I don't know how "bad" the MtxOrb
driver is, but if the new one is better, fine with me. I would think you
should have a couple of good reasons to justify a rewrite from scratch.

> > I do however expect major issues with people complaining about drivers
> > not working as well as they do in 0.4.x.

At least that indicates the drivers are still used. Maybe some new
volonteers will pop up to maintain these drivers. We lack driver

> Any ideas what your most important drivers are? Hopefully there's only a
> couple?

I think the order is HD44780, CFontz, MtxOrb (still?) sed1330, t6963. And
of course curses!

> I think the best way forward is to get one or two drivers in 0.5 working
> well, then release it stating that users of those drivers should use that
> version. Hopefully there are reasons why users would want to use 0.5 over
> 0.4.5?

Certainly, read more on the development page.


Joris Robijn
<joris AT>
Mobile: +31 6 288 41 964

// To understand recursion, we must first understand

Archive powered by MHonArc 2.6.18.

Top of page