Hi,
With Daniel R's helpfulness i was able to get the 2.6.21 images to boot
properly
on the e680. To do so i applied all the 2.6.21 patches, then went in and
edited
arch/arm/mach-pxa/ezx-bp.c by hand.
Specifically on lines 48 and 140 of ezx-bp.c i commented out the
'pm_power_off();' lines, copied
defconfig-e680 from the patchset to .config, and then did the make.
Also, i missed something somewhere and didn't know that the 2.6.21 kernel is
looking for rootfs
on a second mmc partition, once i took care of that things worked again
nicely; again thanks to Daniel R
and all at #openezx for being patient with me :).
The image boots fine to a x11-image rootfs, but it seemed to hang on an
e-image, (but i'm assuming
that's an unrelated issue).
cheers,
Mike
On 5/30/07, Michael Kramer <[EMAIL PROTECTED]> wrote:
Hi,
I just gone done building the angstrom images with the 2.6.21 kernel and
when i try to boot it the
screen shows some garbage and the phone dies right away.
afaict the host and target are setup okay as i've been able to use
ezx-boot-usb to successfully
boot zimages against the opie rootfs as well as the angstrom-console-image
(both
downloaded) as well as a freshly built openmoko-devel-image (that was
really cool!)
all to the same e680, but these were all 2.6.16.13 kernels.
i've also tried some of the new prebuilt angstrom images (built against
2.6.21) and they
bombed the same way (gobbledygook on the screen, then shutdown).
has anyone else had this problem? and/or has anyone else been able to
boot the new images
on an e680? (if its booting on an a780 then i don't see any reason it
shouldn't boot on the
e680, but i'm certainly not enough of an expert to know the detailed
difference; any suggestions?)
thanks,
Mike
