Menu
▾
▴
lcd4linux-users
|
From: Matthew H. <ma...@ma...> - 2015-02-16 10:04:48
|
Hi all,
Hoping someone can point me in the right direction.
I'm running LCD4Linux on a Sophos UTM box (Suse base), I suspect I may have
a dud parallel port, but wanted someone elses thoughts.
LCD4Linux is compiled with just the HD44870 driver, I'm doing a basic
config just to prove I can get a display up on the LCD. I have
double/triple checked wiring and I'm sure I have it right.
My config file looks like this:
----------------------------------------------------------------
Display HD44780-winamp {
Driver 'HD44780'
Model 'generic'
UseBusy 1
Port '/dev/parport0'
Size '16x2'
Wire {
RW 'AUTOFD'
RS 'INIT'
ENABLE 'STROBE'
ENABLE2 'GND'
GPO 'GND'
}
}
Widget MEM {
class 'Text'
expression meminfo('MemTotal')/1024
prefix 'MB:'
width 11
align 'L'
precision '0'
update 1000
}
Layout Default {
Row1 {
Col1 'MEM'
}
}
Display 'HD44780-winamp'
Layout 'Default'
----------------------------------------------------------------
When I run it using: sudo /sbin/lcd4linux -Fvv
I get the following:
----------------------------------------------------------------
Version 0.11.0-SVN-965 starting
lcd4linux.c: initializing driver HD44780
HD44780: $Rev: 905 $
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: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: using busy-flag checking
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: timeout waiting for busy flag on controller 1 (0xff)
HD44780: too many busy flag failures, turning off busy flag checking.
HD44780: using 0 GPI's and 0 GPO's
initializing layout 'Default'
widget 'MEM': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0
lcd4linux.c: starting main loop
----------------------------------------------------------------
But nothing ever displays on the LCD. I get the above regardless if the LCD
is connected or not, so I simply don't think it is seeing the LCD at all. I
have tried two different LCDs as well with the same result
Any pointers from here or how I can trouble shoot further?
Thanks in advance!
Regards,
Matt Hodder
|
|
From: Piet v. d. B. <pv...@te...> - 2015-02-16 15:50:30
|
Hi Matthew,
Did you check the contrast of the LCD's ?
Another thing that can be the problem is the newer parallel ports use
3.3 Volt on the pins
and most of the LCD's needs 5 Volt to operate. You should check this out.
Perhaps some other list member can check the config for you.
regards
Piet
On 16-2-2015 10:04, Matthew Hodder wrote:
> Hi all,
>
> Hoping someone can point me in the right direction.
>
> I'm running LCD4Linux on a Sophos UTM box (Suse base), I suspect I may
> have a dud parallel port, but wanted someone elses thoughts.
>
> LCD4Linux is compiled with just the HD44870 driver, I'm doing a basic
> config just to prove I can get a display up on the LCD. I have
> double/triple checked wiring and I'm sure I have it right.
>
> My config file looks like this:
>
> ----------------------------------------------------------------
>
> Display HD44780-winamp {
> Driver 'HD44780'
> Model 'generic'
> UseBusy 1
> Port '/dev/parport0'
> Size '16x2'
> Wire {
> RW 'AUTOFD'
> RS 'INIT'
> ENABLE 'STROBE'
> ENABLE2 'GND'
> GPO 'GND'
> }
> }
>
>
> Widget MEM {
> class 'Text'
> expression meminfo('MemTotal')/1024
> prefix 'MB:'
> width 11
> align 'L'
> precision '0'
> update 1000
> }
>
> Layout Default {
> Row1 {
> Col1 'MEM'
> }
> }
>
> Display 'HD44780-winamp'
> Layout 'Default'
>
> ----------------------------------------------------------------
>
> When I run it using: sudo /sbin/lcd4linux -Fvv
>
> I get the following:
>
> ----------------------------------------------------------------
>
> Version 0.11.0-SVN-965 starting
> lcd4linux.c: initializing driver HD44780
> HD44780: $Rev: 905 $
> 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: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: using busy-flag checking
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: too many busy flag failures, turning off busy flag checking.
> HD44780: using 0 GPI's and 0 GPO's
> initializing layout 'Default'
> widget 'MEM': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0
> lcd4linux.c: starting main loop
>
> ----------------------------------------------------------------
>
> But nothing ever displays on the LCD. I get the above regardless if
> the LCD is connected or not, so I simply don't think it is seeing the
> LCD at all. I have tried two different LCDs as well with the same result
>
> Any pointers from here or how I can trouble shoot further?
>
> Thanks in advance!
>
> Regards,
> Matt Hodder
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Lcd4linux-users mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-users
|
|
From: Michael R. <mi...@re...> - 2015-02-16 16:27:53
|
Hello Matthew,
do you have a oscilloscope or something?
I guess either the wiring os wrong, or soemthing is wrong with your parport.
are you sure you have the RW line connected properly?
From the warnings in the log, the display does not return the busy-flag (which is ok if you don't use busyflag
checking), but it may be a hint that something is very basically wrong.
checking some of the signals on the parallel port with a oscilloscope could help a lot, we don't need deep timing or
signal nalysis, just knowing that the signal on some pins is "moving"
regards, Michael
Am 2015-02-16 um 11:04 schrieb Matthew Hodder:
> Hi all,
>
> Hoping someone can point me in the right direction.
>
> I'm running LCD4Linux on a Sophos UTM box (Suse base), I suspect I may have a dud parallel port, but wanted someone
> elses thoughts.
>
> LCD4Linux is compiled with just the HD44870 driver, I'm doing a basic config just to prove I can get a display up on the
> LCD. I have double/triple checked wiring and I'm sure I have it right.
>
> My config file looks like this:
>
> ----------------------------------------------------------------
>
> Display HD44780-winamp {
> Driver 'HD44780'
> Model 'generic'
> UseBusy 1
> Port '/dev/parport0'
> Size '16x2'
> Wire {
> RW 'AUTOFD'
> RS 'INIT'
> ENABLE 'STROBE'
> ENABLE2 'GND'
> GPO 'GND'
> }
> }
>
>
> Widget MEM {
> class 'Text'
> expression meminfo('MemTotal')/1024
> prefix 'MB:'
> width 11
> align 'L'
> precision '0'
> update 1000
> }
>
> Layout Default {
> Row1 {
> Col1 'MEM'
> }
> }
>
> Display 'HD44780-winamp'
> Layout 'Default'
>
> ----------------------------------------------------------------
>
> When I run it using: sudo /sbin/lcd4linux -Fvv
>
> I get the following:
>
> ----------------------------------------------------------------
>
> Version 0.11.0-SVN-965 starting
> lcd4linux.c: initializing driver HD44780
> HD44780: $Rev: 905 $
> 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: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: using busy-flag checking
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: timeout waiting for busy flag on controller 1 (0xff)
> HD44780: too many busy flag failures, turning off busy flag checking.
> HD44780: using 0 GPI's and 0 GPO's
> initializing layout 'Default'
> widget 'MEM': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0
> lcd4linux.c: starting main loop
>
> ----------------------------------------------------------------
>
> But nothing ever displays on the LCD. I get the above regardless if the LCD is connected or not, so I simply don't think
> it is seeing the LCD at all. I have tried two different LCDs as well with the same result
>
> Any pointers from here or how I can trouble shoot further?
>
> Thanks in advance!
>
> Regards,
> Matt Hodder
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> 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
|
|
From: Matthew H. <ma...@ma...> - 2015-02-17 05:25:44
|
Hi Michael,
Thanks for the quick reply, I don't have an oscilloscope unfortunately. I
am sure it is connected correctly, and I have traced the cable all the way
through via multimeter continuity testing.
Interestingly, I tried some other sample configs I found and I can get what
looks like a flash cursor every now and then. Also, when changing the
contrast, if I turn it to full, I get the top row blacked out, but only
HALF the second row!?
Totally confused now!
Is there any other way to do a signal test?
Cheers,
Matt
Regards,
Matthew Hodder
Mob: 0422 610 560
On 17 February 2015 at 02:10, Michael Reinelt <mi...@re...> wrote:
> Hello Matthew,
>
> do you have a oscilloscope or something?
>
> I guess either the wiring os wrong, or soemthing is wrong with your
> parport.
>
> are you sure you have the RW line connected properly?
>
> From the warnings in the log, the display does not return the busy-flag
> (which is ok if you don't use busyflag checking), but it may be a hint that
> something is very basically wrong.
>
> checking some of the signals on the parallel port with a oscilloscope
> could help a lot, we don't need deep timing or signal nalysis, just knowing
> that the signal on some pins is "moving"
>
>
>
> regards, Michael
>
>
> Am 2015-02-16 um 11:04 schrieb Matthew Hodder:
>
>> Hi all,
>>
>> Hoping someone can point me in the right direction.
>>
>> I'm running LCD4Linux on a Sophos UTM box (Suse base), I suspect I may
>> have a dud parallel port, but wanted someone
>> elses thoughts.
>>
>> LCD4Linux is compiled with just the HD44870 driver, I'm doing a basic
>> config just to prove I can get a display up on the
>> LCD. I have double/triple checked wiring and I'm sure I have it right.
>>
>> My config file looks like this:
>>
>> ----------------------------------------------------------------
>>
>> Display HD44780-winamp {
>> Driver 'HD44780'
>> Model 'generic'
>> UseBusy 1
>> Port '/dev/parport0'
>> Size '16x2'
>> Wire {
>> RW 'AUTOFD'
>> RS 'INIT'
>> ENABLE 'STROBE'
>> ENABLE2 'GND'
>> GPO 'GND'
>> }
>> }
>>
>>
>> Widget MEM {
>> class 'Text'
>> expression meminfo('MemTotal')/1024
>> prefix 'MB:'
>> width 11
>> align 'L'
>> precision '0'
>> update 1000
>> }
>>
>> Layout Default {
>> Row1 {
>> Col1 'MEM'
>> }
>> }
>>
>> Display 'HD44780-winamp'
>> Layout 'Default'
>>
>> ----------------------------------------------------------------
>>
>> When I run it using: sudo /sbin/lcd4linux -Fvv
>>
>> I get the following:
>>
>> ----------------------------------------------------------------
>>
>> Version 0.11.0-SVN-965 starting
>> lcd4linux.c: initializing driver HD44780
>> HD44780: $Rev: 905 $
>> 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: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: using busy-flag checking
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: timeout waiting for busy flag on controller 1 (0xff)
>> HD44780: too many busy flag failures, turning off busy flag checking.
>> HD44780: using 0 GPI's and 0 GPO's
>> initializing layout 'Default'
>> widget 'MEM': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0
>> lcd4linux.c: starting main loop
>>
>> ----------------------------------------------------------------
>>
>> But nothing ever displays on the LCD. I get the above regardless if the
>> LCD is connected or not, so I simply don't think
>> it is seeing the LCD at all. I have tried two different LCDs as well with
>> the same result
>>
>> Any pointers from here or how I can trouble shoot further?
>>
>> Thanks in advance!
>>
>> Regards,
>> Matt Hodder
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&
>> iu=/4140/ostg.clktrk
>>
>>
>>
>> _______________________________________________
>> 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
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X