Hi Ame,
It sounds like a patch might be missing. Do a cvs update and
then rename your
/ltib/rpm/BUILD/Linux-2.6.34 directory to something else and then
run ltib again.
Try the updated version of uImage to see if it helps any. If it
keeps failing, I take
a look at it in my board.
thanks,
Kevin
From: Burghardt Arne
[mailto:address@hidden
Sent: Thursday, August 05, 2010 2:58 PM
To: Kevin Wells
Cc: address@hidden
Subject: AW: [Ltib] EA3250: Touchscreen not functional with 2.6.34
kernel
Hi Kevin,
thank you for the clarification. Now it is clear, why the booting stops.
Nevertheless i still have my touchscreen problem... :-)
I have already asked EA for help, but maybe you have some other ideas ?
There is maybe one suspicous line in the bootmessages:
---> input: ADS7846 Touchscreen as /class/input/input0
Is this correct ? I suspect, that the touchscreen should be bound to
/dev/input/event0 ?
Best regards
Arne
-----Ursprüngliche Nachricht-----
Von: Kevin Wells [mailto:address@hidden]
Gesendet: Do 05.08.2010 23:20
An: Charles Krinke; Burghardt Arne
Cc: address@hidden
Betreff: RE: [Ltib] EA3250: Touchscreen not functional with 2.6.34 kernel
Hi Ame & Charles,
The u-boot boot storage area did change with the last patch. There is also a
possibility the machine ID is wrong.
i have tried to boot with the old kernel and now i have another problem:
It doesn't boot anymore...
I have replaced u-boot with the orginal provided u-boot and transferred the old
provided kernel via TFTP to my board.
And here is the result:
About 6 months ago, the machine IDs used in u-boot changed to match the
mainline IDs instead of the
generic LPC3XXX IDs. This means the older kernels compiled with only the
LPC3XXX machine ID will no
longer boot with the updated u-boot. However, older versions of u-boot will
boot kernels with both the
LPC3XXX and the new machine IDs. I think this is what you are experiencing.
Here is the original information on that change:
**snip**
If the kernel is uncompressing and seems to start, but there is no console
output, it's possible the machine
IDs used in u-boot and the kernel are different. You can enable the
CONFIG_DEBUG_LL option in the
kernel and then try booting the kernel. If the machine IDs are the issue,
you'll see a message stating the
difference and the kernel will stop running.
The 32x0 kernels recently changed the machine ID from the generic 'LPC3XXX'
used for all boards to
PHY3250, EA3250, and FDI3250 depending on which board you use. u-boot was also
updated with this
change, so depending on which board's version of u-boot you use, you will get a
corresponding
'non-LPC3XXX' machine ID passed via the ATAG list.
To allow for some backward compatability, the LPC3XXX is also supported in the
kernel here along with the
new machine IDs, so older builds of u-boot with the LPC3XXX machine ID should
work fine with the new
kernel builds (as long as the kernel is built via LTIB, the 2.6.34 patches do
not have this support!). Note
2.6.34 support is not in LTIB yet.
Older build kernels with just the LPC3XXX machine ID support will no longer
work with the new version
of u-boot.
Just to clear things up, 'older' and 'newer' builds simply refer to u-boot and
kernel builds before the machine
ID patch and after the machine ID patch, respectively. The patch that changes
these IDs was posted about a
month ago.
It's a bit messy, but it needed to be done, I couldn't release all board
variants to mainline with the same
machine IDs. There should be some information about this in the deployment.txt
file, but I can understand
that existing users probably wouldn't look at this.
Here are the build machine IDs:
old u-boot.bin -> LPC3XXX for Phytec, Embedded Artist, and FDI boards
new u-boot.bin -> Either PHY3250, EA3250, or FDI3250 based on the LTIB
platform selected
old uImage -> LPC3XXX for Phytec, Embedded Artist, and FDI boards
new uImage (2.6.27.8) -> LPC3XXX + one of PHY3250, EA3250, or FDI3250 based
on the LTIB platform selected
new uImage (2.6.34) -> Only one of PHY3250, EA3250, or FDI3250
Here are the working combinations
new u-boot.bin (PHY3250, EA3250, or FDI3250 machine IDs) -> Will not boot
older kernel with LPC3XXX machines IDs
new u-boot.bin (PHY3250 machine ID) -> Only boots newer kernel builds with
PHY3250 machine ID
new u-boot.bin (EA3250 machine ID) -> Only boots newer kernel builds with
EA3250 machine ID
new u-boot.bin (FDI3250 machine ID) -> Only boots newer kernel builds with
FDI3250 machine ID
old u-boot.bin (LPC3XXX machine ID, all boards) -> boots older and newer
kernel builds
This will probably sting a few people in the short term, but it needed to be
done.
**snip**
thanks,
Kevin
|