From fblack947 at yahoo.com  Mon Jun  1 13:44:48 2009
From: fblack947 at yahoo.com (jk)
Date: Mon, 1 Jun 2009 06:44:48 -0700 (PDT)
Subject: [Lcdproc] Removing LCDProc's scripts/debian
In-Reply-To: <200905302029.40525.rbu@gentoo.org>
References: <4A2163F7.2090301@nurfuerspam.de>
	<200905302029.40525.rbu@gentoo.org>
Message-ID: <57651.50299.qm@web37502.mail.mud.yahoo.com>


Markus,




----- Original Message ----
> From: Robert Buchholz <rbu at gentoo.org>
> Sent: Saturday, May 30, 2009 2:29:37 PM
> Subject: Re: [Lcdproc] Removing LCDProc's scripts/debian
> 
> Hi Markus,
> 
> On Saturday 30 May 2009, Markus Dolze wrote:
> > for the upcoming release of LCDproc 0.5.3 I am about to remove the
> > scripts/debian directory.
> >
> > This directory contains Debian specific files for building a package.
> > I have not received feedback from Jose Luis and Robert for one week
> > and have no idea what to put into these files.
> 
> I have received the CC of an email by Jos? Luis Tall?n last week, and he 
> agreed to have the files removed. We don't use anything in scripts/* 
> either.
> 
> 
> 
> Robert

The quick feedback I received is that the scripts/init-LCDd.debian file is very important, but not the debian subdirectory.

-Jonathan K.


      

From TELarson at west.com  Thu Jun  4 22:07:46 2009
From: TELarson at west.com (Larson, Timothy E.)
Date: Thu, 4 Jun 2009 17:07:46 -0500
Subject: [Lcdproc] Call for testers: getopt for clients
In-Reply-To: <226316B3E1F749498E28ACA66321D5BA2542B1D7@oma00cexmbx03.corp.westworlds.com>
References: <20090521191414.111280@gmx.net>
	<226316B3E1F749498E28ACA66321D5BA2542B1D7@oma00cexmbx03.corp.westworlds.com>
Message-ID: <226316B3E1F749498E28ACA66321D5BA2AD5E18E@oma00cexmbx03.corp.westworlds.com>

> For Solaris, this patch worked fine (albeit building without the
> mtc_s16209x driver) after one small change - making inclusion of
> stdint.h conditional.

Is this patch going to be pulled up to the various branches?


Tim

From willu.mailingLists at cse.unsw.edu.au  Sat Jun  6 08:06:17 2009
From: willu.mailingLists at cse.unsw.edu.au (William Uther)
Date: Sat, 6 Jun 2009 18:06:17 +1000
Subject: [Lcdproc] [patch] imonlcd backlight option
Message-ID: <0DD2359C-C044-40BF-B696-D9F5D50E0FDB@cse.unsw.edu.au>

Hi all,

   Just joined the mailing list to suggest this small change  
(hopefully before the next release?).  The imonlcd driver recently  
added has a return statement at the front of the imonlcd_backlight()  
function stopping it from doing anything.  The comment in front of it  
reads:

         /*
          * TODO: For some reason, lcdproc keeps calling this and  
flipping the
          * 'on' so you end up flashing the backlight for no  
particular reason
          * (and on my Antec, turning the backlight off, turns the  
whole thing
          * off, so it's really bad...)
          */
	return;

I wanted to turn off my backlight, so I removed that return statement  
to let the function work.  It seems to work just fine for me.  When  
the backlight is off the whole display turns off, but turns back on  
when you turn the backlight back on.  I've been using it that way for  
at least 6 months.

I thought it must have been turned off for a reason however, so rather  
than just remove it I thought it would be better to add an option to  
switch it off.  I'd really like to understand why the return statement  
was originally added.

Anyway, the patch below is pretty self-explanatory.

Be well,

Will          :-}


-------------- next part --------------
A non-text attachment was scrubbed...
Name: lcdproc-imon-backlight.diff
Type: application/octet-stream
Size: 566 bytes
Desc: not available
URL: <http://lists.omnipotent.net/pipermail/lcdproc/attachments/20090606/adbc1f10/attachment.obj>
-------------- next part --------------




From bsdfan at nurfuerspam.de  Sat Jun  6 15:40:20 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Sat, 06 Jun 2009 17:40:20 +0200
Subject: [Lcdproc] [PATCH] Missing NULL malloc() check
	in	server/menuitem.c
In-Reply-To: <4A210CE3.4020708@nurfuerspam.de>
References: <BC238BC5-A298-4350-B643-C3EAEAA060A5@siliconlandmark.com>	<4A19CD03.6050400@nurfuerspam.de>	<6149728D-A454-4F1E-AD43-77200A762A06@siliconlandmark.com>
	<4A210CE3.4020708@nurfuerspam.de>
Message-ID: <4A2A8DE4.90908@nurfuerspam.de>

Markus Dolze wrote:
> Andre Guibert de Bruet wrote:
>>
>> I have addressed a bunch of malloc-related issues this source file in
>> the attached patch (Against HEAD). I have a list of additional issues
>> with menuitem.c which I will address at a later date.
>>
>> Could the attached patch be committed upon review?
>>
>
> Hi,
>
>
> I had a look at your patch and the menu* part. It is perhaps one of
> the most complex part of LCDproc.
>
> Tracing from menuitem_create to all more specific menuitem_create_*()
> functions and the calling functions I was puzzled by the result
> handling and rewrote parts of it. Patch is attached.
>
> Some remarks:
>
> 1. All calls to malloc are checked for NULL now (based on
> Andre's          patch).
> 2. All calls to strdup are checked as well, because subsequent calls to
>    strlen(NULL) will result in core dump.
> 3. It is not necessary to free allocated memory and duplicates string in
>    menuitem_create_*() IF menuitem_destroy() is called (the latter frees
>    all allocated strings). However, I am not sure if I need to
>    initialize all pointer to NULL before.
> 4. All calls to menu_create() are checked for NULL, exiting the current
>    function in most cases.
> 5. I moved the creation of the test menu into its own function (as a
>    result of 3).

I committed all ot these to cvs HEAD.

Merge to: stable-0-5-x: pending
Merge to: lcdproc-0-5-3: pending

Regards,
Markus

From bsdfan at nurfuerspam.de  Sat Jun  6 16:04:35 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Sat, 06 Jun 2009 18:04:35 +0200
Subject: [Lcdproc] Call for testers: getopt for clients
In-Reply-To: <226316B3E1F749498E28ACA66321D5BA2AD5E18E@oma00cexmbx03.corp.westworlds.com>
References: <20090521191414.111280@gmx.net>	<226316B3E1F749498E28ACA66321D5BA2542B1D7@oma00cexmbx03.corp.westworlds.com>
	<226316B3E1F749498E28ACA66321D5BA2AD5E18E@oma00cexmbx03.corp.westworlds.com>
Message-ID: <4A2A9393.3010009@nurfuerspam.de>

Larson, Timothy E. wrote:
>> For Solaris, this patch worked fine (albeit building without the
>> mtc_s16209x driver) after one small change - making inclusion of
>> stdint.h conditional.
>>     
>
> Is this patch going to be pulled up to the various branches?
>
>   

Two weeks have passed and I received no feedback about other platforms
at all. Therefore I changed my mind and committed this to cvs HEAD
without waiting any longer.

Merge to: stable-0-5-x: pending
Merge to: lcdproc-0-5-3: pending

Regards,
Markus


From bsdfan at nurfuerspam.de  Sun Jun  7 16:40:44 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Sun, 07 Jun 2009 18:40:44 +0200
Subject: [Lcdproc] LCDproc 0.5.3-pre1 available
Message-ID: <4A2BED8C.8080300@nurfuerspam.de>

Hello everyone!

for the last two weeks not much work has been done on the release,
mainly because I had a lot of other work to do.

Today I merged the changes that have been committed to cvs HEAD during
the last weels to the release branch and created the first release
candidate named '0.5.3-pre1' and made it available on Sourceforge for
immediate download.

Please give it a try and report any regressions found. For the next days
I will be busy again, but I want to create the final release in about
two weeks from now on.

Have fun!

Regards,
Markus



From bsdfan at nurfuerspam.de  Sun Jun  7 16:44:27 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Sun, 07 Jun 2009 18:44:27 +0200
Subject: [Lcdproc] Removing LCDProc's scripts/debian
In-Reply-To: <4A2163F7.2090301@nurfuerspam.de>
References: <4A2163F7.2090301@nurfuerspam.de>
Message-ID: <4A2BEE6B.90508@nurfuerspam.de>

Markus Dolze wrote:
> Hi Everyone,
>
> for the upcoming release of LCDproc 0.5.3 I am about to remove the
> scripts/debian directory.
>
> This directory contains Debian specific files for building a package.
> I have not received feedback from Jose Luis and Robert for one week
> and have no idea what to put into these files.
>
> Anyway, the maintainers have their own patch set for Debian so I guess
> not having these files is no problem.

Hi there,

I have decided to go on like this:

   1. The just made available Release Candidates still includes
      scripts/debian/*. You may have a look at these files to check for
      changes that may be necessary.
   2. The final release tarball will *not* include scripts/debian/*, but
      only scripts/*. However, the files will remain in CVS.

Regards,
Markus


From willu.mailingLists at cse.unsw.edu.au  Mon Jun  8 06:39:12 2009
From: willu.mailingLists at cse.unsw.edu.au (William Uther)
Date: Mon, 8 Jun 2009 16:39:12 +1000
Subject: [Lcdproc] imonlcd patch and mythtv
Message-ID: <4730D478-8EB6-4BCC-913C-CEDE5E6EDE3D@cse.unsw.edu.au>

Hi all,

   I'm running a mythtv box on Ubuntu with an Antec Fusion case.  I've  
had to do a bit of patching to get it all going and I've just recently  
started trying to get all the patches (mostly not mine) committed and  
released so that they can make it into Ubuntu Karmic.  That's the  
context for the patch I sent to this mailing list a few days ago  
commenting out a return statement.

   I haven't actually been running lcdproc 0.5.3.  Rather I've been  
running 0.5.2 with the imonlcd drivers added.  (I'm also running the  
standard ubuntu mythtv 0.21-fixes.)  With that setup the patch I  
submitted works well.  When the backlight is switched off, the display  
turns off and everything is good.

   With the imminent release of lcdproc 0.5.3 I thought I should test  
CVS head.  As is known, it fails with mythtv 0.21-fixes.  So I patched  
my mythtv with this patch http://svn.mythtv.org/trac/changeset/20559  
which is the supposed fix.  With that patch, lcdproc head seemed to  
mostly work, except for one thing - now the lcd display was flashing  
with about a 5 second interval.

   This seems to describe exactly the behaviour that lead to the  
return statement being added in the imonlcd driver.

In summary:

Mythtv           lcdproc         imonlcd-patch      Result

0.21-unpatched   0.5.2+imonlcd   return removed     Works well -  
backlight dims appropriately
0.21-unpatched   head            either             known to fail
0.21-patched     head            return left in     lcd backlight  
never dims
0.21-patched     head            return removed     lcd flashes with  
about 5 second period

It seems that the flashing behaviour that the 'return' was added to  
fix could be a regression in the interaction of mythtv and lcdproc  
head.  Has anyone else, with a different lcd that allows backlight  
dimming, seen this interaction between mythtv and lcdproc?

Cheers,

Will       :-}


From willu.mailingLists at cse.unsw.edu.au  Mon Jun  8 08:52:41 2009
From: willu.mailingLists at cse.unsw.edu.au (William Uther)
Date: Mon, 8 Jun 2009 18:52:41 +1000
Subject: [Lcdproc] Flashing screen fixed...
Message-ID: <4FA87A53-9579-489C-88DD-47557BCD61DE@cse.unsw.edu.au>

Hi all,

   Sorry for all the noise.  I think I've fixed the issue I mentioned  
earlier.  It seems that the default for the "ServerScreen" setting was  
changed from 0.5.2.  When this setting is on, mythtv and LCDd fight  
over whether the backlight should be on.  This causes the backlight to  
flash.

   If this is truly the cause of the problem that lead to the addition  
of the return statement in imonlcd, then I think the return statement  
should be entirely removed.  It is unfortunate that a patch was added  
rather than fixing the server settings.

   It does make me wonder if the default should be changed back to  
ServerScreen "off".

Be well,

Will       :-}


From rbu at gentoo.org  Mon Jun  8 15:21:26 2009
From: rbu at gentoo.org (Robert Buchholz)
Date: Mon, 8 Jun 2009 17:21:26 +0200
Subject: [Lcdproc] LCDproc 0.5.3-pre1 available
In-Reply-To: <4A2BED8C.8080300@nurfuerspam.de>
References: <4A2BED8C.8080300@nurfuerspam.de>
Message-ID: <200906081721.28309.rbu@gentoo.org>

On Sunday 07 June 2009, Markus Dolze wrote:
> Hello everyone!
>
> for the last two weeks not much work has been done on the release,
> mainly because I had a lot of other work to do.
>
> Today I merged the changes that have been committed to cvs HEAD
> during the last weels to the release branch and created the first
> release candidate named '0.5.3-pre1' and made it available on
> Sourceforge for immediate download.

Markus,

I have committed updates to Gentoo in the unstable distribution. I'll 
let you know when there are any bug reports. Unfortunately, I have not 
yet added support for mx5000 as we're still missing the mx5000tools.


Robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.omnipotent.net/pipermail/lcdproc/attachments/20090608/f6d28e21/attachment-0001.pgp>

From TELarson at west.com  Mon Jun  8 15:45:37 2009
From: TELarson at west.com (Larson, Timothy E.)
Date: Mon, 8 Jun 2009 10:45:37 -0500
Subject: [Lcdproc] LCDproc 0.5.3-pre1 available
In-Reply-To: <4A2BED8C.8080300@nurfuerspam.de>
References: <4A2BED8C.8080300@nurfuerspam.de>
Message-ID: <226316B3E1F749498E28ACA66321D5BA2AD5E195@oma00cexmbx03.corp.westworlds.com>

> Today I merged the changes that have been committed to cvs HEAD during
> the last weels to the release branch 

Very exciting!  Just posted my smoketest results for lcdproc-0-5-3 and current.  :)

Tim

From bsdfan at nurfuerspam.de  Fri Jun 12 16:45:58 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Fri, 12 Jun 2009 18:45:58 +0200
Subject: [Lcdproc] Flashing screen fixed...
Message-ID: <20090612164558.308660@gmx.net>

Hi,

it is true that the backlight seems flashing if the serverscreen is on and a client has turned the backlight off.

It is a common misunderstanding of how the backlight setting works in LCDproc (BTW: the heartbeat works the same).

The backlight control is enforced by LCDd. There is one global setting (backlight) in LCDd.conf which can be 'on', 'off', or 'open'. These are enforced for all clients (including the internal one). While on/off are obvious, 'open' means that the client may control the backlight for its own screen(s).

So if there is any other client connected (including the server), that client may have different backlight settings. Especially the backlight will be ON if not configured otherwise.

It is not possible to turn the backlight off globally by a client. This is by design. If you want users to experience a completely OFF backlight, you need to tell them to set serverscreen=no and to not connect other clients.

Regards,
Markus

From allsorts at howhill.com  Sat Jun 13 21:28:32 2009
From: allsorts at howhill.com (Dave Liquorice)
Date: Sat, 13 Jun 2009 22:28:32 +0100 (BST)
Subject: [Lcdproc] Flashing screen fixed...
In-Reply-To: <20090612164558.308660@gmx.net>
Message-ID: <mailman.0.1244928551.3617.lcdproc@lists.omnipotent.net>

On Fri, 12 Jun 2009 18:45:58 +0200, Markus Dolze wrote:

> The backlight control is enforced by LCDd. There is one global setting 
> (backlight) in LCDd.conf which can be 'on', 'off', or 'open'. These are 
> enforced for all clients (including the internal one). While on/off are 
> obvious, 'open' means that the client may control the backlight for its 
> own screen(s).
<snip>
> If you want users to experience a completely OFF backlight, you need to 
> tell them to set serverscreen=no and to not connect other clients.

Surely you just set the global backlight setting to off in LCDd.conf?

-- 
Cheers
Dave.



From willu.mailingLists at cse.unsw.edu.au  Mon Jun 15 07:35:47 2009
From: willu.mailingLists at cse.unsw.edu.au (William Uther)
Date: Mon, 15 Jun 2009 17:35:47 +1000
Subject: [Lcdproc] [PATCH] Allow backlight to work on imonlcd
Message-ID: <4B9E8817-D3D3-48C4-8FB0-7DB2F07ECD79@cse.unsw.edu.au>

Hi,
   As it seems to be agreed that incorrect configuration can lead to  
screen flashing, that would seem to be the reason someone added the  
bogus return to the imonlcd driver.  Can this be removed please?

   A simple patch to revert the bogus 'fix' is attached.

Thanks,

Will      :-}

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lcdproc-imon-backlight.diff
Type: application/octet-stream
Size: 768 bytes
Desc: not available
URL: <http://lists.omnipotent.net/pipermail/lcdproc/attachments/20090615/2f1ab2b0/attachment.obj>
-------------- next part --------------



From bsdfan at nurfuerspam.de  Wed Jun 17 05:55:48 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Wed, 17 Jun 2009 07:55:48 +0200
Subject: [Lcdproc] [PATCH] Allow backlight to work on imonlcd
In-Reply-To: <4B9E8817-D3D3-48C4-8FB0-7DB2F07ECD79@cse.unsw.edu.au>
References: <4B9E8817-D3D3-48C4-8FB0-7DB2F07ECD79@cse.unsw.edu.au>
Message-ID: <4A388564.1050703@nurfuerspam.de>

William Uther wrote:
> Hi,
>   As it seems to be agreed that incorrect configuration can lead to
> screen flashing, that would seem to be the reason someone added the
> bogus return to the imonlcd driver.  Can this be removed please?
>
>   A simple patch to revert the bogus 'fix' is attached.


Hi,

after reading the code comment I am not sure if an incorrect
configuration was the source of that author's problem. The comment
describes the fact that the display is turned OFF for some reason. But
using the serverscreen will only turn the backlight ON.

However, I will commit your 'fix' because currently the backlight
feature is completely disabled and we therefore will never get any
feedback if its correctly working or not.

BTW: You don't need to submit patches more than once. Just reply to your
old mail or send a link to the mailing list archive.

Regards,
Markus

From willu.mailingLists at cse.unsw.edu.au  Wed Jun 17 07:03:20 2009
From: willu.mailingLists at cse.unsw.edu.au (William Uther)
Date: Wed, 17 Jun 2009 17:03:20 +1000
Subject: [Lcdproc] [PATCH] Allow backlight to work on imonlcd
In-Reply-To: <4A388564.1050703@nurfuerspam.de>
References: <4B9E8817-D3D3-48C4-8FB0-7DB2F07ECD79@cse.unsw.edu.au>
	<4A388564.1050703@nurfuerspam.de>
Message-ID: <F902B14A-1EE6-4105-9C0A-79DF70A10C02@cse.unsw.edu.au>


On 17/06/2009, at 3:55 PM, Markus Dolze wrote:

>
> William Uther wrote:
>> Hi,
>>  As it seems to be agreed that incorrect configuration can lead to
>> screen flashing, that would seem to be the reason someone added the
>> bogus return to the imonlcd driver.  Can this be removed please?
>>
>>  A simple patch to revert the bogus 'fix' is attached.
>
>
> Hi,
>
> after reading the code comment I am not sure if an incorrect
> configuration was the source of that author's problem. The comment
> describes the fact that the display is turned OFF for some reason. But
> using the serverscreen will only turn the backlight ON.

For those following along at home, here is the comment.  It appears at  
the top of the imonlcd backlight function:

-	/*
-	 * TODO: For some reason, lcdproc keeps calling this and flipping the
-	 * 'on' so you end up flashing the backlight for no particular reason
-	 * (and on my Antec, turning the backlight off, turns the whole thing
-	 * off, so it's really bad...)
-	 */
-	return;

I read the comment as saying two things:
   a) their backlight was being switched on and off (or off and on).   
This happened to me under lcdproc head, but not the last release of  
lcdproc when used with MythTV.
   b) turning the backlight off switches off the "whole thing", "so  
it's really bad".  I don't know exactly what is meant by "whole thing"  
here.  With my device (also an Antec, but there are many imon devices  
used by Antec) turning the backlight off leaves the remote control  
working.  I'm not sure what else would be counted in "while thing".   
It doesn't shut down my machine. :)


   Part a) seems to describe the result of the configuration error  
discussed where MythTV fights with the serverscreen about whether the  
backlight should be on.  It can be fixed by, amongst other methods,  
turning serverscreen off in the LCDd config file.
   Part b) is confusing, but adding "Backlight=on" to the config file  
would seem to be a better fix than commenting out functionality that  
other people can use.


> However, I will commit your 'fix' because currently the backlight
> feature is completely disabled and we therefore will never get any
> feedback if its correctly working or not.

Thank you.

> BTW: You don't need to submit patches more than once. Just reply to  
> your
> old mail or send a link to the mailing list archive.

The two patches I sent are different, although they both address the  
same issue.  Only one should be applied.  The first patch added a  
configuration option - I wasn't sure what the person who put that  
return in was seeing, and by adding a config option I wouldn't break  
anything for anyone.  The second patch removed the return statement  
entirely - I am more confident now that current config options can  
already fix any issues.

Be well,

Will       :-}


From bsdfan at nurfuerspam.de  Sat Jun 20 15:04:42 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Sat, 20 Jun 2009 17:04:42 +0200
Subject: [Lcdproc] Release ahead!
Message-ID: <20090620150442.240190@gmx.net>

Hi,

by tomorrow afternoon (CEST) I will create the LCDproc 0.5.3 release tarball.

If you have any comments on the release, please post them now.

Regards
Markus

From bsdfan at nurfuerspam.de  Sun Jun 21 21:15:19 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Sun, 21 Jun 2009 23:15:19 +0200
Subject: [Lcdproc] LCDproc v0.5.3 released
Message-ID: <4A3EA2E7.2000401@nurfuerspam.de>

Hello,

today LCDproc 0.5.3 has been released. This is the new stable version of
LCDproc.

This release includes a lot of bug fixes as well as several new and
updated drivers. See the release notes for more details.

It is available from the Sourceforge download service:
http://sourceforge.net/project/showfiles.php?group_id=119&package_id=107&release_id=691428

Fingerprint:
------------
SHA1 (lcdproc-0.5.3.tar.gz) = 7550aa28b224fd800047b92d184a64d529e32283

Regards,
Markus Dolze


From pavkamlc at gmail.com  Mon Jun 22 07:51:26 2009
From: pavkamlc at gmail.com (=?UTF-8?B?UGF2ZWwgTWzEjW9jaA==?=)
Date: Mon, 22 Jun 2009 09:51:26 +0200
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A3EA2E7.2000401@nurfuerspam.de>
References: <4A3EA2E7.2000401@nurfuerspam.de>
Message-ID: <4A3F37FE.6000107@gmail.com>

Hello,
 I found wrong link in section Testing. The link "Build and installation 
instructions" pointed to 
http://lcdproc.sourceforge.net/docs/current-user-html/c185.html#BUILD-AND-INSTALL 
but this site writes what You can see in attachment. So can You repair it?
 At the end, I've short question. I've "MSI media-center live" and this 
machine have VFD. I used my own deb package based on third-side patch, 
which support this VFD by dm140 module. Is this module supported in new 
version without this patch? If it's I can create new deb package for my 
PPA repository. However I don't know how to identify my VFD device, and 
I can't find it in list of supported devices. At the end You can see 
information about my HW.

Best regards,
 Pavel Ml?och.

pavka at pavka:~/Plocha/lcdproc-0.5.3$ lsusb
Bus 001 Device 008: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
Bus 001 Device 007: ID 0db0:a97a Micro Star International Bluetooth EDR 
Device
Bus 001 Device 006: ID 040b:7001 Weltrend Semiconductor
Bus 001 Device 005: ID 0db0:6874 Micro Star International RT2573
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0471:0815 Philips eHome Infrared Receiver
Bus 002 Device 002: ID 04f2:0200 Chicony Electronics Co., Ltd
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
pavka at pavka:~/Plocha/lcdproc-0.5.3$ lspci
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51 [GeForce 6150 
LE] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller 
(rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller 
(rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio 
(rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
04:06.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
Capture (rev 11)
04:06.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture 
(rev 11)
04:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 
1394 OHCI Link Layer Controller (rev c0)
pavka at pavka:~/Plocha/lcdproc-0.5.3$




Markus Dolze wrote:
> Hello,
>
> today LCDproc 0.5.3 has been released. This is the new stable version of
> LCDproc.
>
> This release includes a lot of bug fixes as well as several new and
> updated drivers. See the release notes for more details.
>
> It is available from the Sourceforge download service:
> http://sourceforge.net/project/showfiles.php?group_id=119&package_id=107&release_id=691428
>
> Fingerprint:
> ------------
> SHA1 (lcdproc-0.5.3.tar.gz) = 7550aa28b224fd800047b92d184a64d529e32283
>
> Regards,
> Markus Dolze
>
> _______________________________________________
> LCDproc mailing list
> LCDproc at lists.omnipotent.net
> http://lists.omnipotent.net/mailman/listinfo/lcdproc
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lcdprocweb.txt
URL: <http://lists.omnipotent.net/pipermail/lcdproc/attachments/20090622/1d3742ad/attachment-0001.txt>

From TELarson at west.com  Mon Jun 22 14:01:51 2009
From: TELarson at west.com (Larson, Timothy E.)
Date: Mon, 22 Jun 2009 09:01:51 -0500
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A3EA2E7.2000401@nurfuerspam.de>
References: <4A3EA2E7.2000401@nurfuerspam.de>
Message-ID: <226316B3E1F749498E28ACA66321D5BA36AEC767@oma00cexmbx03.corp.westworlds.com>

Big thanks to everyone who contributed to getting this out!



Tim

From jarod at wilsonet.com  Mon Jun 22 15:17:06 2009
From: jarod at wilsonet.com (Jarod Wilson)
Date: Mon, 22 Jun 2009 11:17:06 -0400
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A3EA2E7.2000401@nurfuerspam.de>
References: <4A3EA2E7.2000401@nurfuerspam.de>
Message-ID: <975903A3-FEC2-41A0-A34E-97F8AB8317A4@wilsonet.com>

On Jun 21, 2009, at 5:15 PM, Markus Dolze wrote:

> Hello,
>
> today LCDproc 0.5.3 has been released. This is the new stable  
> version of
> LCDproc.
>
> This release includes a lot of bug fixes as well as several new and
> updated drivers. See the release notes for more details.

Thanks much for all the work folks did on this release!

Updated packages for Fedora have been spun, though only for rawhide at  
the moment. Will build for Fedora 10 and 11 after a bit of testing to  
make sure I didn't screw anything up... (The rawhide packages should  
work fine on F11 w/o a rebuild, not sure about F10).

http://koji.fedoraproject.org/koji/buildinfo?buildID=111345


-- 
Jarod Wilson
jarod at wilsonet.com





From TELarson at west.com  Mon Jun 22 15:50:01 2009
From: TELarson at west.com (Larson, Timothy E.)
Date: Mon, 22 Jun 2009 10:50:01 -0500
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A3EA2E7.2000401@nurfuerspam.de>
References: <4A3EA2E7.2000401@nurfuerspam.de>
Message-ID: <226316B3E1F749498E28ACA66321D5BA36AEC76A@oma00cexmbx03.corp.westworlds.com>

I cannot build from the release tarball on Solaris, though the 0-5-3 CVS branch builds fine.  Diffing the two directories, I see shared/getopt.h was removed from the release.


Tim

From bsdfan at nurfuerspam.de  Mon Jun 22 20:42:25 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Mon, 22 Jun 2009 22:42:25 +0200
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <226316B3E1F749498E28ACA66321D5BA36AEC76A@oma00cexmbx03.corp.westworlds.com>
References: <4A3EA2E7.2000401@nurfuerspam.de>
	<226316B3E1F749498E28ACA66321D5BA36AEC76A@oma00cexmbx03.corp.westworlds.com>
Message-ID: <4A3FECB1.6030808@nurfuerspam.de>

Larson, Timothy E. wrote:
> I cannot build from the release tarball on Solaris, though the 0-5-3
> CVS branch builds fine.  Diffing the two directories, I see
> shared/getopt.h was removed from the release.
> 
> 
> Tim
> 

I really dislike this getopt stuff.

The point is that the release tarball is not just an "export" from cvs,
but it is built with 'make dist'. getopt.h is not declared within
Makefile.am or Makefile.in.

Releases 0.5.2 and 0.5.1 miss this file, too.

I have not detected this, because my system does have a getopt.h, which
is used if LCDproc's one cannot be found.

I'm looking into this right now.

Regards,
Markus

From bsdfan at nurfuerspam.de  Mon Jun 22 21:01:52 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Mon, 22 Jun 2009 23:01:52 +0200
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A3F37FE.6000107@gmail.com>
References: <4A3EA2E7.2000401@nurfuerspam.de> <4A3F37FE.6000107@gmail.com>
Message-ID: <4A3FF140.5020709@nurfuerspam.de>

Hi,

Pavel Ml?och wrote:
> Hello,
> I found wrong link in section Testing. The link "Build and
> installation instructions" pointed to
> http://lcdproc.sourceforge.net/docs/current-user-html/c185.html#BUILD-AND-INSTALL
> but this site writes what You can see in attachment. So can You repair
> it?

the web page at www.lcdproc.org need to be updated at all for the
release. Who is able to do this?

> At the end, I've short question. I've "MSI media-center live" and this
> machine have VFD. I used my own deb package based on third-side patch,
> which support this VFD by dm140 module. Is this module supported in
> new version without this patch? If it's I can create new deb package
> for my PPA repository. However I don't know how to identify my VFD
> device, and I can't find it in list of supported devices. At the end
> You can see information about my HW.
>

I remember having seen this on some Linux distro tracker. As long as
noone submits a driver to the LCDproc project, it will not be
integrated. I am currently not aware that this happened. This only trace
of DM140 is this
http://lists.omnipotent.net/pipermail/lcdproc/2007-May/011737.html which
talks about the device you have: ID 040b:7001

Regards,
Markus

From rw at nelianur.org  Mon Jun 22 21:30:15 2009
From: rw at nelianur.org (Rene Wagner)
Date: Mon, 22 Jun 2009 23:30:15 +0200
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A3FF140.5020709@nurfuerspam.de>
References: <4A3EA2E7.2000401@nurfuerspam.de> <4A3F37FE.6000107@gmail.com>
	<4A3FF140.5020709@nurfuerspam.de>
Message-ID: <1245706215.2933.5.camel@antarctica.nelianur.org>

Hi Gareth,

could you perhaps create a CVS account for the website repository for
Markus?

Thanks,

Rene

On Mon, 2009-06-22 at 23:01 +0200, Markus Dolze wrote:
> the web page at www.lcdproc.org need to be updated at all for the
> release. Who is able to do this?


From bsdfan at nurfuerspam.de  Tue Jun 23 21:13:47 2009
From: bsdfan at nurfuerspam.de (Markus Dolze)
Date: Tue, 23 Jun 2009 23:13:47 +0200
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <226316B3E1F749498E28ACA66321D5BA36AEC76A@oma00cexmbx03.corp.westworlds.com>
References: <4A3EA2E7.2000401@nurfuerspam.de>
	<226316B3E1F749498E28ACA66321D5BA36AEC76A@oma00cexmbx03.corp.westworlds.com>
Message-ID: <4A41458B.1020501@nurfuerspam.de>

Larson, Timothy E. wrote:
> I cannot build from the release tarball on Solaris, though the 0-5-3
> CVS branch builds fine.  Diffing the two directories, I see
> shared/getopt.h was removed from the release.
> 
> 
> Tim
> 

Hi,

looking into this it seems a problem and / or misunderstanding with the
autoconf DIST_COMMON magic.

I do not want to touch the release to fix this (creating some 0.5.3.1).

If we discover other problems with the release, it will be fixed as
well, but otherwise you have to add that file manually on Solaris. I
already added a note about that into the Release Notes.

It will be fixed in cvs HEAD anyway.

Things like these are the reason why I created the release candidate,
but that one slipped through.

Regards,
Markus

From TELarson at west.com  Tue Jun 23 21:26:23 2009
From: TELarson at west.com (Larson, Timothy E.)
Date: Tue, 23 Jun 2009 16:26:23 -0500
Subject: [Lcdproc] LCDproc v0.5.3 released
In-Reply-To: <4A41458B.1020501@nurfuerspam.de>
References: <4A3EA2E7.2000401@nurfuerspam.de>
	<226316B3E1F749498E28ACA66321D5BA36AEC76A@oma00cexmbx03.corp.westworlds.com>
	<4A41458B.1020501@nurfuerspam.de>
Message-ID: <226316B3E1F749498E28ACA66321D5BA36AEC777@oma00cexmbx03.corp.westworlds.com>

> Things like these are the reason why I created the release candidate,
> but that one slipped through.

I'd assumed it was just a drop from CVS, so since I was busy at work I didn't take the time to try the RC.  My bad, I guess.  I imagine there aren't too many in an affected situation, however.

FWIW, it builds fine on my NetBSD box, so I'll still work on incorporating to pkgsrc.  :)


Tim