lcd4linux-devel — lcd4linux development team

Re: [Lcd4linux-devel] [lcd4linux] Improvement ideas for Project accessibility [WAS: Re: lcd4linux - My message to the devel-list]

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

Hi,

> I have personal issues with GMANE, all of them SPAM related. 
> 
> Therefore I will only accept it if my (or all) email addresses are concealed
> from  the GMANE public archive.

ok, good point, I fully agree.

from what I remember GMANE does provide something like "address hiding".

@Robert: Could you please double-check that?


TIA, Michael

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

Re: [Lcd4linux-devel] [lcd4linux] Where do i add lcdserializer support?

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

Hi Errol,

> I want to try and add support for the lcdserializer.
> 
> It is a normal HD44780 connected through a PIC to a serial port at 9600 baud. 
> 
> All data sent to the PIC is relayed to the LCD as data, except if preceded by 0xFE, in which case the following char is sent as a command.
> 
> Now, my question:
> 
> Should I add this as a new driver, or add another bus to the HD44780 driver?

I'd recommend using a new driver, at least as a starting point. The
HD44780 driver is already complicated enough... there are already some
drivers (usb2anything) that drive a HD44780 via USB.


bye, Michael

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

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

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

Hi Michael,

> -----Original Message-----
> From: lcd...@li... 
> [mailto:lcd...@li...] On 
> Behalf Of Michael Reinelt
> Sent: Monday, January 15, 2007 9:29 PM
> Cc: lcd4linux-devel
> Subject: Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.
> 
> Hi Luis,
> 
> > I plan to put myself back into lcd4linux development, to finally 
> > finish the HD44780-I2C driver, if you split it into it's 
> own file, it 
> > would surely make things better :)
> 
> Oh, I don't plan to duplicate the whole HD44780 driver, but 
> only the driver entry in drivers.m4, so one can select 
> "--with-drivers=HD44780-I2C" and don't get the parport stuff 
> linked in (ifdef'ed out by #ifdef WITH_PARPORT or something)
> 
> OTOH, if you like to have your 'own' driver, we could do so; 
> but they would share some common code... maybe we could 
> backport your changes later... just let me know what you prefer.

what I had in mind was something even less stressfull but maybe hard
to make. and it is split the HD44780 driver even further so that
the actual 'bus' connection is fully separated from the HD44780 core.

which would make things like supporting different connections even simpler

from memory there are some major HD44780 connections:

-parport
-i2c
-serial-to-paralell (obsolete by now)
-gpio (from Martin Hejl's, although it uses a parport emulation)
-some other that I can't recall

> 
> 
> > p.s. no need to CC me
> sorry... got used to hit "reply all" :-)
> 

eheh
 

> bye, Michael
> 

Luis Correia

Re: [Lcd4linux-devel] Improvement ideas for Project accessibility [WAS: Re: lcd4linux - My message to the devel-list]

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

Hi there,

I have personal issues with GMANE, all of them SPAM related. 

Therefore I will only accept it if my (or all) email addresses are concealed
from 
the GMANE public archive.

Thank you and sorry for the inconvenience.

Luis Correia


> -----Original Message-----
> From: lcd...@li... 
> [mailto:lcd...@li...] On 
> Behalf Of Michael Reinelt
> Sent: Tuesday, January 16, 2007 8:21 AM
> To: lcd4linux-users
> Cc: lcd4linux-devel
> Subject: Re: [Lcd4linux-devel] Improvement ideas for Project 
> accessibility [WAS: Re: lcd4linux - My message to the devel-list]
> 
> Hi Robert,
> 
> > Maybe I missed the reply, but what about the two ideas I 
> uttered here?
> No, I think I missed your post...
> 
> >> Currently, I cannot see the mail messages at sourceforge.
> Well, I think ther *is* a mailing list archive at SF...
> 
> >> Maybe it would be a good idea to also use an alternative archiving 
> >> service. There's a great one for archiving open source 
> mailing lists 
> >> and viewing them, called GMANE, I am sure you heard about it.
> No, I have not.
> 
> But I think this is a good idea!
> 
> At the moment the mailing list is the only important thing 
> hosted at SourceForge, which I want to get rid of, too (the 
> hosting, not the mailing lists)
> 
> For the moment it would be great if you could set up the list 
> archive at gmane, and probably even import the archives from 
> sourceforge (I read something there that such an import 
> should be possible).
> 
> 
> bye, Michael
> 
> --
> Michael Reinelt <re...@eu...>
> http://home.pages.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781
> 
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT Join 
> SourceForge.net's Techsay panel and you'll get the chance to 
> share your opinions on IT & business topics through brief 
> surveys - and earn cash 
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
> &CID=DEVDEV
> _______________________________________________
> Lcd4linux-devel mailing list
> Lcd...@li...
> https://lists.sourceforge.net/lists/listinfo/lcd4linux-devel
> 

Re: [Lcd4linux-devel] [PATCH] Fix compilation of plugin_wireless.c with linux kernel 2.6.19

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

FoX schrieb:
> Here is a patch that does $subject.
> 
> Comments are welcome.

Applied. (a bit late, I know...)

Thanks for contributing!


bye, Michael

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

Re: [Lcd4linux-devel] Improvement ideas for Project accessibility [WAS: Re: lcd4linux - My message to the devel-list]

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

Hi Robert,

> Maybe I missed the reply, but what about the two ideas I uttered here?
No, I think I missed your post...

>> Currently, I cannot see the mail messages at sourceforge.
Well, I think ther *is* a mailing list archive at SF...

>> Maybe it would be a good idea to also use an alternative archiving
>> service. There's a great one for archiving open source mailing lists and
>> viewing them, called GMANE, I am sure you heard about it.
No, I have not.

But I think this is a good idea!

At the moment the mailing list is the only important thing hosted at
SourceForge, which I want to get rid of, too (the hosting, not the
mailing lists)

For the moment it would be great if you could set up the list archive at
gmane, and probably even import the archives from sourceforge (I read
something there that such an import should be possible).


bye, Michael

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

Re: [Lcd4linux-devel] Error when building only with NULL driver

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

Hi Robert,

> Apparantly, it is missing to build and link the "drv_generic_text.c"
> here. Adding TEXT="yes" helps to the driver helps here.
> 
> Also, the build system does not include all actual m4 files here, so
> rebuilding the configure won't work with the release sources.
> 
> The attached patch should fix both these issues.

Committed. Thanks for contributing!

> Michael, did you think about releasing a new version of the software, as
> the supported devices list has grown impressively since 0.10.0?

Yes, I always think about releasing :-)

As it's been very quiet here the last months, I want to wait a few days
to allow things to calm down a bit, and then I will release 0.11

Please remind me if a forget again :-)


bye, Michael

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

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

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

Robert Buchholz wrote:
> Michael Reinelt wrote:
>>> I plan to put myself back into lcd4linux development, to finally finish 
>>> the HD44780-I2C driver, if you split it into it's own file, it would 
>>> surely make things better :)
>> Oh, I don't plan to duplicate the whole HD44780 driver, but only the
>> driver entry in drivers.m4, so one can select
>> "--with-drivers=HD44780-I2C" and don't get the parport stuff linked in
>> (ifdef'ed out by #ifdef WITH_PARPORT or something)
> 
> Will this disable the possibility to compile both drivers at the same time?

Yes and no :-)

The "normal" HD44780 driver will contain both parport and i2c stuff, but
the new "HD44780-I2C" driver will contain i2c *only*.

Default behaviour (--with-drivers=all) will compile the standard HD44780
driver with i2c support.

Note that there's no seperate HD44780 driver, nor a 2nd drv_HD44780.c
driver source.

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

[Lcd4linux-devel] Error when building only with NULL driver

[Robert B. <rb...@ge...>]

Hi *,

in 0.10.0 I get the following error when building only with the NULL driver:

./configure --prefix=/usr --host=i686-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --sysconfdir=/etc/lcd4linux
--with-drivers=NULL --with-plugins=all,!mysql,!python --without-python
--without-x --build=i686-pc-linux-gnu
...

i686-pc-linux-gnu-gcc -D_GNU_SOURCE -Wall -W -march=athlon-xp -O2 -pipe
 -o lcd4linux  lcd4linux.o cfg.o debug.o drv.o evaluator.o hash.o
layout.o pid.o timer.o thread.o udelay.o qprintf.o widget.o
widget_text.o widget_bar.o widget_icon.o plugin.o plugin_cfg.o
plugin_math.o plugin_string.o plugin_test.o plugin_time.o drv_NULL.o
plugin_apm.o plugin_cpuinfo.o plugin_diskstats.o plugin_dvb.o
plugin_exec.o plugin_i2c_sensors.o plugin_imon.o plugin_isdn.o
plugin_loadavg.o plugin_meminfo.o plugin_netdev.o plugin_pop3.o
plugin_ppp.o plugin_proc_stat.o plugin_seti.o plugin_statfs.o
plugin_uname.o plugin_uptime.o plugin_wireless.o plugin_xmms.o   -lm
drv_NULL.o: In function `drv_NULL_quit':
drv_NULL.c:(.text+0x43): undefined reference to `drv_generic_text_quit'

Apparantly, it is missing to build and link the "drv_generic_text.c"
here. Adding TEXT="yes" helps to the driver helps here.

Also, the build system does not include all actual m4 files here, so
rebuilding the configure won't work with the release sources.

The attached patch should fix both these issues.

Michael, did you think about releasing a new version of the software, as
the supported devices list has grown impressively since 0.10.0?

Bye,

Robert

Re: [Lcd4linux-devel] Improvement ideas for Project accessibility [WAS: Re: lcd4linux - My message to the devel-list]

[Robert B. <rb...@ge...>]

Hi,

nice to see some activity on the list again.

Maybe I missed the reply, but what about the two ideas I uttered here?
(see below).

Thanks a lot,

Robert

Robert Buchholz wrote:
> 1. Who can post to the mailing list?
>=20
> Michael Reinelt schrieb:
>>> On a side note, don't you think it would be a good idea to close the
>>> list for non-subscribers, that would stop the big amount of spam comi=
ng
>>> over it.
>> Hmmm.... I think this is the same question as with the wiki: I think i=
f
>> I close it, there will be far less traffic (it's already (too) low
>> traffic I think)
>>
>> Speaking for myself, if I want to report a bug or something similar to=
 a
>> project, and I need to be subscribed, I wont. But as always, YMMV.
>=20
> But is the mailing list the right place for this?
> First, there are trackers at sourceforge and at bublix.org which are
> much easier for reporting and handling bugs that a mailing list.
> Second, you don't get the replies to the list-report if you are not
> subscribed.
>=20
>=20
> 2. Mailing list archive
>=20
> Currently, I cannot see the mail messages at sourceforge.
> Maybe it would be a good idea to also use an alternative archiving
> service. There's a great one for archiving open source mailing lists an=
d
> viewing them, called GMANE, I am sure you heard about it.
>=20
> You can publish the mailing list at gmane using
> http://gmane.org/subscribe.php
>=20
> As group name, you could use gmane.comp.sysutils.lcd4linux. That would
> be on the same name hierarchy as lcdproc, or some other sub-name of
> gmane.comp.
>=20
> Example Views:
>  * List page: http://dir.gmane.org/gmane.linux.gentoo.devel
>  * Frame view: http://news.gmane.org/gmane.linux.gentoo.devel

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

[Robert B. <rb...@ge...>]

Michael Reinelt wrote:
>> I plan to put myself back into lcd4linux development, to finally finis=
h=20
>> the HD44780-I2C driver, if you split it into it's own file, it would=20
>> surely make things better :)
>=20
> Oh, I don't plan to duplicate the whole HD44780 driver, but only the
> driver entry in drivers.m4, so one can select
> "--with-drivers=3DHD44780-I2C" and don't get the parport stuff linked i=
n
> (ifdef'ed out by #ifdef WITH_PARPORT or something)

Will this disable the possibility to compile both drivers at the same tim=
e?

Regards,
Robert

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

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

Hi Luis,

> I plan to put myself back into lcd4linux development, to finally finish 
> the HD44780-I2C driver, if you split it into it's own file, it would 
> surely make things better :)

Oh, I don't plan to duplicate the whole HD44780 driver, but only the
driver entry in drivers.m4, so one can select
"--with-drivers=HD44780-I2C" and don't get the parport stuff linked in
(ifdef'ed out by #ifdef WITH_PARPORT or something)

OTOH, if you like to have your 'own' driver, we could do so; but they
would share some common code... maybe we could backport your changes
later... just let me know what you prefer.


> p.s. no need to CC me
sorry... got used to hit "reply all" :-)


bye, Michael

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

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

[Luis C. <lfc...@lf...>]

Michael Reinelt wrote:
> Hi Luis,
>
>   
>>> I can help debugging this one, as I half wrote the first implementation.
>>>       
> Great!
>
> Did you already switch to SVN? :-)
>
>   
I did a test checkout yesterday, but no compile tests were done

>>> Have you checked the way we have done it?
>>>       
> Sorry, I don't know what you mean... I thinke the OP's problem is that
> he does not want any parport stuff get compiled/linked.
>
>   
I meant the way we talked to the PCF chip, and the question was meant 
for the uClinux developer, not you, sorry for the confusion.

I plan to put myself back into lcd4linux development, to finally finish 
the HD44780-I2C driver, if you split it into it's own file, it would 
surely make things better :)

Luis

p.s. no need to CC me



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

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

Hi Luis,

>> I can help debugging this one, as I half wrote the first implementation.
Great!

Did you already switch to SVN? :-)

>> Have you checked the way we have done it?
Sorry, I don't know what you mean... I thinke the OP's problem is that
he does not want any parport stuff get compiled/linked.


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

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

[Luis C. <lfc...@lf...>]

Luis Correia wrote:
> Michael Reinelt wrote:
>> Hi Hans,
>>
>>  
>>> Im involved in a project running related to running systems 
>>> onuClinux on Blackfin. Recently i got the task to implement the 
>>> hardware and software needed for a HD44780 LCD via I2C for the 
>>> blackfin. Doing that i got the ide to try to port either lcdproc or 
>>> lcd4linux. Lcdproc failed on some shared library build(may persue 
>>> that later) but i made a successful build of lcd4linux and i have 
>>> also made a uClinux patch for HD44780 over i2c(via pfc8574). Has 
>>> this been done? Tried to search for any other LCD-uClinux projects 
>>> but with no luck. Instructions on how to set it up, and also notes 
>>> on the patch at:
>>>
>>> http://www.vpx.nu/dokuwiki/doku.php?id=displays
>>>     
>>
>> Look nice!
>>
>>  
>>> Also, note that i did(in function rep_nop for the delays)
>>> -    __asm__ __volatile__("rep; nop");
>>> +    __asm__ __volatile__("nop");
>>>
>>> since i think rep is IA32 specific. Dont know if this is a good 
>>> final solution for all platforms.
>>>     
>> This has already been fixed in CVS/SVN.
>>
>>  
>>> Im sure some developer can use the patch and incorporate it to a 
>>> future release in a sweet mannner, a configure switch of 
>>> --with-uclinux would be nice:). Im not a make guru so i did not do 
>>> it so fancy. Hope anyone else can try it out on their embedded system.
>>>     
>>
>> I had a look at your patch. I can't accept it as it is, because it would
>> cause lots of problems with people needing the parpott driver :-(
>>
>> But I got another idea: I will duplicate the HD44780 driver entry in
>> drivers.m4, providing kind of a "sub-driver" called "HD44780-I2C", which
>>  doesnt use parport at all.
>>   
>
> I can help debugging this one, as I half wrote the first implementation.
>
> Have you checked the way we have done it?
>
>> Are you willing to do some testing? You would have to use the SVN 
>> version...
>>
>> Another question: Why did you use vfork()? From what I've read in the
>> manpage, this is dangerous....
>>
>>
>> bye, Michael
>>
>>   
>
> Luis
>
Sorry, the first one got caught in some spam filter, don't know why...



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Lcd4linux-devel] [lcd4linux] uClinux patch.

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

Hi Hans,

> Im involved in a project running related to running systems onuClinux on 
> Blackfin. Recently i got the task to implement the hardware and software 
> needed for a HD44780 LCD via I2C for the blackfin. Doing that i got the ide 
> to try to port either lcdproc or lcd4linux. Lcdproc failed on some shared 
> library build(may persue that later) but i made a successful build of 
> lcd4linux and i have also made a uClinux patch for HD44780 over i2c(via 
> pfc8574). Has this been done? Tried to search for any other LCD-uClinux 
> projects but with no luck. Instructions on how to set it up, and also notes 
> on the patch at:
> 
> http://www.vpx.nu/dokuwiki/doku.php?id=displays

Look nice!

> Also, note that i did(in function rep_nop for the delays)
> -    __asm__ __volatile__("rep; nop");
> +    __asm__ __volatile__("nop");
> 
> since i think rep is IA32 specific. Dont know if this is a good final solution 
> for all platforms.
This has already been fixed in CVS/SVN.

> Im sure some developer can use the patch and incorporate it to a future 
> release in a sweet mannner, a configure switch of --with-uclinux would be 
> nice:). Im not a make guru so i did not do it so fancy. Hope anyone else can 
> try it out on their embedded system.

I had a look at your patch. I can't accept it as it is, because it would
cause lots of problems with people needing the parpott driver :-(

But I got another idea: I will duplicate the HD44780 driver entry in
drivers.m4, providing kind of a "sub-driver" called "HD44780-I2C", which
 doesnt use parport at all.

Are you willing to do some testing? You would have to use the SVN version...

Another question: Why did you use vfork()? From what I've read in the
manpage, this is dangerous....


bye, Michael

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

[Lcd4linux-devel] switch to subversion

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

Hi there,

today I finalized the migration from CVS at SourceForge to Subversion
managed by Trac.

Have a look at the "Source Browser" and "Timeline" and enjoy!

To prevent further modifications to the CVS repository, I removed all
developers from the SF project.


Accessing the subversion repository is *very* easy, I think it's even
easier than it was with CVS.

First, you need a subversion client. I'm sure *every* distribution
provides one...

To initially checkout the repo, use the following command:

svn co https://ssl.bulix.org/svn/lcd4linux/trunk lcd4linux

this should create a local directory 'lcd4linux', containing the 'trunk'
of the repository (development will focus on the trunk; branches and
tags are empty at the moment). No Login is necessary!

to update your local repository, use the following:

svn up

(within the lcd4linux directory!)

to check the status of your repo:

svn stat
svn stat -u

to create a patch, just use

svn diff


If you want write access to the repo (and I'd *really* appreciate active
development), please send me and/or Sam a mail to get write access to
the repository (which is easy, too)

If you have any questions, feel free to ask me!


Finally, I really hope that I can find much more time for development in
the future! I'm very sorry that I didn't even answer emails is the past....



bye, Michael

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

Re: [Lcd4linux-devel] PicoLCD from Mini-Box/Ituner

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

Hi Greg,

> From which I've been able to get a driver up and running in basic
> form. =20

How did you implement the driver? Did you use the SDK, or did you use
direct libusb calls?

> Unfortunately there doesn't seem to be anything (obvious) that
> would allow user defined characters on the fly.  They offer the
> capacity to install up to 10 custom characters via a text file, but
> they don't tell you how to use those characters once installed.
I did a quick glance over the SDK sources, and I'=C4ve seen all the stuff
I'd need. And it looks quite simple. The protocol they use is similar to
stuff I've done already.

I suppose the display itself is a standard HD44780, and they just built
an interface around it...

> This results in no icons and no bar segments ... well, there are bar
> segments, but it's all garbage characters (even flipping the
> ascii255bug on and off).
Not havind bars and icons would be a Bad Thing (TM) :-)

> For what it's worth, after talking to Nico Pavel (the developer at
> ituner.com), it seems like they, too, are working on a lcd4linux
> driver but it may not be released for a little while yet.
As I said, writing a driver should be easy. But writing it "blind"
(without a display to test) may be complicated.

As I really like the cute pictures of the display, I'm thinking about
ordering one. But shipping and customs may be expensive to Austria....
(maybe they want to donate a "development sample"? :-)


bye, Michael

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

Re: [Lcd4linux-devel] PicoLCD from Mini-Box/Ituner

[gcombs <gc...@gm...>]

I've found some rudimentary SDK instructions:

http://resources.mini-box.com/online/picoLCD%2020x2%20(OEM)/Documentation/libusblcd-development-guide.txt

>From which I've been able to get a driver up and running in basic
form.  Unfortunately there doesn't seem to be anything (obvious) that
would allow user defined characters on the fly.  They offer the
capacity to install up to 10 custom characters via a text file, but
they don't tell you how to use those characters once installed.

This results in no icons and no bar segments ... well, there are bar
segments, but it's all garbage characters (even flipping the
ascii255bug on and off).

Here's the SDK download:

http://resources.mini-box.com/online/picoLCD%2020x2%20(OEM)/Software/Linux/SDKSource/usblcd-src-0.1.4.tgz

For what it's worth, after talking to Nico Pavel (the developer at
ituner.com), it seems like they, too, are working on a lcd4linux
driver but it may not be released for a little while yet.

g


On 1/11/07, Michael Reinelt <re...@eu...> wrote:
> Hi Greg,
>
> > In examining drv_USBLCD.c, I notice the vendor and product id's don't match.
>
> > P:  Vendor=04d8 ProdID=0002 Rev= 0.01
> > S:  Manufacturer=ITUNER INC
> > S:  Product=USB-LCD-20x2
>
> Well, I think this is *not* the USBLCD from Adams IT Services. Robin
> used two different Vendor ID's, the old (inoffical) 0x10D2 and the new
> (official) 0x1212 (maybe I swapped these two).
>
> The problem may be that "USBLCD" is a very misleading name, everyone who
> designs such a beast will call it USBLCD, regardless of being compatible
> to whatever.
>
> Can you get a datasheet or something? From my experience, it should be
> easy to write a new (or adopt an existing) driver...
>
>
> HTH, Michael
>
> --
> Michael Reinelt <re...@eu...>
> http://home.pages.at/reinelt
> GPG-Key 0xDF13BA50
> ICQ #288386781
>

Re: [Lcd4linux-devel] PicoLCD from Mini-Box/Ituner

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

Hi Greg,

> In examining drv_USBLCD.c, I notice the vendor and product id's don't match.

> P:  Vendor=04d8 ProdID=0002 Rev= 0.01
> S:  Manufacturer=ITUNER INC
> S:  Product=USB-LCD-20x2

Well, I think this is *not* the USBLCD from Adams IT Services. Robin
used two different Vendor ID's, the old (inoffical) 0x10D2 and the new
(official) 0x1212 (maybe I swapped these two).

The problem may be that "USBLCD" is a very misleading name, everyone who
designs such a beast will call it USBLCD, regardless of being compatible
to whatever.

Can you get a datasheet or something? From my experience, it should be
easy to write a new (or adopt an existing) driver...


HTH, Michael

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

[Lcd4linux-devel] PicoLCD from Mini-Box/Ituner

[gcombs <gc...@gm...>]

I recently picked up a mini-itx case from Mini-Box.com (aka iTuner).
It's got a USBLCD 20x2 in it.

iTuner supplies what looks like an old version of usblcd command line
app.  It works fine, but I'd definitely like to get lcd4linux running
on it.

My first attempt was just to enable the USBLCD driver ... however when
scanning for usblcd devices, the driver complained that it couldn't
find any.

In examining drv_USBLCD.c, I notice the vendor and product id's don't match.

Here's what the /proc/bus/usb/devices said:

T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=04d8 ProdID=0002 Rev= 0.01
S:  Manufacturer=ITUNER INC
S:  Product=USB-LCD-20x2
S:  SerialNumber=1.57rel.
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=  24 Ivl=1ms
E:  Ad=01(O) Atr=03(Int.) MxPS=  24 Ivl=10ms


So in drv_USBLCD.c, I add the vender (0x04d8) and the product ID
(0x0002), recompile and run with -Fvv

It looks like it's running, in that lcd4linux doesn't complain about
anything, however there's no change in the actual LCD.

Am I just using the wrong driver or what?

Greg

Re: [Lcd4linux-devel] 2 displays

[Andreas <An...@t-...>]

Hey All...

I'll try to translate...

Andreas asked:
--------------------------------------------------------------
Hello,

is it possible to drive 2 displays on a fli4l-router (this one
is using lcd4linux for the display feature).
The 2 Displays are one USBLCD and one CTINCLUD.

I would like to show the openvpn users on the usblcd.

Hopefully, someone could help. Sorry for asking in german, cause
my english is'nt the best.

Regards,
Andreas Winkler
---------------------------------------------------------------

Hope that helps for helping (cause i got no idea what's ctinclud)! :)

Regards,
(another) Andreas..

>Luis wrote:
>
>Hi,
>> Andreas wrote:
>>
>> Hallo,
>> ist es möglich und wenn ja dann wie kann ich 2 Displays an
>> einem fli4l betreiben?
>> 1. Display ein USBLCD
>> 2. Display ein CTINCLUD
>> (...)
> mit freundlichen Grüßen,
> Andreas Winkler
>
>English please.
>
>Luis

Non-US residents’ delivery dead-line is weeks

[john p. <gle...@nt...>]

<HTML>
<BODY>
<a href="http://ploroves.com/">Trouble free software to be the best in work</a>

</BODY>
</HTML>

[Lcd4linux-devel] Download notification

[Today: <bev...@sh...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3D"GENERATOR">
</HEAD>
<BODY>
<FONT face=3DArial><FONT size=3D2>
<DIV>Michael says: <STRONG>GCME Huge News Release Expected Before Years =
End!=20
</STRONG></DIV>
<DIV><STRONG></STRONG>&nbsp;</DIV>
<DIV><STRONG>Ring In The New Year With Cash!</STRONG></DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV><STRONG>GCME</STRONG> is fast becoming a major player in the =
foreign film=20
market. With continuing mergers and joint ventures with the industries =
most=20
influential corporations.</DIV>
<DIV>&nbsp;</DIV></DIV>
<DIV><STRONG>Company:</STRONG> Greater China Media &amp; Entertainment=20
Corp.<BR>Symbol: <STRONG>GCME</STRONG><BR><STRONG>Price:</STRONG>=20
$0.70<BR>Status: <STRONG>BUY ALERT</STRONG><BR><STRONG>5 Day =
Target:</STRONG>=20
$1.45</DIV>
<DIV>&nbsp;</DIV>
<DIV><STRONG>Right now</STRONG> it is at $0.70. We have seen consistent =
price=20
jumps following <STRONG>news releases</STRONG> and we have been told to=20
<STRONG>expect big news</STRONG> before the end of the year. Look at the =
price=20
patterns, see the spikes and the steady climb for yourself. <U>Now is =
the time,=20
grab GCME first thing <STRONG>Tuesday</STRONG>=20
Morning</U>.</DIV></FONT></FONT></BODY></HTML>

[Lcd4linux-devel] =?iso-2022-jp?b?GyRCIighIUxARnwkXiRHGyhC?=

[<pan...@ya...>]

lcd...@li...様へ、招待期限になりましたのでご確認下さい。
至急、下記の招待カードからアクセスしていただき、
準備したおります専用スペースへ入室お願いします。

 >>>  招待カード  :::: 明日期限 ::::

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
【No.20024】瑞穂様から
┌──┐
│＼／│　　ご招待カードを開封する
　　　　　http://www.now-on-site.com/acfree/20024

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ずべて無料の自由恋愛コミュニティは、健全セフレの募集板です。