1. why is kernel in Pluto CD 686 ? I guess majority of PCs will be P4 based. I'm compiling all my modules on same arch to stay compatible but am not sure whether this is good...
The 686 kernel works on AMD processors too, not just P4. I've seen it running on a AMD Athlon 64 processor just fine. Haven't tried it on VIA CPUs though.
In the future we may add more kernels to the CD since the installer detects the CPU and installs the most appropriate kernel, but we need to refine the build process to support multiple architectures somehow regarding module compiling.
2. I've compiled pwc.ko module (for support of usb Logitech Quick PRO and other Philips chip based cameras - there are a lots of these used under Linux). I can contribute that module somewhere (maybe contributions forum and place to upload would be needed...).
I just looked around and what I saw is weird. There is a pwc.ko file in the 2.6.8-2 kernel, but it's no longer present in the 2.6.10 version. I was unable to find on Google where it went.
Also I'd kindly ask for guidance how to make proper device templates for adding usb cameras to pluto and motion and more info on whole procedure of adding support for new HW devices....
To make a device template, you use the pluto admin website
on your Core. I don't know how you upload new templates yet though. I don't have much experience with device templates as to properly guide you.
3. I'm trying to compile CAPI support for AVM Fritz cards (1 BRI ISDN interface, quite cheap and really popular around Europe, but have following problem... (quick question: how can I recompile Asterisk to add chan_capi?)
Our current Asterisk has some custom changes in it that haven't been incorporated into the main Asterisk tree yet. Our branch of Asterisk will be available in 24 hours in our newbielink:http://subversion.tigris.org/ [nonactive]
repository, which is accessible at newbielink:http://svn.plutohome.com/pluto/trunk/ [nonactive]
I've downloaded kernel source, configure it and compiled modules and install
them (make menuconfig, make , make modules, make modules_install) .
I'd also like to compile some other stuff according to separate instructions
but get those errors on build directory in /lib/modules..
Any hint what should I do to get rid of those errors ?
make -C src
make: Entering directory `/root/Plutohome/Fritz/fritz/src'
make -C /lib/modules/2.6.10-1-686/build
make: Entering directory `/lib/modules/2.6.10-1-686/build'
make: *** No rule to make target `modules'. Stop.
make: Leaving directory `/lib/modules/2.6.10-1-686/build'
make: *** [fcpci.ko] Error 2
make: Leaving directory `/root/Plutohome/Fritz/fritz/src'
make: *** [src/fcpci.ko] Error 2
We build our modules out-of-tree using the stock Debian 2.6.10 kernel from unstable. The vanilla kernel from newbielink:http://kernel.org [nonactive]
won't work unless you replace the running kernel with one build from those sources.
To compile your modules the same way, you need these packages from our reporitory:
You need the source because the kbuild package is for the 2.6.8 kernel that is found in Sarge, and we use the 2.6.10 from Sid (unstable).
After you install these packages, do this to set up the build environment:
tar -xjvf kernel-source-2.6.10.tar.bz2
cp -a kernel-source-2.6.10/scripts kernel-kbuild-2.6-4/
ln -s ../kernel-headers-2.6.10-1/include/ kernel-kbuild-2.6-4/
cp kernel-headers-2.6.10-1-686/.extraversion kernel-headers-2.6.10-1-686/localversion
After this is done, you can go into your module source directory and build it with this command:KDIR=/usr/src/kernel-headers-2.6.10-1-686 make -f Makefile -e
4. I get same error when I try to compile vloopback (can be found on motion web site), that does useful thing (at least for me and my previous Misterhouse based system).
One of the team members had a task to play with vloopback to be used with linphone. It wasn't integrated into the product yet though, but it's on the TODO list.
It generates virtual v4l devices, motion application duplicates video stream it receives, so for instance Mythtv can show same video as motion is outputting on virtual v4l device - you can have PIP with security video.... What is your opinion on this feature ?
From my point of view, it sounds interesting.