lcd4linux-users — lcd4linux users

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Mattia Jona-L. <mat...@gm...>]

just forgot to mention the operation sequence

1) check out the svn trunk
2) apply the patch
3) recreate the configure script by running the bootstrap script
4) run the configure script

On Tue, Dec 27, 2011 at 3:40 PM, Mattia Jona-Lasinio
<mat...@gm...> wrote:
> Hi Michael and Alexander,
>
> during these holidays I had some spare time to spend on lcd4linux and
> the mac os x support. I realized that some basic support was
> already implemented in plugin_proc_stat and plugin_netinfo but I could
> not make the netinfo part work on my system. I implemented the
> plugin_meminfo and added the relevant ifdefs to detect the mac os x
> environment. The diskstats and netdev plugin are still to be
> implemented.
>
> The support is still at a very early stage and I only tested the X11
> driver, that works with no problems.
>
> These are my notes to compile successfully.
>
> 1) You need to install on mac os x the full GNU autoconf, automake,
> etc etc... tools
> 2) You need to install the GNU libtool. The libtool version provided
> with mac os x has a different syntax and does not work. Keep in mind
> that the macport libtool will be installed as glibtool to avoid name
> clashes so you need to force your system to use the GNU libtool
> instead of the mac os x one. A symbolic link will do the job.
> 3) The libiconv from the macport project misses the iconv_open,
> iconv_close, iconv_..... functions. I don't know whether it is a bug
> or not but the mac os x iconv library has those functions so I just
> linked by hand against this library and everything went fine. Can
> someone report on this?
>
> Happy holidays!
>
> Mattia
>
>
>
> On Thu, Dec 22, 2011 at 3:28 AM, Michael Reinelt <mi...@re...> wrote:
>> Hi Mattia,
>>
>> looks fine, so go ahead!
>>
>>
>> thanks a lot, Michael
>>
>>
>> Am 2011-12-21 14:03, schrieb Mattia Jona-Lasinio:
>>
>>> Hi Michael,
>>>
>>> this is my patch to solve all the header related issues. If you agree
>>> I will commit these changes right away.
>>>
>>> Best,
>>>
>>> Mattia
>>>
>>>
>>> On Wed, Dec 21, 2011 at 12:20 PM, Mattia Jona-Lasinio
>>> <mat...@gm...>  wrote:
>>>>
>>>> Hello Michael,
>>>>
>>>> On Wed, Dec 21, 2011 at 9:12 AM, Michael Reinelt<mi...@re...>
>>>>  wrote:
>>>>>
>>>>> Hello Mattia,
>>>>>
>>>>>
>>>>>> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
>>>>>> with powerPC processor and OS X 10.5.8 (the latest supported OS X
>>>>>> release for this processor architecture).
>>>>>
>>>>>
>>>>>
>>>>> Cool!
>>>>>
>>>>>
>>>>>> I compiled the X11 driver only but I included all the plugins
>>>>>> excluding the following:
>>>>>>
>>>>>> huawei: the flag IUCLC is used in one of the functions and it is
>>>>>> absent in the OS X termios flags
>>>>>
>>>>>
>>>>>
>>>>> I have no idea about this plugin (I don't use it)
>>>>
>>>>
>>>> Yep, me neither. I have no idea about the huawei stuff.
>>>>
>>>>
>>>>>> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
>>>>>> header everything is fine
>>>>>
>>>>>
>>>>> could this be fine on linux, too? in this case we could fix it globally.
>>>>> Could you provide a patch?
>>>>
>>>>
>>>> sure! On Linux we have PATH_MAX defined in linux/limits.h but we don't
>>>> include it directly as it is automatically included by other headers.
>>>>
>>>>>
>>>>>
>>>>>> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not
>>>>>> apply
>>>>>
>>>>>
>>>>> Is there a (simnple) way to exclude this plugin on mac somehow in the
>>>>> autoconf toolchain?
>>>>
>>>>
>>>> yes, I'm not very familiar with all the autoconf stuff but it should
>>>> be feasible.
>>>> A more important question is how do we gather system information on OS X
>>>> if we don't have a proc filesystem to parse?
>>>>
>>>>
>>>>>> The libtool works a bit differently so you will have to link by hand.
>>>>>> Also depending on your installation the libiconv may differ. You may
>>>>>> want to specify the library full path when linking.
>>>>>
>>>>>
>>>>>
>>>>> Well, that does not sound too good to me... I always thought that's why
>>>>> we
>>>>> use all this autoconf stuff?
>>>>
>>>>
>>>> I just linked to check if the binary ran or not. It is surely possible
>>>> to make it work with the libtool chain.
>>>>
>>>>>> I also spotted an error in timer.h This header must include the system
>>>>>> header time.h or the struct timespec is undefined.
>>>>>> Presently time.h is included in timer.c.
>>>>>
>>>>>
>>>>>
>>>>> Again, if this change is fine for linux, too, I want to apply it
>>>>> globally.
>>>>
>>>>
>>>> This has nothing to do with OS X. It's a real programming error.
>>>> Headers must be self contained and should compile also on their own.
>>>> Presently timer.h compiles with a BIG warning concerning the undefined
>>>> struct timespec. With the inclusion of time.h everything is fine.
>>>>
>>>>>
>>>>>
>>>>> merry christmas to everyone!
>>>>>
>>>>
>>>> merry christmas to you all!
>>>>
>>>>>
>>>>>
>>>>> regards, michael
>>>>>
>>>>>
>>>>> --
>>>>> Michael Reinelt<mi...@re...>
>>>>> http://home.pages.at/reinelt
>>>>> GPG-Key 0xDF13BA50
>>>>> ICQ #288386781
>>
>>
>> --
>> Michael Reinelt <mi...@re...>
>> http://home.pages.at/reinelt
>> GPG-Key 0xDF13BA50
>> ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Mattia Jona-L. <mat...@gm...>]

Hi Michael and Alexander,

during these holidays I had some spare time to spend on lcd4linux and
the mac os x support. I realized that some basic support was
already implemented in plugin_proc_stat and plugin_netinfo but I could
not make the netinfo part work on my system. I implemented the
plugin_meminfo and added the relevant ifdefs to detect the mac os x
environment. The diskstats and netdev plugin are still to be
implemented.

The support is still at a very early stage and I only tested the X11
driver, that works with no problems.

These are my notes to compile successfully.

1) You need to install on mac os x the full GNU autoconf, automake,
etc etc... tools
2) You need to install the GNU libtool. The libtool version provided
with mac os x has a different syntax and does not work. Keep in mind
that the macport libtool will be installed as glibtool to avoid name
clashes so you need to force your system to use the GNU libtool
instead of the mac os x one. A symbolic link will do the job.
3) The libiconv from the macport project misses the iconv_open,
iconv_close, iconv_..... functions. I don't know whether it is a bug
or not but the mac os x iconv library has those functions so I just
linked by hand against this library and everything went fine. Can
someone report on this?

Happy holidays!

Mattia



On Thu, Dec 22, 2011 at 3:28 AM, Michael Reinelt <mi...@re...> wrote:
> Hi Mattia,
>
> looks fine, so go ahead!
>
>
> thanks a lot, Michael
>
>
> Am 2011-12-21 14:03, schrieb Mattia Jona-Lasinio:
>
>> Hi Michael,
>>
>> this is my patch to solve all the header related issues. If you agree
>> I will commit these changes right away.
>>
>> Best,
>>
>> Mattia
>>
>>
>> On Wed, Dec 21, 2011 at 12:20 PM, Mattia Jona-Lasinio
>> <mat...@gm...>  wrote:
>>>
>>> Hello Michael,
>>>
>>> On Wed, Dec 21, 2011 at 9:12 AM, Michael Reinelt<mi...@re...>
>>>  wrote:
>>>>
>>>> Hello Mattia,
>>>>
>>>>
>>>>> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
>>>>> with powerPC processor and OS X 10.5.8 (the latest supported OS X
>>>>> release for this processor architecture).
>>>>
>>>>
>>>>
>>>> Cool!
>>>>
>>>>
>>>>> I compiled the X11 driver only but I included all the plugins
>>>>> excluding the following:
>>>>>
>>>>> huawei: the flag IUCLC is used in one of the functions and it is
>>>>> absent in the OS X termios flags
>>>>
>>>>
>>>>
>>>> I have no idea about this plugin (I don't use it)
>>>
>>>
>>> Yep, me neither. I have no idea about the huawei stuff.
>>>
>>>
>>>>> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
>>>>> header everything is fine
>>>>
>>>>
>>>> could this be fine on linux, too? in this case we could fix it globally.
>>>> Could you provide a patch?
>>>
>>>
>>> sure! On Linux we have PATH_MAX defined in linux/limits.h but we don't
>>> include it directly as it is automatically included by other headers.
>>>
>>>>
>>>>
>>>>> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not
>>>>> apply
>>>>
>>>>
>>>> Is there a (simnple) way to exclude this plugin on mac somehow in the
>>>> autoconf toolchain?
>>>
>>>
>>> yes, I'm not very familiar with all the autoconf stuff but it should
>>> be feasible.
>>> A more important question is how do we gather system information on OS X
>>> if we don't have a proc filesystem to parse?
>>>
>>>
>>>>> The libtool works a bit differently so you will have to link by hand.
>>>>> Also depending on your installation the libiconv may differ. You may
>>>>> want to specify the library full path when linking.
>>>>
>>>>
>>>>
>>>> Well, that does not sound too good to me... I always thought that's why
>>>> we
>>>> use all this autoconf stuff?
>>>
>>>
>>> I just linked to check if the binary ran or not. It is surely possible
>>> to make it work with the libtool chain.
>>>
>>>>> I also spotted an error in timer.h This header must include the system
>>>>> header time.h or the struct timespec is undefined.
>>>>> Presently time.h is included in timer.c.
>>>>
>>>>
>>>>
>>>> Again, if this change is fine for linux, too, I want to apply it
>>>> globally.
>>>
>>>
>>> This has nothing to do with OS X. It's a real programming error.
>>> Headers must be self contained and should compile also on their own.
>>> Presently timer.h compiles with a BIG warning concerning the undefined
>>> struct timespec. With the inclusion of time.h everything is fine.
>>>
>>>>
>>>>
>>>> merry christmas to everyone!
>>>>
>>>
>>> merry christmas to you all!
>>>
>>>>
>>>>
>>>> regards, michael
>>>>
>>>>
>>>> --
>>>> Michael Reinelt<mi...@re...>
>>>> http://home.pages.at/reinelt
>>>> GPG-Key 0xDF13BA50
>>>> ICQ #288386781
>
>
> --
> Michael Reinelt <mi...@re...>
> http://home.pages.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781

[lcd4linux] old ancient legacy port access disabled

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

Hello all,

today I decided to disable the old direct raw parallel port access in LCD4Linux (using outb() and so on)

If you really need it, you can enable it with configure --with-outb

I don't want to remove the code completely (in about 15 years, I want to show my kids that "bit banging" wasn't obscene :-)

I cannot test it completely, because I don't have any parallel ports available here, and I don't have any non-x86 
machines to test.

But I hope that now debian builds on non-x86 architectures don't fail (I got some error reports for sparc, mipsel, 
powerpc, s390)


Maybe someone can do some testing?


regards, Michael

-- 
Michael Reinelt <mi...@re...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

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

Hi Mattia,

looks fine, so go ahead!


thanks a lot, Michael


Am 2011-12-21 14:03, schrieb Mattia Jona-Lasinio:
> Hi Michael,
>
> this is my patch to solve all the header related issues. If you agree
> I will commit these changes right away.
>
> Best,
>
> Mattia
>
>
> On Wed, Dec 21, 2011 at 12:20 PM, Mattia Jona-Lasinio
> <mat...@gm...>  wrote:
>> Hello Michael,
>>
>> On Wed, Dec 21, 2011 at 9:12 AM, Michael Reinelt<mi...@re...>  wrote:
>>> Hello Mattia,
>>>
>>>
>>>> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
>>>> with powerPC processor and OS X 10.5.8 (the latest supported OS X
>>>> release for this processor architecture).
>>>
>>>
>>> Cool!
>>>
>>>
>>>> I compiled the X11 driver only but I included all the plugins
>>>> excluding the following:
>>>>
>>>> huawei: the flag IUCLC is used in one of the functions and it is
>>>> absent in the OS X termios flags
>>>
>>>
>>> I have no idea about this plugin (I don't use it)
>>
>> Yep, me neither. I have no idea about the huawei stuff.
>>
>>
>>>> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
>>>> header everything is fine
>>>
>>> could this be fine on linux, too? in this case we could fix it globally.
>>> Could you provide a patch?
>>
>> sure! On Linux we have PATH_MAX defined in linux/limits.h but we don't
>> include it directly as it is automatically included by other headers.
>>
>>>
>>>
>>>> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not
>>>> apply
>>>
>>> Is there a (simnple) way to exclude this plugin on mac somehow in the
>>> autoconf toolchain?
>>
>> yes, I'm not very familiar with all the autoconf stuff but it should
>> be feasible.
>> A more important question is how do we gather system information on OS X
>> if we don't have a proc filesystem to parse?
>>
>>
>>>> The libtool works a bit differently so you will have to link by hand.
>>>> Also depending on your installation the libiconv may differ. You may
>>>> want to specify the library full path when linking.
>>>
>>>
>>> Well, that does not sound too good to me... I always thought that's why we
>>> use all this autoconf stuff?
>>
>> I just linked to check if the binary ran or not. It is surely possible
>> to make it work with the libtool chain.
>>
>>>> I also spotted an error in timer.h This header must include the system
>>>> header time.h or the struct timespec is undefined.
>>>> Presently time.h is included in timer.c.
>>>
>>>
>>> Again, if this change is fine for linux, too, I want to apply it globally.
>>
>> This has nothing to do with OS X. It's a real programming error.
>> Headers must be self contained and should compile also on their own.
>> Presently timer.h compiles with a BIG warning concerning the undefined
>> struct timespec. With the inclusion of time.h everything is fine.
>>
>>>
>>>
>>> merry christmas to everyone!
>>>
>>
>> merry christmas to you all!
>>
>>>
>>>
>>> regards, michael
>>>
>>>
>>> --
>>> Michael Reinelt<mi...@re...>
>>> http://home.pages.at/reinelt
>>> GPG-Key 0xDF13BA50
>>> ICQ #288386781

-- 
Michael Reinelt <mi...@re...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Mattia Jona-L. <mat...@gm...>]

Hi Michael,

this is my patch to solve all the header related issues. If you agree
I will commit these changes right away.

Best,

Mattia


On Wed, Dec 21, 2011 at 12:20 PM, Mattia Jona-Lasinio
<mat...@gm...> wrote:
> Hello Michael,
>
> On Wed, Dec 21, 2011 at 9:12 AM, Michael Reinelt <mi...@re...> wrote:
>> Hello Mattia,
>>
>>
>>> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
>>> with powerPC processor and OS X 10.5.8 (the latest supported OS X
>>> release for this processor architecture).
>>
>>
>> Cool!
>>
>>
>>> I compiled the X11 driver only but I included all the plugins
>>> excluding the following:
>>>
>>> huawei: the flag IUCLC is used in one of the functions and it is
>>> absent in the OS X termios flags
>>
>>
>> I have no idea about this plugin (I don't use it)
>
> Yep, me neither. I have no idea about the huawei stuff.
>
>
>>> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
>>> header everything is fine
>>
>> could this be fine on linux, too? in this case we could fix it globally.
>> Could you provide a patch?
>
> sure! On Linux we have PATH_MAX defined in linux/limits.h but we don't
> include it directly as it is automatically included by other headers.
>
>>
>>
>>> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not
>>> apply
>>
>> Is there a (simnple) way to exclude this plugin on mac somehow in the
>> autoconf toolchain?
>
> yes, I'm not very familiar with all the autoconf stuff but it should
> be feasible.
> A more important question is how do we gather system information on OS X
> if we don't have a proc filesystem to parse?
>
>
>>> The libtool works a bit differently so you will have to link by hand.
>>> Also depending on your installation the libiconv may differ. You may
>>> want to specify the library full path when linking.
>>
>>
>> Well, that does not sound too good to me... I always thought that's why we
>> use all this autoconf stuff?
>
> I just linked to check if the binary ran or not. It is surely possible
> to make it work with the libtool chain.
>
>>> I also spotted an error in timer.h This header must include the system
>>> header time.h or the struct timespec is undefined.
>>> Presently time.h is included in timer.c.
>>
>>
>> Again, if this change is fine for linux, too, I want to apply it globally.
>
> This has nothing to do with OS X. It's a real programming error.
> Headers must be self contained and should compile also on their own.
> Presently timer.h compiles with a BIG warning concerning the undefined
> struct timespec. With the inclusion of time.h everything is fine.
>
>>
>>
>> merry christmas to everyone!
>>
>
> merry christmas to you all!
>
>>
>>
>> regards, michael
>>
>>
>> --
>> Michael Reinelt <mi...@re...>
>> http://home.pages.at/reinelt
>> GPG-Key 0xDF13BA50
>> ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Mattia Jona-L. <mat...@gm...>]

Hello Michael,

On Wed, Dec 21, 2011 at 9:12 AM, Michael Reinelt <mi...@re...> wrote:
> Hello Mattia,
>
>
>> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
>> with powerPC processor and OS X 10.5.8 (the latest supported OS X
>> release for this processor architecture).
>
>
> Cool!
>
>
>> I compiled the X11 driver only but I included all the plugins
>> excluding the following:
>>
>> huawei: the flag IUCLC is used in one of the functions and it is
>> absent in the OS X termios flags
>
>
> I have no idea about this plugin (I don't use it)

Yep, me neither. I have no idea about the huawei stuff.


>> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
>> header everything is fine
>
> could this be fine on linux, too? in this case we could fix it globally.
> Could you provide a patch?

sure! On Linux we have PATH_MAX defined in linux/limits.h but we don't
include it directly as it is automatically included by other headers.

>
>
>> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not
>> apply
>
> Is there a (simnple) way to exclude this plugin on mac somehow in the
> autoconf toolchain?

yes, I'm not very familiar with all the autoconf stuff but it should
be feasible.
A more important question is how do we gather system information on OS X
if we don't have a proc filesystem to parse?


>> The libtool works a bit differently so you will have to link by hand.
>> Also depending on your installation the libiconv may differ. You may
>> want to specify the library full path when linking.
>
>
> Well, that does not sound too good to me... I always thought that's why we
> use all this autoconf stuff?

I just linked to check if the binary ran or not. It is surely possible
to make it work with the libtool chain.

>> I also spotted an error in timer.h This header must include the system
>> header time.h or the struct timespec is undefined.
>> Presently time.h is included in timer.c.
>
>
> Again, if this change is fine for linux, too, I want to apply it globally.

This has nothing to do with OS X. It's a real programming error.
Headers must be self contained and should compile also on their own.
Presently timer.h compiles with a BIG warning concerning the undefined
struct timespec. With the inclusion of time.h everything is fine.

>
>
> merry christmas to everyone!
>

merry christmas to you all!

>
>
> regards, michael
>
>
> --
> Michael Reinelt <mi...@re...>
> http://home.pages.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Alexander v. d. B. <atv...@ho...>]

All, Long shot perhaps, but wouldn't it be great to have lcd4linux available through MacPorts one day?
Cheers, Alexander> Date: Wed, 21 Dec 2011 09:12:54 +0100
> From: mi...@re...
> To: mat...@gm...
> CC: atv...@ho...; lcd...@li...
> Subject: Re: [lcd4linux] Compiling on Mac OS X Snow Leopard
> 
> Hello Mattia,
> 
> > I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
> > with powerPC processor and OS X 10.5.8 (the latest supported OS X
> > release for this processor architecture).
> 
> Cool!
> 
> > I compiled the X11 driver only but I included all the plugins
> > excluding the following:
> >
> > huawei: the flag IUCLC is used in one of the functions and it is
> > absent in the OS X termios flags
> 
> I have no idea about this plugin (I don't use it)
> 
> > i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
> > header everything is fine
> could this be fine on linux, too? in this case we could fix it globally. Could you provide a patch?
> 
> > proc_stat: OS_X doesn't have a proc filesystem so this plugin does not apply
> Is there a (simnple) way to exclude this plugin on mac somehow in the autoconf toolchain?
> 
> 
> > The libtool works a bit differently so you will have to link by hand.
> > Also depending on your installation the libiconv may differ. You may
> > want to specify the library full path when linking.
> 
> Well, that does not sound too good to me... I always thought that's why we use all this autoconf stuff?
> 
> 
> > I also spotted an error in timer.h This header must include the system
> > header time.h or the struct timespec is undefined.
> > Presently time.h is included in timer.c.
> 
> Again, if this change is fine for linux, too, I want to apply it globally.
> 
> 
> merry christmas to everyone!
> 
> 
> regards, michael
> 
> 
> -- 
> Michael Reinelt <mi...@re...>
> http://home.pages.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781
 		 	   		  

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

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

Hello Mattia,

> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
> with powerPC processor and OS X 10.5.8 (the latest supported OS X
> release for this processor architecture).

Cool!

> I compiled the X11 driver only but I included all the plugins
> excluding the following:
>
> huawei: the flag IUCLC is used in one of the functions and it is
> absent in the OS X termios flags

I have no idea about this plugin (I don't use it)

> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
> header everything is fine
could this be fine on linux, too? in this case we could fix it globally. Could you provide a patch?

> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not apply
Is there a (simnple) way to exclude this plugin on mac somehow in the autoconf toolchain?


> The libtool works a bit differently so you will have to link by hand.
> Also depending on your installation the libiconv may differ. You may
> want to specify the library full path when linking.

Well, that does not sound too good to me... I always thought that's why we use all this autoconf stuff?


> I also spotted an error in timer.h This header must include the system
> header time.h or the struct timespec is undefined.
> Presently time.h is included in timer.c.

Again, if this change is fine for linux, too, I want to apply it globally.


merry christmas to everyone!


regards, michael


-- 
Michael Reinelt <mi...@re...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Alexander v. d. B. <atv...@ho...>]

Wow Mattia,
This was exactly the info I was hoping for, thank you so much! Gonna give it a go next week and will report back. Thanks and merry Christmas to you all, Alexander> Date: Mon, 19 Dec 2011 16:32:13 +0100
> Subject: Re: [lcd4linux] Compiling on Mac OS X Snow Leopard
> From: mat...@gm...
> To: atv...@ho...
> CC: mi...@re...; lcd...@li...
> 
> Hi Alexander and Michael,
> 
> I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
> with powerPC processor and OS X 10.5.8 (the latest supported OS X
> release for this processor architecture).
> 
> I compiled the X11 driver only but I included all the plugins
> excluding the following:
> 
> huawei: the flag IUCLC is used in one of the functions and it is
> absent in the OS X termios flags
> i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
> header everything is fine
> proc_stat: OS_X doesn't have a proc filesystem so this plugin does not apply
> 
> Excluding this, everything works fine.
> 
> The libtool works a bit differently so you will have to link by hand.
> Also depending on your installation the libiconv may differ. You may
> want to specify the library full path when linking.
> 
> I also spotted an error in timer.h This header must include the system
> header time.h or the struct timespec is undefined.
> Presently time.h is included in timer.c.
> 
> Regards,
> 
> Mattia
> 
> 
> 
> 
> 
> 
> On Mon, Dec 19, 2011 at 8:22 AM, Alexander van den Bosch
> <atv...@ho...> wrote:
> > Excellent, thanks for the quick reaction.
> >
> > Long term plans look like I'll have some hardware running Linux one day, but
> > at the moment all I have is a Mac. Macports has allowed me to compile and
> > run lots of useful Linux applications like GIMP etc. so I thought why
> > not see if I could get lcd4linux up and running too? I was also encouraged
> > by the fact that this guy seemed to have done it too last year.
> > http://www.civade.com/post/2010/11/10/Installer-afficheur-LCD-44780-lcd4linux-NAS-ReadyNAS-Netgear
> >
> > Being a (.NET) programmer by trade I'm not afraid of the usual digging work
> > that comes with an exercise like this, but manual Linux compiling is fairly
> > new to me, so hence this check for possible blind spots on my side.
> >
> > Anyway, thanks for the suggested compilation options and the smoketest
> > script, which I hadn't noticed yet. I'm certainly going to give them a spin!
> >
> > Best regards,
> >
> > Alexander
> >> Date: Mon, 19 Dec 2011 03:24:40 +0100
> >> From: mi...@re...
> >> To: atv...@ho...
> >> CC: lcd...@li...
> >> Subject: Re: [lcd4linux] Compiling on Mac OS X Snow Leopard
> >
> >>
> >> Hello Alexander,
> >>
> >> > I'm currently trying to compile lcd4linux on Mac OS X 10.6.8 (Snow
> >> > Leopard). I'd like to try it with the X11 driver to
> >> > see what it can do for me, and maybe to try and write my own lcd4linux
> >> > plugin. Unfortunately I can't get the svn trunk
> >> > to build successfully on my machine at the moment.
> >> >
> >> > Before going into details I'd like to know if what I want to achieve is
> >> > possible at all? And if so, are there specific
> >> > caveats I might be unaware of?
> >>
> >> I don't know. First, guess why lcd4linux has "linux" in its name :-)
> >>
> >> I know that some BSD guys failed long time ago.
> >>
> >> Maybe some x86 specific low-level port access stuff in drv_parport will
> >> fail (which should be removed anyway)
> >>
> >> you may find the scsript "smoketest.sh" useful, because it will try to
> >> compile lcd4linux with all possible combinations
> >> of sinlge driver / single plugins.
> >>
> >> As a first try, I would try to compile it --with-drivers=null
> >> --with_plugins=none to make sure there isn't a very basic
> >> problem somewhere.
> >>
> >>
> >>
> >> regards, Michael
> >>
> >>
> >>
> >> --
> >> Michael Reinelt <mi...@re...>
> >> http://home.pages.at/reinelt
> >> GPG-Key 0xDF13BA50
> >> ICQ #288386781
> >
> > ------------------------------------------------------------------------------
> > Learn Windows Azure Live!  Tuesday, Dec 13, 2011
> > Microsoft is holding a special Learn Windows Azure training event for
> > developers. It will provide a great way to learn Windows Azure and what it
> > provides. You can attend the event by watching it streamed LIVE online.
> > Learn more at http://p.sf.net/sfu/ms-windowsazure
> > _______________________________________________
> > Lcd4linux-users mailing list
> > Lcd...@li...
> > https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
> >

 		 	   		  

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Mattia Jona-L. <mat...@gm...>]

Hi Alexander and Michael,

I managed to turn lcd4linux into lcd4mac ;) on an old mac powerbook G4
with powerPC processor and OS X 10.5.8 (the latest supported OS X
release for this processor architecture).

I compiled the X11 driver only but I included all the plugins
excluding the following:

huawei: the flag IUCLC is used in one of the functions and it is
absent in the OS X termios flags
i2c_sensors: PATH_MAX is defined in sys/syslimits.h; by including this
header everything is fine
proc_stat: OS_X doesn't have a proc filesystem so this plugin does not apply

Excluding this, everything works fine.

The libtool works a bit differently so you will have to link by hand.
Also depending on your installation the libiconv may differ. You may
want to specify the library full path when linking.

I also spotted an error in timer.h This header must include the system
header time.h or the struct timespec is undefined.
Presently time.h is included in timer.c.

Regards,

Mattia






On Mon, Dec 19, 2011 at 8:22 AM, Alexander van den Bosch
<atv...@ho...> wrote:
> Excellent, thanks for the quick reaction.
>
> Long term plans look like I'll have some hardware running Linux one day, but
> at the moment all I have is a Mac. Macports has allowed me to compile and
> run lots of useful Linux applications like GIMP etc. so I thought why
> not see if I could get lcd4linux up and running too? I was also encouraged
> by the fact that this guy seemed to have done it too last year.
> http://www.civade.com/post/2010/11/10/Installer-afficheur-LCD-44780-lcd4linux-NAS-ReadyNAS-Netgear
>
> Being a (.NET) programmer by trade I'm not afraid of the usual digging work
> that comes with an exercise like this, but manual Linux compiling is fairly
> new to me, so hence this check for possible blind spots on my side.
>
> Anyway, thanks for the suggested compilation options and the smoketest
> script, which I hadn't noticed yet. I'm certainly going to give them a spin!
>
> Best regards,
>
> Alexander
>> Date: Mon, 19 Dec 2011 03:24:40 +0100
>> From: mi...@re...
>> To: atv...@ho...
>> CC: lcd...@li...
>> Subject: Re: [lcd4linux] Compiling on Mac OS X Snow Leopard
>
>>
>> Hello Alexander,
>>
>> > I'm currently trying to compile lcd4linux on Mac OS X 10.6.8 (Snow
>> > Leopard). I'd like to try it with the X11 driver to
>> > see what it can do for me, and maybe to try and write my own lcd4linux
>> > plugin. Unfortunately I can't get the svn trunk
>> > to build successfully on my machine at the moment.
>> >
>> > Before going into details I'd like to know if what I want to achieve is
>> > possible at all? And if so, are there specific
>> > caveats I might be unaware of?
>>
>> I don't know. First, guess why lcd4linux has "linux" in its name :-)
>>
>> I know that some BSD guys failed long time ago.
>>
>> Maybe some x86 specific low-level port access stuff in drv_parport will
>> fail (which should be removed anyway)
>>
>> you may find the scsript "smoketest.sh" useful, because it will try to
>> compile lcd4linux with all possible combinations
>> of sinlge driver / single plugins.
>>
>> As a first try, I would try to compile it --with-drivers=null
>> --with_plugins=none to make sure there isn't a very basic
>> problem somewhere.
>>
>>
>>
>> regards, Michael
>>
>>
>>
>> --
>> Michael Reinelt <mi...@re...>
>> http://home.pages.at/reinelt
>> GPG-Key 0xDF13BA50
>> ICQ #288386781
>
> ------------------------------------------------------------------------------
> Learn Windows Azure Live!  Tuesday, Dec 13, 2011
> Microsoft is holding a special Learn Windows Azure training event for
> developers. It will provide a great way to learn Windows Azure and what it
> provides. You can attend the event by watching it streamed LIVE online.
> Learn more at http://p.sf.net/sfu/ms-windowsazure
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

[Alexander v. d. B. <atv...@ho...>]

Excellent, thanks for the quick reaction. Long term plans look like I'll have some hardware running Linux one day, but at the moment all I have is a Mac. Macports has allowed me to compile and run lots of useful Linux applications like GIMP etc. so I thought why not see if I could get lcd4linux up and running too? I was also encouraged by the fact that this guy seemed to have done it too last year. http://www.civade.com/post/2010/11/10/Installer-afficheur-LCD-44780-lcd4linux-NAS-ReadyNAS-Netgear  Being a (.NET) programmer by trade I'm not afraid of the usual digging work that comes with an exercise like this, but manual Linux compiling is fairly new to me, so hence this check for possible blind spots on my side. Anyway, thanks for the suggested compilation options and the smoketest script, which I hadn't noticed yet. I'm certainly going to give them a spin! Best regards, Alexander> Date: Mon, 19 Dec 2011 03:24:40 +0100
> From: mi...@re...
> To: atv...@ho...
> CC: lcd...@li...
> Subject: Re: [lcd4linux] Compiling on Mac OS X Snow Leopard
> 
> Hello Alexander,
> 
> > I'm currently trying to compile lcd4linux on Mac OS X 10.6.8 (Snow Leopard). I'd like to try it with the X11 driver to
> > see what it can do for me, and maybe to try and write my own lcd4linux plugin. Unfortunately I can't get the svn trunk
> > to build successfully on my machine at the moment.
> >
> > Before going into details I'd like to know if what I want to achieve is possible at all? And if so, are there specific
> > caveats I might be unaware of?
> 
> I don't know. First, guess why lcd4linux has "linux" in its name :-)
> 
> I know that some BSD guys failed long time ago.
> 
> Maybe some x86 specific low-level port access stuff in drv_parport will fail (which should be removed anyway)
> 
> you may find the scsript "smoketest.sh" useful, because it will try to compile lcd4linux with all possible combinations 
> of sinlge driver / single plugins.
> 
> As a first try, I would try to compile it --with-drivers=null --with_plugins=none to make sure there isn't a very basic 
> problem somewhere.
> 
> 
> 
> regards, Michael
> 
> 
> 
> -- 
> Michael Reinelt <mi...@re...>
> http://home.pages.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781
 		 	   		  

Re: [lcd4linux] Degree sign on display

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

Hi Stefan,

> I try to get a temperature on my display like on "wiki/Features - data
> sources". How is the "°" shown?

By specifying a "°" character in postfix? :-)

> If this is a icon, how can i use a icen-widget in a text-widget?

No, it is a regular character. You may experience some problems if your display supports a non-standard charcater set 
(OTOH, what would be "standard" here?)

If you can find the char or at least its ascii code, you can always send it using the octal \xxx notation.



regards, Michael

-- 
Michael Reinelt <mi...@re...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Compiling on Mac OS X Snow Leopard

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

Hello Alexander,

> I'm currently trying to compile lcd4linux on Mac OS X 10.6.8 (Snow Leopard). I'd like to try it with the X11 driver to
> see what it can do for me, and maybe to try and write my own lcd4linux plugin. Unfortunately I can't get the svn trunk
> to build successfully on my machine at the moment.
>
> Before going into details I'd like to know if what I want to achieve is possible at all? And if so, are there specific
> caveats I might be unaware of?

I don't know. First, guess why lcd4linux has "linux" in its name :-)

I know that some BSD guys failed long time ago.

Maybe some x86 specific low-level port access stuff in drv_parport will fail (which should be removed anyway)

you may find the scsript "smoketest.sh" useful, because it will try to compile lcd4linux with all possible combinations 
of sinlge driver / single plugins.

As a first try, I would try to compile it --with-drivers=null --with_plugins=none to make sure there isn't a very basic 
problem somewhere.



regards, Michael



-- 
Michael Reinelt <mi...@re...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Degree sign on display

[Stefan K. <mai...@sk...>]

Hello,

I try to get a temperature on my display like on "wiki/Features - data
sources". How is the "°" shown?

If this is a icon, how can i use a icen-widget in a text-widget?

Regards,
Stefan Kuhne

[lcd4linux] Compiling on Mac OS X Snow Leopard

[Alexander v. d. B. <atv...@ho...>]

Hello All,
I'm currently trying to compile lcd4linux on Mac OS X 10.6.8 (Snow Leopard). I'd like to try it with the X11 driver to see what it can do for me, and maybe to try and write my own lcd4linux plugin. Unfortunately I can't get the svn trunk to build successfully on my machine at the moment.
Before going into details I'd like to know if what I want to achieve is possible at all? And if so, are there specific caveats I might be unaware of?
Cheers,
Alexander 		 	   		  

Re: [lcd4linux] HD44780 20x2 only shows 8 characters

[Joao B. <bon...@ya...>]

So  I downloaded the source code from svn and started looking at the HD44780 driver.

I did a small change in there and now I get all 20 characters on line 1 to display. But a widget in line 2 won't display at all.
Also, as text in widget 1 changes, it will wrap into line 2.

Basically, I changed this line in the goto() function into this:
    drv_HD_command(currController, (0x80 | 15), T_EXEC);

The changes I made in drv_HD44780.c are:

static int drv_HD_goto(int row, int col)
{
    int pos, controller;

    /* handle multiple controllers */
    for (pos = 0, controller = 0; controller < numControllers; controller++) {
        pos += CROWS[controller];
        if (row < pos) {
            currController = (1 << controller);
            break;
 }
        row -= CROWS[controller];
    }

    /* column outside of current display's width */
    if (col >= CCOLS[controller])
        return -1;

    if (0) {
        debug("goto: [%d,%d] mask=%d, controller=%d, size:%dx%d", row, col, cur$
     CROWS[controller], CCOLS[controller]);
    }

    /* 16x1 Displays are organized as 8x2 :-( */
    if (CCOLS[controller] == 16 && CROWS[controller] == 1 && col > 7) {
        row++;
        col -= 8;
    }

    if (Capabilities & CAP_HD66712) {
    /* the HD66712 doesn't have a braindamadged RAM layout */
        pos = row * 32 + col;
    } else {
        /* 16x4 Controllers use a slightly different layout */
        if (CCOLS[controller] == 16 && CROWS[controller] == 4) {
            pos = (row % 2) * 64 + (row / 2) * 16 + col;
        } else {
            pos = (row % 2) * 64 + (row / 2) * 20 + col;
        }
    }      /*  drv_HD_command(currController, (0x80 | pos), T_EXEC); */

    drv_HD_command(currController, (0x80 | 15), T_EXEC);

    /* return columns left on current display */
    return CCOLS[controller] - col;
//      return 20;
}


static void drv_HD_write(const int row, const int col, const char *data, const $
{
printf(" %s len is %d\n", data , len);

    int space = drv_HD_goto(row, col);

    if (space > 0) {
        drv_HD_data(currController, data, len > space ? space : len, T_EXEC);
    }

        /* JLB - cusor was blinking */
        drv_HD_command(allControllers, 0x0c, T_ONOFF);
}


Can anybody help on this?

Thanks







________________________________
 From: Joao Bonina <bon...@ya...>
To: "lcd...@li..." <lcd...@li...> 
Sent: Thursday, 1 December 2011, 2:07
Subject: Re: [lcd4linux] HD44780 20x2 only shows 8 characters
 

Can anybody give me some hints on how to to debug this?



________________________________
 From: Joao Bonina <bon...@ya...>
To: "lcd...@li..." <lcd...@li...> 
Sent: Tuesday, 29 November 2011, 22:46
Subject: [lcd4linux] HD44780 20x2 only shows 8 characters
 

Hello,

I'm trying a new lcd display, this time a CrystalFontz CFAH2002Y-PDI-ET (HD44780 compatible).

The problem is that it only shows 8 characters on line 1. If I send it more than 8 characters, nothing will show.

Also, can't get any widget to display on line 2.


the log and conf file are:

0# lcd4linux -Fvvq -f lcd4linux.conf
LCD4Linux 0.11.0-SVN-1092 starting
Dump of lcd4linux.conf:
  Display                           'HD44780-20x2'
  Display:HD44780-20x2.Bits         8
 
 Display:HD44780-20x2.Driver       'HD44780'
  Display:HD44780-20x2.Model        'generic'
  Display:HD44780-20x2.Port         '/dev/parport0'
  Display:HD44780-20x2.Size         '20x2'
  Display:HD44780-20x2.UseBusy      0
  Display:HD44780-20x2.Wire.ENABLE  'STROBE'
  Display:HD44780-20x2.Wire.ENABLE2 'GND'
  Display:HD44780-20x2.Wire.GPO     'GND'
  Display:HD44780-20x2.Wire.RS      'AUTOFD'
  Display:HD44780-20x2.Wire.RW      'INIT'
  Layout                            'Default'
 
 Layout:Default.Row1.Col1          'Make'
  Layout:Default.Row2.Col1          'Make2'
  Variables.counter                 0
  Variables.tick                    2000
  Widget:Make.align                 'R'
  Widget:Make.class                 'Text'
  Widget:Make.expression            'i1234567'
  Widget:Make.update                tick
 
 Widget:Make.width                 20
  Widget:Make2.align                'R'
  Widget:Make2.class                'Text'
  Widget:Make2.expression           'i5867'
  Widget:Make2.update               tick
  Widget:Make2.width                20
  Widget:Time.active                counter < 100
 
 Widget:Time.class                 'Timer'
  Widget:Time.expression            counter = counter+1
  Widget:Time.update                2000

plugin_cfg.c: Variable counter = '0' (0)
plugin_cfg.c: Variable tick = '2000' (2000)
[DBus] Error connecting to the dbus session bus: /usr/bin/dbus-launch terminated abnormally without any error message

lcd4linux.c: initializing driver HD44780
HD44780: $Rev: 1066 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parport0
HD44780: wiring: DISPLAY:RS        - PARPORT:AUTOFD (Pin
 14)
HD44780: wiring: DISPLAY:RW        - PARPORT:INIT   (Pin 16)
HD44780: wiring: DISPLAY:ENABLE    - PARPORT:STROBE (Pin  1)
HD44780: wiring: DISPLAY:ENABLE2   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE3   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE4   - PARPORT:GND
HD44780: wiring: DISPLAY:BACKLIGHT - PARPORT:GND
HD44780: wiring: DISPLAY:GPO       - PARPORT:GND
HD44780: wiring: DISPLAY:GPI       - PARPORT:GND
HD44780: wiring: DISPLAY:POWER     - PARPORT:GND
HD44780: timing:     CY =  1000 ns (default)
HD44780: timing:     PW =   450 ns (default)
HD44780: timing:     AS =   140 ns (default)
HD44780: timing:     AH =   
 20 ns (default)
HD44780: timing:  INIT1 =  4100 us (default)
HD44780: timing:  INIT2 =   100 us (default)
HD44780: timing:   EXEC =    80 us (default)
HD44780: timing:   WRCG =   120 us (default)
HD44780: timing:  CLEAR =  2250 us (default)
HD44780: timing:   HOME =  2250 us (default)
HD44780: timing:  ONOFF =  2250 us (default)
HD44780: not using busy-flag checking
HD44780: using 0 GPI's and 0 GPO's
initializing layout 'Default'
layout.c: Layout:Default: migrating 'row1.col1' to 'Layer:1.row1.col1'
layout.c: Layout:Default: migrating 'row2.col1' to 'Layer:1.row2.col1'
Creating new timer group (2000 ms)
 widget 'Make': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,20)
 widget 'Make2': Class 'text', Parent '<root>', Layer 1, Row 1, Col 0 (to 1,20)
lcd4linux.c: starting
 main loop





Conf file is:

Variables {
   tick 2000
   counter 0
}


Display HD44780-20x2 {
    Driver  'HD44780'
    Model 'generic'
    UseBusy  0
    Port    '/dev/parport0'
    Size    '20x2'
    Bits 8
    Wire {
        RW      'INIT'
        RS      'AUTOFD'
      ENABLE  'STROBE'
        ENABLE2 'GND'

       GPO     'GND'
    }
}



Widget Make {
    class 
 'Text'
    expression  'i1234567'
    width  20
    align 'R'
        update tick
}

Widget Make2 {
    class  'Text'
    expression  'i5867'
    width  20
     align 'R'
        update tick
}



Widget Time {
        class 'Timer'
        expression counter = counter+1
        active counter < 100
        update 2000
}

Layout Default {
    Row1 {
        Col1 'Make'
    }
    Row2 {
        Col1
 'Make2'
    }


Display 'HD44780-20x2'
Layout  'Default'




Will appreciate your help.

Kind regards,
Joao









------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Lcd4linux-users mailing list
Lcd...@li...
https://lists.sourceforge.net/lists/listinfo/lcd4linux-users



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Lcd4linux-users mailing list
Lcd...@li...
https://lists.sourceforge.net/lists/listinfo/lcd4linux-users

Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling

[Joao B. <bon...@ya...>]

Hello Michael,

with that particular LCD, I also had to switch the RS with RW and got that working. Thanks!

Now I have a problem with a 20x2 lcd, hope someone can chime in.

J



________________________________
 From: Joao Bonina <bon...@ya...>
To: "lcd...@li..." <lcd...@li...> 
Sent: Thursday, 10 November 2011, 20:18
Subject: Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling
 

Hi,

you're absolutely right Mattia.

Here is the output:

# lcd4linux -Fvvq  -f lcd4linux.conf
Version 0.10.1-RC2-796 starting
plugin_cfg.c: Variable tick = '500' (500)
[KVV] Using station 89
[KVV] Using default port 80
[KVV] Using default refresh interval of 60 seconds
[KVV] Default abbreviation setting: off
lcd4linux.c: initializing driver HD44780
HD44780: $Rev: 773 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parport0
HD44780: wiring: DISPLAY:RS        -
 PARPORT:INIT   (Pin 16)
HD44780: wiring: DISPLAY:RW        - PARPORT:AUTOFD (Pin 14)
HD44780: wiring: DISPLAY:ENABLE    - PARPORT:STROBE (Pin  1)
HD44780: wiring: DISPLAY:ENABLE2   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE3   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE4   - PARPORT:GND
HD44780: wiring: DISPLAY:BACKLIGHT - PARPORT:GND
HD44780: wiring: DISPLAY:GPO       - PARPORT:GND
HD44780: wiring: DISPLAY:POWER     - PARPORT:GND
HD44780: timing:     CY =  1000 ns (default)
HD44780: timing:     PW =   450 ns (default)
HD44780: timing:     AS =   140 ns (default)
HD44780: timing:     AH =    20 ns (default)
HD44780: timing:  INIT1 =  4100
 us (default)
HD44780: timing:  INIT2 =   100 us (default)
HD44780: timing:   EXEC =    80 us (default)
HD44780: timing:   WRCG =   120 us (default)
HD44780: timing:  CLEAR =  2250 us (default)
HD44780: timing:   HOME =  2250 us (default)
HD44780: timing:  ONOFF =  2250 us (default)
HD44780: using busy-flag checking
HD44780: using 0 GPI's and 0 GPO's
initializing layout 'Default'
lcd4linux.c: starting main loop
HD44780: timeout waiting for busy flag on controller 1 (0x80)
^Clcd4linux.c: got signal 2
lcd4linux.c: leaving main loop
HD44780: shutting down display.
HD44780: shutting down GPIO driver.
drv_generic_parport.c: closing ppdev /dev/parport0



The lcd4linux.conf file is:


Display HD44780-20x1 {
    Driver  'HD44780'
    Model 'generic'
    UseBusy  1
    Port    '/dev/parport0'
    Size    '20x1'
    Wire {
        RW      'AUTOFD'
        RS      'INIT'
        ENABLE  'STROBE'
        ENABLE2 'GND'
        GPO     'GND'

    }
}

Widget CPU {
  class      'Text'
    expression     'CPU'
    width      
 3
    align      'L'
}

Layout Default {
    Row1 {
        Col1 'CPU'
    }


Variables {
   tick 500
}

Display 'HD44780-20x1'
Layout  'Default'


Best regards,
Joao


________________________________
From: Mattia Jona-Lasinio <mat...@gm...>
To: "lcd...@li..." <lcd...@li...>
Sent: Thursday, 10 November 2011, 12:07
Subject: Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling

Hi,

can you be more specific on what exactly you do and what exactly happens?

Posting your current lcd4linux configuration file and a verbose output
from lcd4linux wouldn't harm either.

Best,

M


On Thu, Nov 10, 2011 at 12:57 PM, Joao Bonina <bon...@ya...> wrote:
> Hello,
> I just got a parallel HD44780-compatible lcd display and got it working with
> LCD4Linux.
> The first time I tried it, it workined really fine with the CPU widget
> showing.
> Then, I stopped/started LCD4Linux, and the text started scrolling
> left-to-right. This happens always, no matter what settings I tried to
> change or what else.
> LCD4Linux version is 0.10.1-RC2 on Debian Squeeze with
 2.6.38 kernel.
>
> Can anyone give me a hint on how to debug this?
> Cheers,
> Joao
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>
>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register
 now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Lcd4linux-users mailing list
Lcd...@li...
https://lists.sourceforge.net/lists/listinfo/lcd4linux-users



------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Lcd4linux-users mailing list
Lcd...@li...
https://lists.sourceforge.net/lists/listinfo/lcd4linux-users

Re: [lcd4linux] HD44780 20x2 only shows 8 characters

[Joao B. <bon...@ya...>]

Can anybody give me some hints on how to to debug this?



________________________________
 From: Joao Bonina <bon...@ya...>
To: "lcd...@li..." <lcd...@li...> 
Sent: Tuesday, 29 November 2011, 22:46
Subject: [lcd4linux] HD44780 20x2 only shows 8 characters
 

Hello,

I'm trying a new lcd display, this time a CrystalFontz CFAH2002Y-PDI-ET (HD44780 compatible).

The problem is that it only shows 8 characters on line 1. If I send it more than 8 characters, nothing will show.

Also, can't get any widget to display on line 2.


the log and conf file are:

0# lcd4linux -Fvvq -f lcd4linux.conf
LCD4Linux 0.11.0-SVN-1092 starting
Dump of lcd4linux.conf:
  Display                           'HD44780-20x2'
  Display:HD44780-20x2.Bits         8
 
 Display:HD44780-20x2.Driver       'HD44780'
  Display:HD44780-20x2.Model        'generic'
  Display:HD44780-20x2.Port         '/dev/parport0'
  Display:HD44780-20x2.Size         '20x2'
  Display:HD44780-20x2.UseBusy      0
  Display:HD44780-20x2.Wire.ENABLE  'STROBE'
  Display:HD44780-20x2.Wire.ENABLE2 'GND'
  Display:HD44780-20x2.Wire.GPO     'GND'
  Display:HD44780-20x2.Wire.RS      'AUTOFD'
  Display:HD44780-20x2.Wire.RW      'INIT'
  Layout                            'Default'
 
 Layout:Default.Row1.Col1          'Make'
  Layout:Default.Row2.Col1          'Make2'
  Variables.counter                 0
  Variables.tick                    2000
  Widget:Make.align                 'R'
  Widget:Make.class                 'Text'
  Widget:Make.expression            'i1234567'
  Widget:Make.update                tick
 
 Widget:Make.width                 20
  Widget:Make2.align                'R'
  Widget:Make2.class                'Text'
  Widget:Make2.expression           'i5867'
  Widget:Make2.update               tick
  Widget:Make2.width                20
  Widget:Time.active                counter < 100
 
 Widget:Time.class                 'Timer'
  Widget:Time.expression            counter = counter+1
  Widget:Time.update                2000

plugin_cfg.c: Variable counter = '0' (0)
plugin_cfg.c: Variable tick = '2000' (2000)
[DBus] Error connecting to the dbus session bus: /usr/bin/dbus-launch terminated abnormally without any error message

lcd4linux.c: initializing driver HD44780
HD44780: $Rev: 1066 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parport0
HD44780: wiring: DISPLAY:RS        - PARPORT:AUTOFD (Pin
 14)
HD44780: wiring: DISPLAY:RW        - PARPORT:INIT   (Pin 16)
HD44780: wiring: DISPLAY:ENABLE    - PARPORT:STROBE (Pin  1)
HD44780: wiring: DISPLAY:ENABLE2   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE3   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE4   - PARPORT:GND
HD44780: wiring: DISPLAY:BACKLIGHT - PARPORT:GND
HD44780: wiring: DISPLAY:GPO       - PARPORT:GND
HD44780: wiring: DISPLAY:GPI       - PARPORT:GND
HD44780: wiring: DISPLAY:POWER     - PARPORT:GND
HD44780: timing:     CY =  1000 ns (default)
HD44780: timing:     PW =   450 ns (default)
HD44780: timing:     AS =   140 ns (default)
HD44780: timing:     AH =   
 20 ns (default)
HD44780: timing:  INIT1 =  4100 us (default)
HD44780: timing:  INIT2 =   100 us (default)
HD44780: timing:   EXEC =    80 us (default)
HD44780: timing:   WRCG =   120 us (default)
HD44780: timing:  CLEAR =  2250 us (default)
HD44780: timing:   HOME =  2250 us (default)
HD44780: timing:  ONOFF =  2250 us (default)
HD44780: not using busy-flag checking
HD44780: using 0 GPI's and 0 GPO's
initializing layout 'Default'
layout.c: Layout:Default: migrating 'row1.col1' to 'Layer:1.row1.col1'
layout.c: Layout:Default: migrating 'row2.col1' to 'Layer:1.row2.col1'
Creating new timer group (2000 ms)
 widget 'Make': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,20)
 widget 'Make2': Class 'text', Parent '<root>', Layer 1, Row 1, Col 0 (to 1,20)
lcd4linux.c: starting
 main loop





Conf file is:

Variables {
   tick 2000
   counter 0
}


Display HD44780-20x2 {
    Driver  'HD44780'
    Model 'generic'
    UseBusy  0
    Port    '/dev/parport0'
    Size    '20x2'
    Bits 8
    Wire {
        RW      'INIT'
        RS      'AUTOFD'
      ENABLE  'STROBE'
        ENABLE2 'GND'

       GPO     'GND'
    }
}



Widget Make {
    class 
 'Text'
    expression  'i1234567'
    width  20
    align 'R'
        update tick
}

Widget Make2 {
    class  'Text'
    expression  'i5867'
    width  20
     align 'R'
        update tick
}



Widget Time {
        class 'Timer'
        expression counter = counter+1
        active counter < 100
        update 2000
}

Layout Default {
    Row1 {
        Col1 'Make'
    }
    Row2 {
        Col1
 'Make2'
    }


Display 'HD44780-20x2'
Layout  'Default'




Will appreciate your help.

Kind regards,
Joao









------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Lcd4linux-users mailing list
Lcd...@li...
https://lists.sourceforge.net/lists/listinfo/lcd4linux-users

[lcd4linux] HD44780 20x2 only shows 8 characters

[Joao B. <bon...@ya...>]

Hello,

I'm trying a new lcd display, this time a CrystalFontz CFAH2002Y-PDI-ET (HD44780 compatible).

The problem is that it only shows 8 characters on line 1. If I send it more than 8 characters, nothing will show.

Also, can't get any widget to display on line 2.


the log and conf file are:

0# lcd4linux -Fvvq -f lcd4linux.conf
LCD4Linux 0.11.0-SVN-1092 starting
Dump of lcd4linux.conf:
  Display                           'HD44780-20x2'
  Display:HD44780-20x2.Bits         8
  Display:HD44780-20x2.Driver       'HD44780'
  Display:HD44780-20x2.Model        'generic'
  Display:HD44780-20x2.Port         '/dev/parport0'
  Display:HD44780-20x2.Size         '20x2'
  Display:HD44780-20x2.UseBusy      0
  Display:HD44780-20x2.Wire.ENABLE  'STROBE'
  Display:HD44780-20x2.Wire.ENABLE2 'GND'
  Display:HD44780-20x2.Wire.GPO     'GND'
  Display:HD44780-20x2.Wire.RS      'AUTOFD'
  Display:HD44780-20x2.Wire.RW      'INIT'
  Layout                            'Default'
  Layout:Default.Row1.Col1          'Make'
  Layout:Default.Row2.Col1          'Make2'
  Variables.counter                 0
  Variables.tick                    2000
  Widget:Make.align                 'R'
  Widget:Make.class                 'Text'
  Widget:Make.expression            'i1234567'
  Widget:Make.update                tick
  Widget:Make.width                 20
  Widget:Make2.align                'R'
  Widget:Make2.class                'Text'
  Widget:Make2.expression           'i5867'
  Widget:Make2.update               tick
  Widget:Make2.width                20
  Widget:Time.active                counter < 100
  Widget:Time.class                 'Timer'
  Widget:Time.expression            counter = counter+1
  Widget:Time.update                2000

plugin_cfg.c: Variable counter = '0' (0)
plugin_cfg.c: Variable tick = '2000' (2000)
[DBus] Error connecting to the dbus session bus: /usr/bin/dbus-launch terminated abnormally without any error message

lcd4linux.c: initializing driver HD44780
HD44780: $Rev: 1066 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parport0
HD44780: wiring: DISPLAY:RS        - PARPORT:AUTOFD (Pin 14)
HD44780: wiring: DISPLAY:RW        - PARPORT:INIT   (Pin 16)
HD44780: wiring: DISPLAY:ENABLE    - PARPORT:STROBE (Pin  1)
HD44780: wiring: DISPLAY:ENABLE2   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE3   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE4   - PARPORT:GND
HD44780: wiring: DISPLAY:BACKLIGHT - PARPORT:GND
HD44780: wiring: DISPLAY:GPO       - PARPORT:GND
HD44780: wiring: DISPLAY:GPI       - PARPORT:GND
HD44780: wiring: DISPLAY:POWER     - PARPORT:GND
HD44780: timing:     CY =  1000 ns (default)
HD44780: timing:     PW =   450 ns (default)
HD44780: timing:     AS =   140 ns (default)
HD44780: timing:     AH =    20 ns (default)
HD44780: timing:  INIT1 =  4100 us (default)
HD44780: timing:  INIT2 =   100 us (default)
HD44780: timing:   EXEC =    80 us (default)
HD44780: timing:   WRCG =   120 us (default)
HD44780: timing:  CLEAR =  2250 us (default)
HD44780: timing:   HOME =  2250 us (default)
HD44780: timing:  ONOFF =  2250 us (default)
HD44780: not using busy-flag checking
HD44780: using 0 GPI's and 0 GPO's
initializing layout 'Default'
layout.c: Layout:Default: migrating 'row1.col1' to 'Layer:1.row1.col1'
layout.c: Layout:Default: migrating 'row2.col1' to 'Layer:1.row2.col1'
Creating new timer group (2000 ms)
 widget 'Make': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,20)
 widget 'Make2': Class 'text', Parent '<root>', Layer 1, Row 1, Col 0 (to 1,20)
lcd4linux.c: starting main loop





Conf file is:

Variables {
   tick 2000
   counter 0
}


Display HD44780-20x2 {
    Driver  'HD44780'
    Model 'generic'
    UseBusy  0
    Port    '/dev/parport0'
    Size    '20x2'
    Bits 8
    Wire {
        RW      'INIT'
        RS      'AUTOFD'
      ENABLE  'STROBE'
        ENABLE2 'GND'

       GPO     'GND'
    }
}



Widget Make {
    class  'Text'
    expression  'i1234567'
    width  20
    align 'R'
        update tick
}

Widget Make2 {
    class  'Text'
    expression  'i5867'
    width  20
     align 'R'
        update tick
}



Widget Time {
        class 'Timer'
        expression counter = counter+1
        active counter < 100
        update 2000
}

Layout Default {
    Row1 {
        Col1 'Make'
    }
    Row2 {
        Col1 'Make2'
    }


Display 'HD44780-20x2'
Layout  'Default'




Will appreciate your help.

Kind regards,
Joao

Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling

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

Looks like ypu're using busy-flag checking (lcd4linux.conf:useBusy 1) which is not working (HD44780: timeout waiting for 
busy flag on controller 1 (0x80))

Try to disable busy-flag checking (set useBusy to 0 or remove this entry completely)



hope this helps, michael


Am 2011-11-10 21:18, schrieb Joao Bonina:
> Hi,
>
> you're absolutely right Mattia.
>
> Here is the output:
>
> # lcd4linux -Fvvq -f lcd4linux.conf
> Version 0.10.1-RC2-796 starting
> plugin_cfg.c: Variable tick = '500' (500)
> [KVV] Using station 89
> [KVV] Using default port 80
> [KVV] Using default refresh interval of 60 seconds
> [KVV] Default abbreviation setting: off
> lcd4linux.c: initializing driver HD44780
> HD44780: $Rev: 773 $
> HD44780: using model 'generic'
> HD44780: using parallel port
> HD44780: using 1 Controller(s)
> HD44780: using 8 bit mode
> udelay: using gettimeofday() delay loop
> HD44780: using ppdev /dev/parport0
> HD44780: wiring: DISPLAY:RS - PARPORT:INIT (Pin 16)
> HD44780: wiring: DISPLAY:RW - PARPORT:AUTOFD (Pin 14)
> HD44780: wiring: DISPLAY:ENABLE - PARPORT:STROBE (Pin 1)
> HD44780: wiring: DISPLAY:ENABLE2 - PARPORT:GND
> HD44780: wiring: DISPLAY:ENABLE3 - PARPORT:GND
> HD44780: wiring: DISPLAY:ENABLE4 - PARPORT:GND
> HD44780: wiring: DISPLAY:BACKLIGHT - PARPORT:GND
> HD44780: wiring: DISPLAY:GPO - PARPORT:GND
> HD44780: wiring: DISPLAY:POWER - PARPORT:GND
> HD44780: timing: CY = 1000 ns (default)
> HD44780: timing: PW = 450 ns (default)
> HD44780: timing: AS = 140 ns (default)
> HD44780: timing: AH = 20 ns (default)
> HD44780: timing: INIT1 = 4100 us (default)
> HD44780: timing: INIT2 = 100 us (default)
> HD44780: timing: EXEC = 80 us (default)
> HD44780: timing: WRCG = 120 us (default)
> HD44780: timing: CLEAR = 2250 us (default)
> HD44780: timing: HOME = 2250 us (default)
> HD44780: timing: ONOFF = 2250 us (default)
> HD44780: using busy-flag checking
> HD44780: using 0 GPI's and 0 GPO's
> initializing layout 'Default'
> lcd4linux.c: starting main loop
> HD44780: timeout waiting for busy flag on controller 1 (0x80)
> ^Clcd4linux.c: got signal 2
> lcd4linux.c: leaving main loop
> HD44780: shutting down display.
> HD44780: shutting down GPIO driver.
> drv_generic_parport.c: closing ppdev /dev/parport0
>
>
>
> The lcd4linux.conf file is:
>
>
> Display HD44780-20x1 {
> Driver 'HD44780'
> Model 'generic'
> UseBusy 1
> Port '/dev/parport0'
> Size '20x1'
> Wire {
> RW 'AUTOFD'
> RS 'INIT'
> ENABLE 'STROBE'
> ENABLE2 'GND'
> GPO 'GND'
>
> }
> }
>
> Widget CPU {
> class 'Text'
> expression 'CPU'
> width 3
> align 'L'
> }
>
> Layout Default {
> Row1 {
> Col1 'CPU'
> }
>
>
> Variables {
> tick 500
> }
>
> Display 'HD44780-20x1'
> Layout 'Default'
>
>
> Best regards,
> Joao
>
> ------------------------------------------------------------------------------------------------------------------------
> *From:* Mattia Jona-Lasinio <mat...@gm...>
> *To:* "lcd...@li..." <lcd...@li...>
> *Sent:* Thursday, 10 November 2011, 12:07
> *Subject:* Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling
>
> Hi,
>
> can you be more specific on what exactly you do and what exactly happens?
>
> Posting your current lcd4linux configuration file and a verbose output
> from lcd4linux wouldn't harm either.
>
> Best,
>
> M
>
>
> On Thu, Nov 10, 2011 at 12:57 PM, Joao Bonina <bon...@ya... <mailto:bon...@ya...>> wrote:
>  > Hello,
>  > I just got a parallel HD44780-compatible lcd display and got it working with
>  > LCD4Linux.
>  > The first time I tried it, it workined really fine with the CPU widget
>  > showing.
>  > Then, I stopped/started LCD4Linux, and the text started scrolling
>  > left-to-right. This happens always, no matter what settings I tried to
>  > change or what else.
>  > LCD4Linux version is 0.10.1-RC2 on Debian Squeeze with 2.6.38 kernel.
>  >
>  > Can anyone give me a hint on how to debug this?
>  > Cheers,
>  > Joao
>  >
>  > ------------------------------------------------------------------------------
>  > RSA(R) Conference 2012
>  > Save $700 by Nov 18
>  > Register now
>  > http://p.sf.net/sfu/rsa-sfdev2dev1
>  > _______________________________________________
>  > Lcd4linux-users mailing list
>  > Lcd...@li... <mailto:Lcd...@li...>
>  > https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>  >
>  >
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li... <mailto:Lcd...@li...>
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
>
>
>
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users

-- 
Michael Reinelt <mi...@re...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling

[Joao B. <bon...@ya...>]

Hi,

you're absolutely right Mattia.

Here is the output:

# lcd4linux -Fvvq  -f lcd4linux.conf
Version 0.10.1-RC2-796 starting
plugin_cfg.c: Variable tick = '500' (500)
[KVV] Using station 89
[KVV] Using default port 80
[KVV] Using default refresh interval of 60 seconds
[KVV] Default abbreviation setting: off
lcd4linux.c: initializing driver HD44780
HD44780: $Rev: 773 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parport0
HD44780: wiring: DISPLAY:RS        -
 PARPORT:INIT   (Pin 16)
HD44780: wiring: DISPLAY:RW        - PARPORT:AUTOFD (Pin 14)
HD44780: wiring: DISPLAY:ENABLE    - PARPORT:STROBE (Pin  1)
HD44780: wiring: DISPLAY:ENABLE2   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE3   - PARPORT:GND
HD44780: wiring: DISPLAY:ENABLE4   - PARPORT:GND
HD44780: wiring: DISPLAY:BACKLIGHT - PARPORT:GND
HD44780: wiring: DISPLAY:GPO       - PARPORT:GND
HD44780: wiring: DISPLAY:POWER     - PARPORT:GND
HD44780: timing:     CY =  1000 ns (default)
HD44780: timing:     PW =   450 ns (default)
HD44780: timing:     AS =   140 ns (default)
HD44780: timing:     AH =    20 ns (default)
HD44780: timing:  INIT1 =  4100
 us (default)
HD44780: timing:  INIT2 =   100 us (default)
HD44780: timing:   EXEC =    80 us (default)
HD44780: timing:   WRCG =   120 us (default)
HD44780: timing:  CLEAR =  2250 us (default)
HD44780: timing:   HOME =  2250 us (default)
HD44780: timing:  ONOFF =  2250 us (default)
HD44780: using busy-flag checking
HD44780: using 0 GPI's and 0 GPO's
initializing layout 'Default'
lcd4linux.c: starting main loop
HD44780: timeout waiting for busy flag on controller 1 (0x80)
^Clcd4linux.c: got signal 2
lcd4linux.c: leaving main loop
HD44780: shutting down display.
HD44780: shutting down GPIO driver.
drv_generic_parport.c: closing ppdev /dev/parport0



The lcd4linux.conf file is:


Display HD44780-20x1 {
    Driver  'HD44780'
    Model 'generic'
    UseBusy  1
    Port    '/dev/parport0'
    Size    '20x1'
    Wire {
        RW      'AUTOFD'
        RS      'INIT'
        ENABLE  'STROBE'
        ENABLE2 'GND'
        GPO     'GND'

    }
}

Widget CPU {
  class      'Text'
    expression     'CPU'
    width      
 3
    align      'L'
}

Layout Default {
    Row1 {
        Col1 'CPU'
    }


Variables {
   tick 500
}

Display 'HD44780-20x1'
Layout  'Default'


Best regards,
Joao


________________________________
From: Mattia Jona-Lasinio <mat...@gm...>
To: "lcd...@li..." <lcd...@li...>
Sent: Thursday, 10 November 2011, 12:07
Subject: Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling

Hi,

can you be more specific on what exactly you do and what exactly happens?

Posting your current lcd4linux configuration file and a verbose output
from lcd4linux wouldn't harm either.

Best,

M


On Thu, Nov 10, 2011 at 12:57 PM, Joao Bonina <bon...@ya...> wrote:
> Hello,
> I just got a parallel HD44780-compatible lcd display and got it working with
> LCD4Linux.
> The first time I tried it, it workined really fine with the CPU widget
> showing.
> Then, I stopped/started LCD4Linux, and the text started scrolling
> left-to-right. This happens always, no matter what settings I tried to
> change or what else.
> LCD4Linux version is 0.10.1-RC2 on Debian Squeeze with 2.6.38 kernel.
>
> Can anyone give me a hint on how to debug this?
> Cheers,
> Joao
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>
>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Lcd4linux-users mailing list
Lcd...@li...
https://lists.sourceforge.net/lists/listinfo/lcd4linux-users

Re: [lcd4linux] Parallel HD44780 Lcd display keeps scrolling

[Mattia Jona-L. <mat...@gm...>]

Hi,

can you be more specific on what exactly you do and what exactly happens?

Posting your current lcd4linux configuration file and a verbose output
from lcd4linux wouldn't harm either.

Best,

M


On Thu, Nov 10, 2011 at 12:57 PM, Joao Bonina <bon...@ya...> wrote:
> Hello,
> I just got a parallel HD44780-compatible lcd display and got it working with
> LCD4Linux.
> The first time I tried it, it workined really fine with the CPU widget
> showing.
> Then, I stopped/started LCD4Linux, and the text started scrolling
> left-to-right. This happens always, no matter what settings I tried to
> change or what else.
> LCD4Linux version is 0.10.1-RC2 on Debian Squeeze with 2.6.38 kernel.
>
> Can anyone give me a hint on how to debug this?
> Cheers,
> Joao
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>
>

[lcd4linux] Parallel HD44780 Lcd display keeps scrolling

[Joao B. <bon...@ya...>]

Hello,

I just got a parallel HD44780-compatible lcd display and got it working with LCD4Linux.

The first time I tried it, it workined really fine with the CPU widget showing.

Then, I stopped/started LCD4Linux, and the text started scrolling left-to-right. This happens always, no matter what settings I tried to change or what else.

LCD4Linux version is 0.10.1-RC2 on Debian Squeeze with 2.6.38 kernel.


Can anyone give me a hint on how to debug this?

Cheers,
Joao

Re: [lcd4linux] Fwd: PicoLCD from Mini-Box M300 not detecting?

[Kaya S. <kay...@gm...>]

The actual SEGFAULT from the config provided in the previous email is this:

lcd4linux -Fvv:

Version 0.11.0-SVN-965 starting
plugin_cfg.c: Variable tack = '100' (100)
plugin_cfg.c: Variable tick = '500' (500)
lcd4linux.c: initializing driver picoLCD
picoLCD: $Rev: 947 $
picoLCD: scanning for picoLCD...
picoLCD: found picoLCD on bus 004 device 002
picoLCD: Manufacturer='ITUNER INC' Product='USB-LCD-20x2' 
SerialNumber='1.57rel.'
Setting contrast to 0
Setting backlight to 1
picoLCD: reserving 6 of 8 user-defined characters for icons
picoLCD: using 1 GPI's and 8 GPO's
initializing layout 'L20x2'
  widget 'GPO_kf1': Class 'gpo', Parent '<root>', Layer 0, Row 1, Col 0
Segmentation fault


????


Regards,


Kaya


On 10/15/2011 05:22 AM, Michael Reinelt wrote:
> Hi Kaya,
>
> Could you provide a copy of your lcd4linux.conf?
>
> signal 2 is SIGINT, did you stop it with Ctrl-C or something?
>
>
> regards, Michael
>
> Am 2011-10-12 21:01, schrieb Kaya Saman:
>> Ok managed to get the display recognized as it was on the wrong USB 
>> header!
>>
>> However, when running: lcd4linux -Fvv
>>
>> I get:
>>
>> # cat lcd
>> Version 0.10.1-RC1-768 starting
>> plugin_cfg.c: Variable n = '0' (0)
>> plugin_cfg.c: Variable nkey = '0' (0)
>> [KVV] Using station 89
>> [KVV] Using default port 80
>> [KVV] Using default refresh interval of 60 seconds
>> [KVV] Default abbreviation setting: off
>> lcd4linux.c: initializing driver picoLCD
>> picoLCD: $Rev: 759 $
>> picoLCD: scanning for picoLCD...
>> picoLCD: found picoLCD on bus 004 device 002
>> picoLCD: Manufacturer='ITUNER INC' Product='USB-LCD-20x2' 
>> SerialNumber='1.57rel.'
>> Setting contrast to 0
>> Setting backlight to 1
>> picoLCD: reserving 6 of 8 user-defined characters for icons
>> picoLCD: using 0 GPI's and 8 GPO's
>> initializing layout 'L20x2'
>> lcd4linux.c: starting main loop
>> lcd4linux.c: got signal 2
>> lcd4linux.c: leaving main loop
>> picoLCD: shutting down.
>>
>>
>> with a whole bunch of these errors:
>>
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>>
>>
>> and additionally this error too:
>>
>> Starting lcd4linux: error evaluating variable 'button_text' from 
>> /etc/lcd4linux.conf
>>
>>
>> Can anyone help me with that?
>>
>>
>> Thanks,
>>
>>
>> Kaya
>>
>>
>>
>> -------- Original Message --------
>> Subject:     PicoLCD from Mini-Box M300 not detecting?
>> Date:     Wed, 12 Oct 2011 21:17:31 +0300
>> From:     Kaya Saman <kay...@gm...>
>> To:     lcd...@li...
>>
>>
>>
>> Hi,
>>
>> I'm totally new to working with LCD's and linux. I purchased a Mini-Box
>> Mini-ITX case with 20x2 PicoLCD module embedded to run on a Trixbox
>> based Asterisk server.
>>
>> The display lights up and information is displayed on the panel and the
>> keyboard works at least for the power key.
>>
>> I hooked it up via the on-board USB connector to the internal USB header
>> on the system board.
>>
>>
>> I have the wiring diagram for it at hand even though came pre-wired but
>> still I think all that was needed was to attach the USB cable to the
>> system board.....
>>
>>
>> Anyway, when I run the lcd4linux command I get this output:
>>
>> # lcd4linux -Fvv
>> Version 0.10.1-RC1-768 starting
>> error evaluating variable 'button_text' from /etc/lcd4linux.conf
>> plugin_cfg.c: Variable n = '0' (0)
>> plugin_cfg.c: Variable nkey = '0' (0)
>> [KVV] Using station 89
>> [KVV] Using default port 80
>> [KVV] Using default refresh interval of 60 seconds
>> [KVV] Default abbreviation setting: off
>> lcd4linux.c: initializing driver picoLCD
>> picoLCD: $Rev: 759 $
>> picoLCD: scanning for picoLCD...
>> picoLCD: could not find a picoLCD
>>
>> How come that it isn't finding the picoLCD device?
>>
>>
>> I took the sample configuration from here:
>>
>> http://ssl.bulix.org/projects/lcd4linux/wiki/picoLCD
>>
>>
>> and also checked out this as well:
>>
>> http://ssl.bulix.org/projects/lcd4linux/ticket/265
>>
>> but am a bit confused?
>>
>>
>> Can anyone give me a hand as to what is going on?
>>
>>
>>
>>
>> This is the output of uname -a:
>>
>> 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386
>> GNU/Linux
>>
>>
>>
>> lsusb doesn't actually show anything either?
>>
>>
>> # lsusb
>> Bus 005 Device 001: ID 0000:0000
>> Bus 001 Device 001: ID 0000:0000
>> Bus 002 Device 001: ID 0000:0000
>> Bus 002 Device 002: ID 0b38:0003 Gear Head Keyboard
>> Bus 003 Device 001: ID 0000:0000
>> Bus 004 Device 001: ID 0000:0000
>>
>>
>>
>> Many thanks!!
>>
>>
>> Kaya
>>
>>
>>
>> ------------------------------------------------------------------------------ 
>>
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2d-oct
>>
>>
>>
>> _______________________________________________
>> Lcd4linux-users mailing list
>> Lcd...@li...
>> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>

Re: [lcd4linux] Fwd: PicoLCD from Mini-Box M300 not detecting?

[Kaya S. <kay...@gm...>]

Hi Michael,

thanks for the response!

I have managed to get as far as this:

----------------------------

Variables {
     tick 500
     tack 100
}


Widget TimerW {
    class 'Timer'
    expression n=LCD::GPI(1);nkey=n!=0?n:nkey
    active 1
    update 100
}



Widget Eth0 {
     class 'Text'
     expression (netdev('eth0', 'Rx_bytes', 500)+netdev('eth0', 
'Tx_bytes', 500))/1024
     prefix 'eth0'
     postfix 'B'
     width  9
     precision 0
     align 'R'
     update tick
}

Widget Eth0Bar {
     class 'Bar'
     expression  netdev('eth0', 'Rx_bytes', 500)
     expression2 netdev('eth0', 'Tx_bytes', 500)
     length 9
     direction 'E'
     update tack
}



Widget CPU {
     class  'Text'
     expression  uname('machine')
     prefix 'CPU '
     width  9
     align  'L'
     update tick
}



Widget Busy {
     class 'Text'
     expression proc_stat::cpu('busy', 500)
     prefix 'CPU'
     postfix '%'
     width 10
     precision 1
     align 'R'
     update tick
}


Widget BusyBar {
     class 'Bar'
     expression  proc_stat::cpu('busy',   500)
     expression2 proc_stat::cpu('system', 500)
     length 9
     direction 'E'
     update tack
}


Widget GPO_kf1 {
    class 'GPO'
    expression button_text=nkey==3?uptime('%d days 
%H:%M:%S'):button_text;nkey==3?1:0
    update 300
}

Widget GPO_kf2 {
    class 'GPO'
    expression button_text=nkey==4?strftime('%a,%d/%m 
%H:%M:%S',time()):button_text;nkey==4?1:0
    update 300
}


Display picoLCD20x2 {
    Driver   'picoLCD'
    Size     '20x2'
    Contrast  0
    Backlight 1
    Icons     6
}

Layout L20x2 {
    Row1 {
         Col1 'Eth0'
     Col11 'Busy'
    }
    Row2 {
     Col1 'Eth0Bar'
     Col11 'BusyBar'
    }
Layer1 {
    Timer1 'TimerW'
    GPO2       'GPO_kf1'
    GPO3       'GPO_kf2'
}
}

Display 'picoLCD20x2'
Layout 'L20x2'

-------------------------------------------------


I have now upgraded to the SVN version off the site: 
lcd4linux-0.11.0-SVN as I compiled it myself.


I now can display the desired content on the LCD but the software seems 
to SEGFAULT if I don't use the 'Layers'???


Additionally with the content provided I can't read anything from the 
F1-F4 keys either :-(


Regards,


Kaya


On 10/15/2011 05:22 AM, Michael Reinelt wrote:
> Hi Kaya,
>
> Could you provide a copy of your lcd4linux.conf?
>
> signal 2 is SIGINT, did you stop it with Ctrl-C or something?
>
>
> regards, Michael
>
> Am 2011-10-12 21:01, schrieb Kaya Saman:
>> Ok managed to get the display recognized as it was on the wrong USB 
>> header!
>>
>> However, when running: lcd4linux -Fvv
>>
>> I get:
>>
>> # cat lcd
>> Version 0.10.1-RC1-768 starting
>> plugin_cfg.c: Variable n = '0' (0)
>> plugin_cfg.c: Variable nkey = '0' (0)
>> [KVV] Using station 89
>> [KVV] Using default port 80
>> [KVV] Using default refresh interval of 60 seconds
>> [KVV] Default abbreviation setting: off
>> lcd4linux.c: initializing driver picoLCD
>> picoLCD: $Rev: 759 $
>> picoLCD: scanning for picoLCD...
>> picoLCD: found picoLCD on bus 004 device 002
>> picoLCD: Manufacturer='ITUNER INC' Product='USB-LCD-20x2' 
>> SerialNumber='1.57rel.'
>> Setting contrast to 0
>> Setting backlight to 1
>> picoLCD: reserving 6 of 8 user-defined characters for icons
>> picoLCD: using 0 GPI's and 8 GPO's
>> initializing layout 'L20x2'
>> lcd4linux.c: starting main loop
>> lcd4linux.c: got signal 2
>> lcd4linux.c: leaving main loop
>> picoLCD: shutting down.
>>
>>
>> with a whole bunch of these errors:
>>
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>> picoLCD::GPI(1): GPI out of range (1..0)
>>
>>
>> and additionally this error too:
>>
>> Starting lcd4linux: error evaluating variable 'button_text' from 
>> /etc/lcd4linux.conf
>>
>>
>> Can anyone help me with that?
>>
>>
>> Thanks,
>>
>>
>> Kaya
>>
>>
>>
>> -------- Original Message --------
>> Subject:     PicoLCD from Mini-Box M300 not detecting?
>> Date:     Wed, 12 Oct 2011 21:17:31 +0300
>> From:     Kaya Saman <kay...@gm...>
>> To:     lcd...@li...
>>
>>
>>
>> Hi,
>>
>> I'm totally new to working with LCD's and linux. I purchased a Mini-Box
>> Mini-ITX case with 20x2 PicoLCD module embedded to run on a Trixbox
>> based Asterisk server.
>>
>> The display lights up and information is displayed on the panel and the
>> keyboard works at least for the power key.
>>
>> I hooked it up via the on-board USB connector to the internal USB header
>> on the system board.
>>
>>
>> I have the wiring diagram for it at hand even though came pre-wired but
>> still I think all that was needed was to attach the USB cable to the
>> system board.....
>>
>>
>> Anyway, when I run the lcd4linux command I get this output:
>>
>> # lcd4linux -Fvv
>> Version 0.10.1-RC1-768 starting
>> error evaluating variable 'button_text' from /etc/lcd4linux.conf
>> plugin_cfg.c: Variable n = '0' (0)
>> plugin_cfg.c: Variable nkey = '0' (0)
>> [KVV] Using station 89
>> [KVV] Using default port 80
>> [KVV] Using default refresh interval of 60 seconds
>> [KVV] Default abbreviation setting: off
>> lcd4linux.c: initializing driver picoLCD
>> picoLCD: $Rev: 759 $
>> picoLCD: scanning for picoLCD...
>> picoLCD: could not find a picoLCD
>>
>> How come that it isn't finding the picoLCD device?
>>
>>
>> I took the sample configuration from here:
>>
>> http://ssl.bulix.org/projects/lcd4linux/wiki/picoLCD
>>
>>
>> and also checked out this as well:
>>
>> http://ssl.bulix.org/projects/lcd4linux/ticket/265
>>
>> but am a bit confused?
>>
>>
>> Can anyone give me a hand as to what is going on?
>>
>>
>>
>>
>> This is the output of uname -a:
>>
>> 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386
>> GNU/Linux
>>
>>
>>
>> lsusb doesn't actually show anything either?
>>
>>
>> # lsusb
>> Bus 005 Device 001: ID 0000:0000
>> Bus 001 Device 001: ID 0000:0000
>> Bus 002 Device 001: ID 0000:0000
>> Bus 002 Device 002: ID 0b38:0003 Gear Head Keyboard
>> Bus 003 Device 001: ID 0000:0000
>> Bus 004 Device 001: ID 0000:0000
>>
>>
>>
>> Many thanks!!
>>
>>
>> Kaya
>>
>>
>>
>> ------------------------------------------------------------------------------ 
>>
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2d-oct
>>
>>
>>
>> _______________________________________________
>> Lcd4linux-users mailing list
>> Lcd...@li...
>> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
>