From: <li...@ba...> - 2008-04-06 11:56:22
|
Hi, it's more than time to make a new release. So I just put a new CVS snapshot online: http://lirc.sourceforge.net/software/snapshots/lirc-0.8.3pre2.tar.bz2 Please test if there is anything obvious which might prevent us from releasing this version. Christoph |
From: Alexander D. <po...@le...> - 2008-04-06 17:27:45
Attachments:
signature.asc
|
Hi Christoph, > it's more than time to make a new release. So I just put a new CVS > snapshot online: > > http://lirc.sourceforge.net/software/snapshots/lirc-0.8.3pre2.tar.bz2 I just tried the snapshot, that makes it possible for me to build a bleeding edge lirc without my build environment trouble, which prevents me from building directly from CVS. O:-) > Please test if there is anything obvious which might prevent us from > releasing this version. I was able to build lirc 0.8.3pre2 with driver options 'atiusb' and 'userspace', so far so good, but it fails with driver 'serial'. Here is how I configured lirc: ./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var/lib \ --libdir=/usr/lib \ --host=i386-pc-linux-gnu \ --libexecdir=/usr/local/lirc \ --without-x \ --with-driver=serial The error I get is the same on a machine with kernel 2.4.26 and gcc 2.95.3 and another machine with kernel 2.4.35 and gcc 3.4.6 (both patched distribution specific kernels), I show some output of the second one: lirc_serial.c:102:22: linux/io.h: No such file or directory lirc_serial.c:123:2: warning: #warning "Software carrier only affects transmitting" lirc_serial.c:129:2: warning: #warning "Note: using rdtsc instruction" lirc_serial.c: In function `sinp': lirc_serial.c:407: warning: implicit declaration of function `inb' lirc_serial.c: In function `soutp': lirc_serial.c:419: warning: implicit declaration of function `outb' make[5]: *** [lirc_serial.o] Error 1 make[5]: Leaving directory `/home/alex/src/lirc-0.8.3pre2/drivers/lirc_serial' I assume the crucial point is that he doesn't find 'linux/io.h'. I compared the code of drivers/lirc_serial/lirc_serial.c with the one from lirc release 0.8.2. In 0.8.2 'asm/io.h' is included instead of 'linux/io.h'. I changed this back to 'asm/io.h' and make runs successful on both machines described above then. I don't have time to test the binaries today, perhaps I'll do this later. HTH & greets Alex -- ***** http://www.lespocky.de ******************************************* Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin) |
From: <li...@ba...> - 2008-04-06 19:14:09
|
Hi! Alexander Dahl "po...@le..." wrote: [...] >> Please test if there is anything obvious which might prevent us from >> releasing this version. > I was able to build lirc 0.8.3pre2 with driver options 'atiusb' and > 'userspace', so far so good, but it fails with driver 'serial'. Some time ago I have asked around if anyone still needs 2.4 kernel support. At that time nobody objected to drop 2.4 support, so it's not supported officialy anymore. Christoph |
From: Alexander D. <po...@le...> - 2008-04-06 19:53:55
Attachments:
signature.asc
|
Hi Christoph, > Some time ago I have asked around if anyone still needs 2.4 kernel > support. At that time nobody objected to drop 2.4 support, so it's not > supported officialy anymore. I would have complained, if I had read the list. Unfortunatly I subscribed not until last week. :-( Sorry for bothering you with a problem deriving from dropped support for an old kernel. You are certainly right, kernel 2.4 is old and for the major distributions no topic anymore. The things with eisfair are a bit different and we just released an up to date 2.4 series kernel for eisfair-1. eisfair-2 will use kernel 2.6 and is on the way, but I assume that we still have to stay with eisfair-1 and kernel 2.4 for quite a while. I regret this, but speed of development is dependent on number of active developers and there are still too much issues preventing us from releasing eisfair-2. Despite of this: how difficult would it be to revert changes making lirc imcomplete to kernel 2.4. series? For now I include only two drivers into the LIRC package for eisfair: serial and atiusb. There was no single wish to include more drivers for eisfair in the past so I think it would be sufficient for me to obtain support for at least the serial driver for kernel 2.4 series. Is the change on the include paths I proposed before the only one necessary to make this driver run again? Would that be enough to make this driver correctly working again with 2.4.x kernel or are there problems to be expected resulting from other changes since you decided to drop 2.4.x support? Assuming you don't want to support 2.4 anyway, when was the point you stopped support? Perhaps I could make a special patched version from this point of development to match my requirements. Greets Alex -- ***** http://www.lespocky.de ******************************************* Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin) |
From: <li...@ba...> - 2008-04-08 06:40:33
|
Hi! Alexander Dahl "po...@le..." wrote: [...] > Is the change on the include paths I proposed before the only one > necessary to make this driver run again? Would that be enough to make > this driver correctly working again with 2.4.x kernel or are there > problems to be expected resulting from other changes since you decided > to drop 2.4.x support? Probably it will be enough to change the include paths. That we dropped 2.4 support simply means that I don't test compilation on 2.4 anymore. If you submit reasonable patches, I can include them, but you most likely won't get any support if you run into trouble. Christoph |
From: Alexander D. <po...@le...> - 2008-04-08 07:36:17
Attachments:
signature.asc
|
Hi Christoph, > Probably it will be enough to change the include paths. > That we dropped 2.4 support simply means that I don't test compilation > on 2.4 anymore. If you submit reasonable patches, I can include them, > but you most likely won't get any support if you run into trouble. Ok thank you. I'll check the changes in the serial driver by myself and test and report then. :) Another good news is, that we (eisfair) stumbled upon a third software where autoconf doesn't work correctly so I'm in a good hope we can fix our build environment and I will be able to build LIRC from CVS soon. :) Greets Alex -- 'With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** |
From: Alexander D. <po...@le...> - 2008-04-10 08:15:45
Attachments:
signature.asc
|
Hello, > Ok thank you. I'll check the changes in the serial driver by myself and > test and report then. :) I saw you changed the lirc_serial.c to include the correct io.h on 2.4 kernels in CVS, thanks :) > Another good news is, that we (eisfair) stumbled upon a third software > where autoconf doesn't work correctly so I'm in a good hope we can fix > our build environment and I will be able to build LIRC from CVS soon. :) The autogen.sh produces a correct ./configure now after we switched to new versions of m4 and autoconf. I was able to build LIRC from CVS yesterday. I didn't had much time to test yet, but I was able to build it without errors with gcc 3.4.6 and patched kernel 2.4.35 with all driver options (serial, atiusb, userspace) I need. I successfully tested my IR remote with the serial driver and mode2 and irw :-) My ATI remote produces codes with mode2, irw didn't work out of the box with the ATI config you deliver. I will try again soon, it could be an issue with the channel of the remote or I have to use irrecord to make my own config. I don't expect problems. Greets Alex -- 'With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** |