But in that case, the git repository that I downloaded from wasn't identical
to kernel.org, is it?
huh? the script use kernel.org git repo as a "base" for everything..
Surely you are doing something with it, if only
setting up the dot-config file?
If all we were doing was setting up a dot-config, I wouldn't be
wasting my time maintaining a script.. Instead every reply on this
list would say "use kernel.org" but that isn't the case..
I am asking because I would like to be able
to compile a streamlined kernel, add the Leopard Imaging device driver to it
and then patch it up for Xenomai, too.
Everything but the "Xenomai" patch is already done for you... So I am
now expecting an "Xenomai" patchset from you in the next few days...
Then I will have to write kernel
modules for reading data from sensors and sending data to the devices
real-time. That is why I need to know how to put it together. Is there a
step-by-step guide explaining the procedure anywhere?
Instead of just running "./build_kernel.sh" blindly, actually take a
look at "patch.sh" and "version.sh" in my repo.. Your answers are
there..
I have acquired a disconnected set of skills which still do not enable me to
do what I want. In Angstroem's version of the kernel, I can install the
webcam as a module (as intended) and take pictures. In your version of the
kernel, the device driver is part of the kernel itself but I wasn't able to
access it from an application yet.
Well, the camera driver didn't properly load when it was built as a
module.. (patches welcome)
I can load and install your rootfs and
kernel images. As of yesterday, I can also compile from your git repos and
install a later kernel but not the latest one because there is a
compatibility problem.
What "compatibility" problem? The v3.6.x branch works perfectly fine
on all Beagle's and the Panda es..
I didn't understand what problem you are working on
if you are using a source code identical to the one at kernel.org. So, I am
confused.
Your questions are confusing... yes i'm using kernel.org as a base..
Yes, we deal with problems on a daily basis, if we didn't then
kernel.org would be "done" as no new fixes/changes would be needed..
I found that there is more than one set of MLO, u-boot and uEnv.txt
circulating. I remember in particular that enabling the Leopard Imaging
camera was not the same in the uEnv.txt files of Angstroem version and your
version of uEnv.txt.
Well then run "Angstrom" if you don't like what i changed in uEnv.txt
to enable the camera..
On one occasion, I compiled from kernel.org but it
didn't load presumably because it wasn't comaptible with the MLO or u_boot
that I had. Is that possible?
The last time it was "incompatiable" was back in 2.6.29 and it was
related to ehci and u-boot 1.3.x on the Beagle Cx.. More then likely
when you built your new kernel.org release, you didn't release you
enabled something, which required a one character change in your
uEnv.txt..
Here are the three sets of MLO, u-Boot and uEnv.txt that I have found so
far.
ahmet@T520:~/BB/sdcard$ ls -la Angstroem/
total 316
drwxrwxr-x 2 ahmet ahmet 4096 Oct 19 11:17 .
drwxrwxr-x 5 ahmet ahmet 4096 Oct 19 11:24 ..
-rw-r--r-- 1 ahmet ahmet 22232 Apr 19 2011 MLO
-rw-r--r-- 1 ahmet ahmet 284788 Apr 19 2011 U-BOOT.BIN
-rw-r--r-- 1 ahmet ahmet 150 Oct 8 13:26 uEnv.txt
ahmet@T520:~/BB/sdcard$ ls -la RobertCNelson/
total 396
drwxrwxr-x 2 ahmet ahmet 4096 Oct 19 11:15 .
drwxrwxr-x 5 ahmet ahmet 4096 Oct 19 11:24 ..
-rw-r--r-- 1 ahmet ahmet 46500 Oct 18 17:06 MLO
-rw-r--r-- 1 ahmet ahmet 342436 Oct 18 17:06 u-boot.img
-rw-r--r-- 1 ahmet ahmet 1065 Oct 18 17:09 uEnv.txt
ahmet@T520:~/BB/sdcard$ ls -la sabayon/
total 396
drwxrwxr-x 2 ahmet ahmet 4096 Oct 19 11:26 .
drwxrwxr-x 5 ahmet ahmet 4096 Oct 19 11:24 ..
-rw-rw-r-- 1 ahmet ahmet 43040 Oct 19 11:27 MLO
-rw-rw-r-- 1 ahmet ahmet 10583 Oct 19 11:24 README.txt
-rw-rw-r-- 1 ahmet ahmet 330836 Oct 19 11:28 u-boot.img
-rw-rw-r-- 1 ahmet ahmet 111 Oct 19 11:26 uEnv.txt
-rw-rw-r-- 1 ahmet ahmet 66 Oct 19 11:24 URL.txt
This is a total useless comparisons... IF "MLO" and "u-boot.*" came
from a once in a while closed source project, that had a release
whenever someone felt like it, then (and only then) would that
comparison make sense.. Instead they come from the the u-boot project
(1), which is very active with a stable release every 3-4 months.. So
actually boot the processor up with those files and look at the
"version"... The differences in uEnv.txt of course would match
changes in u-boot from version to version..
1: U-Boot / U-Boot · GitLab
Regards,