Mojo Handheld's Ubuntu armv5el Install for BeagleBoard

Just put up a quick guide located here (needs review before linking to
http://elinux.org/BeagleBoard) : http://elinux.org/BeagleBoardUbuntu
on installing Mojo Handhelds's frisky-armv5el along with native built
uImage, kernel-image, and kernel-headers. This use's the same kernel
source as the debian port, 2.6.26-omap1-oer61. Stable enough to build
new uImage and *.deb's. If dash ever install, make sure to remove it,
it will error on reading any init scripts.

As with the Debian project, I suggest you register it on
http://beagleboard.org/project.

It should be clear to people on this mailing list that the Debian and
Ubuntu on ARM projects are fantastically interesting, but not as
optimized for the ARM Cortex-A8 processor as Angstrom is today.
Hopefully the Debian and Ubuntu communities come to recognize OMAP3
and the Beagle Board project as something attractive for them to
utilize for better optimization of their distros and the effort that
you are starting in demonstrating existing builds of those distros on
the Beagle Board helps to promote that activity.

Also, http://beagleboard.org/project doesn't reflect any of the status
of commercial distros as of today, but I have no objections to adding
commercial links as long as this is clear in the description.

(Sorry about that last spam e-mail I let slip through. I was asleep
at the mouse.)

As with the Debian project, I suggest you register it on
BeagleBone Black Project Spotlight: Shield I/O - BeagleBoard.

Will do later today Jason, thought I had just solved an issue causing
frisky-armv6el-vfp to not boot the root file system, so i was going to
have a nice update.

It should be clear to people on this mailing list that the Debian and
Ubuntu on ARM projects are fantastically interesting, but not as
optimized for the ARM Cortex-A8 processor as Angstrom is today.

I agree, I just haven't found the best way to explain these issues to
the groups.

Debian is a wonderful project, with ton's of software available, and
very stable. However, everything but the kernel image is compiled for
armv4t. For basic non gui applications, this is not a big problem
(aka visually obvious). But once someone loads xorg and uses the
standard fbdev driver it really slows down (It's not really slow if
you consider the cortex-a8 is processing the 1280x720x32 screen in
real time, but i know everyone's first thought is 'slow'.) Once the
video drivers are released it will be interesting to revisit this.

Mojo's Ubuntu armv5el and armv6el-vfp port. I have to admit, i
haven't built/ran the Angstrom port yet ( other then borrowing the
kernel and patches ) so i don't know what this is built with, or how
fast it actually is. So i'm just guessing when i say the mojo's
armv6el-vfp port may be just as fast. However other then installing
the frisky-armv5el (based off ubuntu 7.04) port, installing the
other's is not simple at the moment. Once ubuntu 8.10 is released,
with gcc 4.3.x, it will be interesting to see if Mojo would add an
armv7-a port.

Considering how long it takes to rebuild the entire universe for
ubuntu, a gentoo port might be a more viable solution for that.. (even
with the three day weekend, i will stay away from that one.. :wink: )

Hopefully the Debian and Ubuntu communities come to recognize OMAP3
and the Beagle Board project as something attractive for them to
utilize for better optimization of their distros and the effort that
you are starting in demonstrating existing builds of those distros on
the Beagle Board helps to promote that activity.

I agree, and the more people bugging them about it the better! :wink: At
this point, i believe the Mojo community is the best inlet into this,
I've found a couple bugs, and will add bug reports for them. It would
be really nice to have them include a default beagleboard kernel and a
netboot initrd.gz image so the community can do easy netboot installs.

Also, BeagleBone Black Project Spotlight: Shield I/O - BeagleBoard doesn't reflect any of the status
of commercial distros as of today, but I have no objections to adding
commercial links as long as this is clear in the description.

(Sorry about that last spam e-mail I let slip through. I was asleep
at the mouse.)

Ps.. Jeremy and I are also hacking away with openocd, on a custom jtag board.

Info: JTAG device found: 0x0b7ae02f (Manufacturer: 0x017, Part:
0xb7ae, Version: 0x0)