lcd4linux-users — lcd4linux users

Re: [lcd4linux] lcdproc - lcd4linux

[Michael R. <re...@eu...>]

 >> From: Jan Kloppenburg [mailto:ja...@ph...]

 >> I have LCDproc working with my HD44780 and it was quite a
 >> work to get done
 >> with that! My LCD uses winamp wiring, at least for LCDproc. I
 >> have googeld
 >> everything, but I cannot find a Wiring scheme for lcd4linux
 >> compilant to the
 >> WinAmp scheme of LCDproc. On this issue the docs are not very
 >> helpful at
 >> lcd4linux.sf.net. When I find out how to do, I'll drop a mail.

Did you succeed?

 >>
 >> Anyone has an idea how to realize that? I'd be glad about tips for
 >> sourcecode-changes that would manage it. Or even better just
 >> the right
 >> settings for the Wire.xy-parameters.

Luis.F.Correia schrieb:
>>From my Bering uClibc router setup file:
> 
> Wire.RW GND
> Wire.RS INIT
> 
> This corresponds to winamp style connection.

Thanks, Luis! I've added this as an "wiring example" to the docs at 
lcd4linux.sf.net. I hope they are correct. otherwise I will forward any 
complains to you :-)

bye, Michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

RE: [lcd4linux] lcdproc - lcd4linux

[Luis.F.Correia <Lui...@se...>]

From my Bering uClibc router setup file:

Wire.RW GND
Wire.RS INIT

This corresponds to winamp style connection.

> -----Original Message-----
> From: Jan Kloppenburg [mailto:ja...@ph...]
> Sent: quinta-feira, 14 de Agosto de 2003 00:25
> To: lcd...@li...
> Subject: [lcd4linux] lcdproc - lcd4linux
> 
> 
> Hi!
> 
> I have LCDproc working with my HD44780 and it was quite a 
> work to get done 
> with that! My LCD uses winamp wiring, at least for LCDproc. I 
> have googeld 
> everything, but I cannot find a Wiring scheme for lcd4linux 
> compilant to the 
> WinAmp scheme of LCDproc. On this issue the docs are not very 
> helpful at 
> lcd4linux.sf.net. When I find out how to do, I'll drop a mail.
> 
> I'd like to use lcd4linux because it gives more freedom in 
> configuring the 
> displayed infos. I really like the horizontal divided bars :) 
> 
> Anyone has an idea how to realize that? I'd be glad about tips for 
> sourcecode-changes that would manage it. Or even better just 
> the right 
> settings for the Wire.xy-parameters.
> 
> Thanx, janK
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet
> _072303_01/01
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
> 

[lcd4linux] lcdproc - lcd4linux

[Jan K. <ja...@ph...>]

Hi!

I have LCDproc working with my HD44780 and it was quite a work to get don=
e=20
with that! My LCD uses winamp wiring, at least for LCDproc. I have googel=
d=20
everything, but I cannot find a Wiring scheme for lcd4linux compilant to =
the=20
WinAmp scheme of LCDproc. On this issue the docs are not very helpful at=20
lcd4linux.sf.net. When I find out how to do, I'll drop a mail.

I'd like to use lcd4linux because it gives more freedom in configuring th=
e=20
displayed infos. I really like the horizontal divided bars :)=20

Anyone has an idea how to realize that? I'd be glad about tips for=20
sourcecode-changes that would manage it. Or even better just the right=20
settings for the Wire.xy-parameters.

Thanx, janK

RE: [lcd4linux] PID file handling (was: rpl_malloc?)

[Luis.F.Correia <Lui...@se...>]

> Hi Luis,
> 
> >>>We do have /proc, but one of our security fixes, 
> >>grsecurity, disables
> >>>access to /proc/kcore.
> >>
> >>Hmm... I do not "access" it. I just call 'stat("/proc/kcore", 
> >>&buf)'. I 
> >>don't understand why this is disabled, I don't see any 
> >>security reasons 
> >>here.
> > 
> > If you have /proc/kcore you can open it and read/write the memory
> > positions...
> 
> Ok, I understand. grsecurity does not disbale access, but diables 
> /proc/kcore as a whole?

Yes, that's it.

BTW, grsec disables most 'critical' aspects of writing into the kernel
itself

> 
> 
> >>>>>The daemon must know about the 'pid' file. can you add support?
> 
> Done, but in CVS only. Could you please test? As soon as I've 
> got your 
> Ok, I will release 0.9.10

Cool, I'll try it tonight.

Re: [lcd4linux] PID file handling (was: rpl_malloc?)

[Michael R. <re...@eu...>]

Hi Luis,

>>>We do have /proc, but one of our security fixes, 
>>grsecurity, disables
>>>access to /proc/kcore.
>>
>>Hmm... I do not "access" it. I just call 'stat("/proc/kcore", 
>>&buf)'. I 
>>don't understand why this is disabled, I don't see any 
>>security reasons 
>>here.
> 
> If you have /proc/kcore you can open it and read/write the memory
> positions...

Ok, I understand. grsecurity does not disbale access, but diables 
/proc/kcore as a whole?


>>>>>The daemon must know about the 'pid' file. can you add support?

Done, but in CVS only. Could you please test? As soon as I've got your 
Ok, I will release 0.9.10

bye, Michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

> >>>in our system we do not have /prog/kcore, so lots of info=20
> >>do not appear.
> >>The only client that uses /proc/kcore is "Ram" (forgot about=20
> >>the token=20
> >>now), it uses "sizeof(/proc/kcore)" because /proc/meminfo=20
> gives wrong=20
> >>results here.
> > We do have /proc, but one of our security fixes,=20
> grsecurity, disables
> > access to /proc/kcore.
>=20
> Hmm... I do not "access" it. I just call 'stat("/proc/kcore",=20
> &buf)'. I=20
> don't understand why this is disabled, I don't see any=20
> security reasons=20
> here.

If you have /proc/kcore you can open it and read/write the memory
positions...

>=20
> > We will find a way to display the correct amount of system memory.
>=20
> Well, I've to change this thing anyway, because I recently=20
> noticed that=20
> with "highmem" (or whatever this stuff is called) gives wrong results =

> with the sizeof(kcore) approach.
>=20
> Anybody has got a hint how to detect the "real" amount of=20
> memory built=20
> into a PC?
>=20
> >>>>From the docs and the token list, i cannot find the=20
> >>equivalent of 'uptime'.
> >>No. This is a good example for a plugin. have a look at the=20
> >>"%x" tokens...
>=20
> There's another thread "Text overlay problem", looks like this guy=20
> already has written (or stolen :-) such a plugin.
>=20
>=20
>  >>my
>  >>notebook was stolen during a flight from d=FCsseldorf to graz. =
Shit!
>  > Very bad indeed, I hope you can sue the travel agency for that...
> No, I can't. Nobody can. It's explicitly stated in their=20
> "Bef=F6rderungsbedingungen" (what's the english word?) that =
electronic=20

"Terms of use"?

> devices such as computers are not assured. And even if they would be, =

> not based on their value, but only on weight! Strange...
>=20
> >>>The daemon must know about the 'pid' file. can you add support?
> > Some changes must be made until we consider it production package.
> > The most important is the start-stop thing...
>=20
> Ok, I will implement this stuff really soon (at least I'll try to).
>=20
> Anybody with hints where one could steal^Hlook up good code=20
> for pid file=20
> handling?

No. well at least no now... i'll keep you posted.

>=20
> What should happen if there are two instances of lcd4linux=20
> running? Two=20
> pid files?

This should not happen. At least on a router.

Re: [lcd4linux] rpl_malloc?

[Michael R. <re...@eu...>]

Hi,


Luis.F.Correia schrieb:
> Quick reply ;)

By accident. Sitting in the office without my notebook doesn't make too=20
much sense :-(

>>>in our system we do not have /prog/kcore, so lots of info=20
>>do not appear.
>>The only client that uses /proc/kcore is "Ram" (forgot about=20
>>the token=20
>>now), it uses "sizeof(/proc/kcore)" because /proc/meminfo gives wrong=20
>>results here.
> We do have /proc, but one of our security fixes, grsecurity, disables
> access to /proc/kcore.

Hmm... I do not "access" it. I just call 'stat("/proc/kcore", &buf)'. I=20
don't understand why this is disabled, I don't see any security reasons=20
here.

> We will find a way to display the correct amount of system memory.

Well, I've to change this thing anyway, because I recently noticed that=20
with "highmem" (or whatever this stuff is called) gives wrong results=20
with the sizeof(kcore) approach.

Anybody has got a hint how to detect the "real" amount of memory built=20
into a PC?

>>>>From the docs and the token list, i cannot find the=20
>>equivalent of 'uptime'.
>>No. This is a good example for a plugin. have a look at the=20
>>"%x" tokens...

There's another thread "Text overlay problem", looks like this guy=20
already has written (or stolen :-) such a plugin.


 >>my
 >>notebook was stolen during a flight from d=FCsseldorf to graz. Shit!
 > Very bad indeed, I hope you can sue the travel agency for that...
No, I can't. Nobody can. It's explicitly stated in their=20
"Bef=F6rderungsbedingungen" (what's the english word?) that electronic=20
devices such as computers are not assured. And even if they would be,=20
not based on their value, but only on weight! Strange...

>>>The daemon must know about the 'pid' file. can you add support?
> Some changes must be made until we consider it production package.
> The most important is the start-stop thing...

Ok, I will implement this stuff really soon (at least I'll try to).

Anybody with hints where one could steal^Hlook up good code for pid file=20
handling?

What should happen if there are two instances of lcd4linux running? Two=20
pid files?


bye, Michael

--=20
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

Re: [lcd4linux] Text Overlay Problem

[Michael R. <re...@eu...>]

Hi James, Hi List,

[I'm cc:ing this to the list again, because I'd need some help from 
other CrystalFontz users]

you had this problem:

 >I'm having a problem though... I'm sure it's with the way I've got
 >things configured...
 >
 >I'm using a CrystalFontz 634 by the way..
 >
 >When scrolling, the new line does not clear the previous line.  If the
 >previous line had data that went to the end of the line and the next
 >line, say has data that goes half way, the data from the previous line
 >after the halfway mark remains.
 >
 >Example:
 >
 >If I have a line that reads:
 >
 >Up: 21 days 19:54
 >
 >Which then scrolls up one line and the new line at the bottom reads:
 >
 >Disk   |    19:54
 >
 >
 >So my question is:  Is there a way that I can force a line to be >cleared
 >initially before the new line is written?


I Asked you for your lcd4linux.conf, here it is:

> Display 634
> Port /dev/lcd
> #Speed 9600
> Backlight 100
> Rows 5
> Scroll 1
> Turn 10000
> 
> 
> x1 uptime.pl
> Row1 %x1
> Row2 "Busy %cb%% $r10cs+cb"
> Row3 "Disk%dm $R10dr+dw"
> Row4 "Net %nm $R10nr+nw"
> Row5 "CPU Temp: %s1c"
> #Row6 "Load%l1%L$r10l1"
> 
> Tick 100
> Tack 500
> Tau 500
> 
> Overload 2.0
> 
> Sensor1 /proc/sys/dev/sensors/it87-isa-0290/temp1
> Sensor1_min 30
> Sensor1_max 100


I had to modify it a bit to meet the needs of my MatrixOrbital. But the 
problem does not arise here. Maybe because I don't have your 
"uptime.pl". Could you please provide this script, too?

herp [author of the crystalfontz driver], anywhere out there? Your email 
adress is invalid...

If all doesn't help, I'm afraid I have to rewrite the crystalfontz 
driver. It's the only driver not using the "general bar" functions. And 
I have to admit that I don't really understand herp's code here :-(


bye, Michael


-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

Quick reply ;)

> -----Original Message-----
> From: Michael Reinelt [mailto:re...@eu...]=20
> Sent: Thursday, August 07, 2003 4:24 PM
> To: Luis.F.Correia
> Cc: lcd...@li...
> Subject: Re: [lcd4linux] rpl_malloc?
>=20
>=20
> Hi Luis,
>=20
> > it does work ;)
> Fine!
>=20
> > it needs parport_pc + parport + ppdev.
> Thats what I would have told you.
>=20
I know that now, i didn't RTFM enough ;)

> > in our system we do not have /prog/kcore, so lots of info=20
> do not appear.
> The only client that uses /proc/kcore is "Ram" (forgot about=20
> the token=20
> now), it uses "sizeof(/proc/kcore)" because /proc/meminfo gives wrong =

> results here.
>=20
> Or do you mean you don't have /proc at all? That would be bad...
>=20

We do have /proc, but one of our security fixes, grsecurity, disables
access to /proc/kcore.

We will find a way to display the correct amount of system memory.

> >>From the docs and the token list, i cannot find the=20
> equivalent of 'uptime'.
> > Are there any plans to add it soon?
> No. This is a good example for a plugin. have a look at the=20
> "%x" tokens...

I will.

>=20
> > One other thing, we use the Debian start-stop-daemon script=20
> to start, stop
> > and restart our daemons.
> > The daemon must know about the 'pid' file. can you add support?
> I will do so. But not really soon, because I've run into a=20
> problem: my=20
> notebook was stolen during a flight from d=FCsseldorf to graz. Shit!

Very bad indeed, I hope you can sue the travel agency for that...

> > I'm not quite sure now of the exact needs, but i can tell=20
> you tomorrow.
> Fine, tell me tomorrow :-)
>=20
> > Thanks for this great software, it is possible that you=20
> will see it soon as
> > one of our add-on packages.
> This would be great!
>=20
> btw, who is "we"? what's your "main package"?

We, the Bering uClibc team.

http://leaf.sourceforge.net/mod.php?mod=3Duserpage&menu=3D910&page_id=3D=
36


>=20
> anyway, I will place a linkt to whatever-it-is on the=20
> lcd4linux homepage :-)

Please, put the link only when we have a finished package. :)
I'm testing it now.
Some changes must be made until we consider it production package.
The most important is the start-stop thing...

Have fun!

Re: [lcd4linux] rpl_malloc?

[Michael R. <re...@eu...>]

Hi Luis,

> it does work ;)
Fine!

> it needs parport_pc + parport + ppdev.
Thats what I would have told you.

> in our system we do not have /prog/kcore, so lots of info do not appear.
The only client that uses /proc/kcore is "Ram" (forgot about the token=20
now), it uses "sizeof(/proc/kcore)" because /proc/meminfo gives wrong=20
results here.

Or do you mean you don't have /proc at all? That would be bad...

>>From the docs and the token list, i cannot find the equivalent of 'upti=
me'.
> Are there any plans to add it soon?
No. This is a good example for a plugin. have a look at the "%x" tokens...

> One other thing, we use the Debian start-stop-daemon script to start, s=
top
> and restart our daemons.
> The daemon must know about the 'pid' file. can you add support?
I will do so. But not really soon, because I've run into a problem: my=20
notebook was stolen during a flight from d=FCsseldorf to graz. Shit!

> I'm not quite sure now of the exact needs, but i can tell you tomorrow.
Fine, tell me tomorrow :-)

> Thanks for this great software, it is possible that you will see it soo=
n as
> one of our add-on packages.
This would be great!

btw, who is "we"? what's your "main package"?

anyway, I will place a linkt to whatever-it-is on the lcd4linux homepage =
:-)

bye, michael

--=20
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

Michael, 

it does work ;)

it needs parport_pc + parport + ppdev.

I have some complains...

in our system we do not have /prog/kcore, so lots of info do not appear.

From the docs and the token list, i cannot find the equivalent of 'uptime'.
Are there any plans to add it soon?

One other thing, we use the Debian start-stop-daemon script to start, stop
and restart our daemons.
The daemon must know about the 'pid' file. can you add support?

I'm not quite sure now of the exact needs, but i can tell you tomorrow.


Thanks for this great software, it is possible that you will see it soon as
one of
our add-on packages.

Take care!

> -----Original Message-----
> From: Michael Reinelt [mailto:re...@eu...] 
> Sent: Wednesday, August 06, 2003 9:41 AM
> To: Luis.F.Correia
> Cc: lcd...@li...
> Subject: Re: [lcd4linux] rpl_malloc?
> 
> 
> Hi,
> 
> >>c 99 0 /dev/parport0
> > 
> > That is done with mknod, right?
> 
> Yes.
> 
> > And when the parport module is loaded (which is not built 
> in the kernel),
> > all will work?
> 
> I think so, yes. If not, let me know.
> 
> good luck!
> 
> bye, michael
> 
> -- 
> netWorks                                          Vox: +43 316  698260
> Michael Reinelt                                   Fax: +43 316  692343
> Geisslergasse 4                                   GSM: +43 676 3079941
> A-8045 Graz, Austria                          e-mail: re...@eu...
> 

RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

Michael,

can you provide me with the correct modules relevant to make
lcd4linux work using ppdev?

I'm somewhat confused, sorry.

> -----Original Message-----
> From: Michael Reinelt [mailto:re...@eu...] 
> Sent: Wednesday, August 06, 2003 9:41 AM
> To: Luis.F.Correia
> Cc: lcd...@li...
> Subject: Re: [lcd4linux] rpl_malloc?
> 
> 
> Hi,
> 
> >>c 99 0 /dev/parport0
> > 
> > That is done with mknod, right?
> 
> Yes.
> 
> > And when the parport module is loaded (which is not built 
> in the kernel),
> > all will work?
> 
> I think so, yes. If not, let me know.
> 
> good luck!
> 
> bye, michael
> 
> -- 
> netWorks                                          Vox: +43 316  698260
> Michael Reinelt                                   Fax: +43 316  692343
> Geisslergasse 4                                   GSM: +43 676 3079941
> A-8045 Graz, Austria                          e-mail: re...@eu...
> 

Re: [lcd4linux] rpl_malloc?

[Michael R. <re...@eu...>]

Hi,

>>c 99 0 /dev/parport0
> 
> That is done with mknod, right?

Yes.

> And when the parport module is loaded (which is not built in the kernel),
> all will work?

I think so, yes. If not, let me know.

good luck!

bye, michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

Michael, 

> 
> Hi Luis,
> 
> >>Hmm... I looked things up on the internet, and found this a little 
> >>glitch or bug in the autoconf area.
> >>
> >>Could you please try to comment out the "AC_FUNC_MALLOC" line from 
> >>configure.in?
> > 
> > I did commented out the #define malloc rpl_malloc in config.h, and
> > all went well
> 
> Fine. But I'd really like you to test my suggestion, because config.h 
> will be newly created with a 'configure'-run.

I'll do so later on.
My devel sys is stabler at home ;)

> 
> > Our firewall's filesystem is in RAM and is rebuilt on every boot.
> > Meaning that all /dev entries must be created also.
> > 
> > I need some help here, to use parport.o and to have the device
> > correctly created, what do I need to do?
> 
> Are you using devfs? THen all /dev entries will be created 
> automagically.
> 

No, we are not (yet) using devfs...

> Without devfs, you'll have to create the device manually. I'm 
> not shure 
> whats the correct name, but I'd suggest:
> 
> c 99 0 /dev/parport0
> c 99 1 /dev/parport1
> c 99 2 /dev/parport2
> 

That is done with mknod, right?
And when the parport module is loaded (which is not built in the kernel),
all will work?

> Of course you have to change the "Port" entry in the lcd4linux.conf.

I thought so...

Re: [lcd4linux] rpl_malloc?

[Michael R. <re...@eu...>]

Hi Luis,

>>Hmm... I looked things up on the internet, and found this a little 
>>glitch or bug in the autoconf area.
>>
>>Could you please try to comment out the "AC_FUNC_MALLOC" line from 
>>configure.in?
> 
> I did commented out the #define malloc rpl_malloc in config.h, and
> all went well

Fine. But I'd really like you to test my suggestion, because config.h 
will be newly created with a 'configure'-run.

> Our firewall's filesystem is in RAM and is rebuilt on every boot.
> Meaning that all /dev entries must be created also.
> 
> I need some help here, to use parport.o and to have the device
> correctly created, what do I need to do?

Are you using devfs? THen all /dev entries will be created automagically.

Without devfs, you'll have to create the device manually. I'm not shure 
whats the correct name, but I'd suggest:

c 99 0 /dev/parport0
c 99 1 /dev/parport1
c 99 2 /dev/parport2

Of course you have to change the "Port" entry in the lcd4linux.conf.


bye, Michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

> [...]
> > dvb.c: In function `DVB':
> > dvb.c:57: warning: implicit declaration of function `error'
> 
> This has been fixed in CVS. But it's only a warning :-)

No problem. I do tend to ignore such errors

> > lcd4linux.o: In function `main':
> > /bering/lcd4linux-0.9.9/lcd4linux.c:308: undefined 
> reference to `rpl_malloc'
> > collect2: ld returned 1 exit status
> 
> Hmm... I looked things up on the internet, and found this a little 
> glitch or bug in the autoconf area.
> 
> Could you please try to comment out the "AC_FUNC_MALLOC" line from 
> configure.in?
> 

I did commented out the #define malloc rpl_malloc in config.h, and
all went well

Now I do have another issue, since our firewall distro came out,
Bering-uClibc, i have been using lcdproc as a primary display.

But now that we have secured our firewall with the grsecurity
patches, 'previledge io' (ioperm()) does not work anymore...

So, logically i switched to test LCD4linux, using the parport
device.

Our firewall's filesystem is in RAM and is rebuilt on every boot.
Meaning that all /dev entries must be created also.

I need some help here, to use parport.o and to have the device
correctly created, what do I need to do?

Thanks!

Re: [lcd4linux] rpl_malloc?

[Michael R. <re...@eu...>]

Hi Luis,

> I'm trying to compile lcd4linux-0.9.9 with uClibc 0.9.20, and i get this
> exact error.
[...]
> dvb.c: In function `DVB':
> dvb.c:57: warning: implicit declaration of function `error'

This has been fixed in CVS. But it's only a warning :-)

> lcd4linux.o: In function `main':
> /bering/lcd4linux-0.9.9/lcd4linux.c:308: undefined reference to `rpl_malloc'
> collect2: ld returned 1 exit status

Hmm... I looked things up on the internet, and found this a little 
glitch or bug in the autoconf area.

Could you please try to comment out the "AC_FUNC_MALLOC" line from 
configure.in?

TIA, Michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

Re: [lcd4linux] Text Overlay Problem

[Michael R. <re...@eu...>]

Hi James,

> I'm having a problem though... I'm sure it's with the way I've got
> things configured...

I'm not shure...

> I'm using a CrystalFontz 634 by the way..
This may be the problem. The CryFon Driver differs a lot from all other 
drivers. And I don't have any CrystalFontz display here to test with...

> When scrolling, the new line does not clear the previous line.  If the
> previous line had data that went to the end of the line and the next
> line, say has data that goes half way, the data from the previous line
> after the halfway mark remains.

I cannot reproduce here, but maybe I'm using the wrong setup. could you 
please provide your lcd4linux.conf, I will test with my MatrixOrbital 
(20x4).

bye, Michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

[lcd4linux] Text Overlay Problem

[James Van't S. <ja...@si...>]

Hi all,

First off great job on the new release!  I've been dying for scrolling
output for ages! 

I'm having a problem though... I'm sure it's with the way I've got
things configured...

I'm using a CrystalFontz 634 by the way..

When scrolling, the new line does not clear the previous line.  If the
previous line had data that went to the end of the line and the next
line, say has data that goes half way, the data from the previous line
after the halfway mark remains.

Example:

If I have a line that reads:

Up: 21 days 19:54

Which then scrolls up one line and the new line at the bottom reads:

Disk   |    19:54


So my question is:  Is there a way that I can force a line to be cleared
initially before the new line is written?

Thanks for your help.

james 

[lcd4linux] Text Overlay Problem

[James Van't S. <ja...@va...>]

Hi all,

First off great job on the new release!  I've been dying for scrolling
output for ages! 

I'm having a problem though... I'm sure it's with the way I've got
things configured...

I'm using a CrystalFontz 634 by the way..

When scrolling, the new line does not clear the previous line.  If the
previous line had data that went to the end of the line and the next
line, say has data that goes half way, the data from the previous line
after the halfway mark remains.

Example:

If I have a line that reads:

Up: 21 days 19:54

Which then scrolls up one line and the new line at the bottom reads:

Disk   |    19:54


So my question is:  Is there a way that I can force a line to be cleared
initially before the new line is written?

Thanks for your help.

james 

[lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

Hi!

before i start, sorry for the very large message.

I'm trying to compile lcd4linux-0.9.9 with uClibc 0.9.20, and i get this
exact error.

I ran './configure  ./configure --host=i386-uclibc --with-drivers=HD44780
--without-x --without-ncurses'
and make.

compileShell:/bering/lcd4linux-0.9.9$ make
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c lcd4linux.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c debug.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c cfg.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c lock.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c parser.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c processor.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c system.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c isdn.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c mail.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c seti.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c battery.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c dvb.c
dvb.c:49:2: warning: #warning linux/dvb/frontend.h not found.
dvb.c:50:2: warning: #warning DVB client will be disabled.
dvb.c: In function `DVB':
dvb.c:57: warning: implicit declaration of function `error'
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c filter.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c udelay.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c display.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c pixmap.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c bar.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c fontmap.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c exec.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c mail2.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c socket.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c HD44780.c
/bering/buildtool/staging/bin/i386-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE -Wall -g -O2 -c parport.c
/bering/buildtool/staging/bin/i386-uclibc-gcc  -D_GNU_SOURCE -Wall -g -O2
-o lcd4linux  lcd4linux.o debug.o cfg.o lock.o parser.o processor.o system.o
isdn.o mail.o seti.o battery.o dvb.o filter.o udelay.o display.o pixmap.o
bar.o fontmap.o exec.o mail2.o socket.o HD44780.o parport.o  -lm
lcd4linux.o: In function `main':
/bering/lcd4linux-0.9.9/lcd4linux.c:308: undefined reference to `rpl_malloc'
collect2: ld returned 1 exit status

Luis Correia   
PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 
Key Server: http://pgp.mit.edu

[lcd4linux] lcd4linux 0.9.9 released!

[Michael R. <re...@eu...>]

Well, finally....

It's my birthday. Not really today, but two days ago. That's when I 
decided to release 0.9.9.


It's been almost two years since 0.98. Lots of things happened. Lots of 
other things didn't happen.

I got ESR's "The Cathedral and the Bazaar". I read "Release often, 
release early". I will to so.

what has happened to lcd4linux in these two years:

* new version number scheme:
   0.9.9 instead of 0.99
   the next release will be 0.9.10

* moved documentation to web page
   there are no more README's. All the documentation is
   on the web page. Have a look at it! Comments are welcome!

* virtual rows, scrolling
   you can control more rows than your display has. And scroll them...

* DVB client
   If you've got a digital satellite card, you'll like this one:
   display "Signal Strenght" and "Signal/Noise Ratio" on your
   Home Theater PC. Looks cool. Really.

* parallel port abstraction
   you can use any wiring you like (lcdproc, WinAmp, ..) Just
   tell lcd4linux which wires are connected.

* gcc3 issues
   and automake issues. and include issues. and other issues.

* sensors factor and offset
   needed e.g. for my EPIA board (the HTPC!)

* new drivers:
   * Mitsubishi M50530
   * USBLCD
   * Toshiba T6963
   * MatrixOrbital LK202
   * Cwlinux CW12232 CW1602



I hope you like it!

bye, Michael

-- 
netWorks                                          Vox: +43 316  698260
Michael Reinelt                                   Fax: +43 316  692343
Geisslergasse 4                                   GSM: +43 676 3079941
A-8045 Graz, Austria                          e-mail: re...@eu...

[lcd4linux] (no subject)

[Pohl, F. <F....@di...>]

Mit freundlichen Gr=FCssen
Frank Pohl

DIGIHAUS Dr. J=FCrgen Rakow GmbH=20
e-mail: f....@di...
home: http://www.digihaus.de <http://www.digihaus.de/>=20
Forckenbeckstr. 9-13, 14199 Berlin=20
Tel.: +49 30 824 0000
Fax: +49 30 853 96 97

[lcd4linux] A 17% dividend?

[<der...@ya...>]

PEhUTUw+PEJPRFk+PEZPTlQgY29sb3I9I2ZmZmZmZj4gIGFtYmx5b3BpYSAs
IHNpZ2h0IHByb2JsZW1zICA8L0ZPTlQ+DQo8RElWPjxGT05UIGZhY2U9QXJp
YWw+MTclIGRpdmlkZW5kPyBJcyBpdCBwb3NzaWJsZT88L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIGZhY2U9QXJpYWw+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbD5EaWQg
eW91IGtub3cgdGhhdCB0aGVyZSBpcyBhIGdyb3VwIG9mIHN0b2NrcyB0aGF0
IGhhdmUgDQpjb25zaXN0YW50bHkgcGFpZCBmcm9tIDE1IHRvIDIwJSBpbiBh
bm51YWwgZGl2aWRlbmRzPzwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9E
SVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWw+V2VsbCwgdGhlIHdvcmQgaXMg
c3ByZWFkaW5nLi4uLjwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+
DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwODAwMD5QVlg8QlI+
TkNOPEJSPkVSRjxCUj5UUlU8QlI+UEdIPC9GT05UPjwvRElWPg0KPERJVj4m
bmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbD5BcmUgeW91IHRp
cmVkIG9mIHJpZGljdWxvdXNseSBsb3cgcmV0dXJuIG9uIGludmVzdG1lbnRz
PyANClRoZW4gY2hlY2sgb3V0IHRoZSBxdWFsaXR5IHN0b2NrcyBhYm92ZS48
L0ZPTlQ+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBm
YWNlPUFyaWFsPlNvbWUgcGF5IGFzIG11Y2ggYXMgMjAlIGFubnVhbCBkaXZp
ZGVuZCwgcGFpZCBpbiBNT05USExZIA0KZGlzdHJpYnV0aW9ucywgYW5kIGhh
dmUgY29uc2lzdGFudGx5IGZvciANCnllYXJzLjwvRk9OVD48L0RJVj48QlI+
PEJSPjxCUj48QlI+PEJSPjxCUj48QlI+PEJSPg0KPERJVj48Rk9OVCBmYWNl
PUFyaWFsIGNvbG9yPSMwMDgwMDA+V291bGRuJ3QgaXQgYmUgZ3JlYXQgdG8g
b3duIHN0b2NrcyB0aGF0IA0KcGFpZCZuYnNwO3lvdSBhIG1vbnRobHkgaW5j
b21lPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgDQpmYWNlPUFyaWFsPjxC
Uj48L0ZPTlQ+PC9ESVY+PEJSPjxCUj48QlI+PEJSPjxCUj48QlI+PEJSPjxC
Uj48QlI+PEJSPjxCUj48QlI+PEJSPjxCUj48QlI+PEJSPjxCUj48QlI+PEJS
PjxCUj48QlI+PEJSPjxCUj48QlI+PEJSPjxCUj48QlI+DQpUaGlzIGlzIG5v
dCBhIHNvbGljaXRhdGlvbiB0byBidXkgb3Igc2VsbCBhbnkgc3RvY2suIEFs
d2F5cyBjb25zdWx0IGFuIGludmVzdG1lbnQgDQpwcm9mZXNzaW9uYWwgYmVm
b3JlIGludmVzdGluZy4gVGhpcyBlbWFpbCZuYnNwOyBpcyBmb3IgaW5mb3Jt
YXRpb25hbCBwdXJwb3NlcyANCm9ubHkuIFRoaXMgaXMgYSBvbmUgdGltZSBt
YWlsaW5nLiBZb3Ugd2lsbCBub3QgcmVjaWV2ZSB0aGlzIA0KZW1haWwgYWdh
aW4uPC9CT0RZPjwvSFRNTD4NCjMzOThFUWFmNi05ODZRTVNFNTEzNGhPTmk0
LTMwNU5NVEpsMzI=

[lcd4linux] LCD4LINUX.SOURCEFORGE.NET

[Sarah W. <re...@tm...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"><!-- =
Ap -->
<STYLE type=3Dtext/css>TD {
	FONT-SIZE: 11px; COLOR: #000000; FONT-FAMILY: verdana, arial, helvetica
}
</STYLE>

<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<TABLE cellSpacing=3D0 cellPadding=3D0 width=3D600 border=3D0>
  <TBODY>
  <TR>
    <TD>Hi<BR><BR>I visited <A 
      href=3D=
"http://www.trafficmagnet.com/signup/index.html">LCD4LINUX.SOURCEFORGE.NET</A=
>, and noticed that you're not listed on some search engines! I 
      think we can offer you a service which can help you increase traffic =
and 
      the number of visitors to your website.<BR><BR>I would like to =
introduce 
      you to <A 
      href=3D=
"http://www.trafficmagnet.com/signup/index.html">Trafficmagnet.com</A>. 
      We offer a unique technology that will submit your website to over =
300,000 
      search engines and directories every month.<BR><BR>
      <TABLE cellSpacing=3D0 cellPadding=3D0 width=3D398 align=3Dcenter =
border=3D0>
        <TBODY>
        <TR>
          <TD><A href=3D"http://www.trafficmagnet.com/signup/index.html"><IMG =

            height=3D136 src=3D"http://www.trafficmagnet.com/img/img_tm.gif" =
width=3D137 border=3D0></A>&nbsp;</TD>
          <TD><A href=3D"http://www.trafficmagnet.com/signup/index.html"><IMG =

            height=3D141 src=3D=
"http://image10.trafficmagnet.net/img4/ZEUS199/001/133/eem.jpg" width=3D197 =
border=3D1></A></TD>
          <TD vAlign=3Dbottom><A 
            href=3D"http://www.trafficmagnet.com/signup/index.html"><IMG 
            height=3D136 src=3D=
"http://www.trafficmagnet.com/img/img_signup.gif" width=3D62 
      border=3D0></A></TD></TR></TBODY></TABLE><BR>You'll be surprised by the =
low 
      cost, and by how effective this website promotion method can be. 
      <BR><BR>To find out more about TrafficMagnet and the cost for =
submitting 
      your website to over 300,000 search engines and directories, visit <A 
      href=3D=
"http://www.trafficmagnet.com/signup/index.html">www.trafficmagnet.com</A>. 
      <BR><BR>I would love to hear from you. <BR><BR><BR>Best 
      Regards,<BR><BR>Sarah Williams <BR>Sales and Marketing <BR>E-mail: 
      sar...@tm... <BR><A 
      href=3D=
"http://www.trafficmagnet.com/signup/index.html">http://www.trafficmagnet.com=
</A> 

      <P>This email was sent to lcd...@li.... We apologize if this email =

      has reached you in error.<BR>We honor all removal requests. Please <A 
      href=3D"http://optout.trafficmagnet.com/optout/Action/OptOut?email=3D=
lcd...@li...&url=3D lcd4linux.sourceforge.net">click 
      here</A> to be removed from our mailing 
list.</P></TD></TR></TBODY></TABLE></BODY></HTML>