I have uploaded a testing Image that should work on DreamPlug and GuruPlug+
Here is the wiki page about it: http://wiki.ipfire.org/en/hardware/arm/kirkwood
Happy testing and give many feedback.
--
Arne Fitzenreiter
----------------------------------------------
mailto:arne@fitzenreiter.de
http://www.fitzenreiter.de
ICQ: 285-193-731
----------------------------------------------
Tel: +49 179/8603400 (Mo-Do 17-22 Uhr)
Tel: +49 36337/18300 (Wochendende)
sip://493633718300@warriors.homedns.org
----------------------------------------------
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Hi,
i have managed to build a booting kernel that boot on dreamplug. The network schould work but wlan and bluetooth are not supported yet. (There is a missing driver (uAP) and some firmware problems)
All other hardware should work. So i will build a new Image with this kernel...
If you want already test here http://people.ipfire.org/~arne_f/testing/kirkwood/ are the kernel image, ramdisk and modules.
Arne
--
Arne Fitzenreiter
----------------------------------------------
mailto:arne@fitzenreiter.de
http://www.fitzenreiter.de
ICQ: 285-193-731
----------------------------------------------
Tel: +49 179/8603400 (Mo-Do 17-22 Uhr)
Tel: +49 36337/18300 (Wochendende)
sip://493633718300@warriors.homedns.org
----------------------------------------------
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Hello guys,
this is a short mail to inform you all about the current status of the
ARM port. The discussion has been done behind closed doors and it is now
time to move it to that list.
What has been done so far:
As IPFire (or distributions in general) does not support
cross-compilation it was important to create a toolchain that is able to
compile the whole distribution on the designated platform.
We used Debian (Lenny) for that and had to upgrade Glibc, binutils, GCC
and the kernel headers to achieve support for EABI. Designated platform
is armv5tel-unknown-linux-gnueabi.
Arne focussed on the kernel configuration that needed to be optimized to
compile at all and I fixed various errors in the userspace area.
Currently, we once compiled the whole distributions with exception of a
couple of addon packages which did not compile in the first place and
have not been reviewed by me or Arne, yet. Because of some experiments,
crashes and messing around with the build environment, the final build
wasn't really clean and so we decided to restart it once again and go on
after that with the creation of the first image.
If everything goes well, this won't be a huge deal and done by the
beginning of the next week, as the build is expected to take at least
until Saturday evening (Europe time).
A big question that is still unanswered:
ARM is not very well standardized in the way, that there are plenty of
"sub-architectures" (I have no idea how to call that) like TI OMAP,
Marvel Kirkwood... For all of them, there is a configuration option in
the Linux kernel that makes the kernel capable of running on that
hardware. So, Rod, do you have any information about a common kernel
that is able to run on all of the platforms (it's still ARM, isn't it?)
or if we have to build a set of kernels to support various boards. The
latter wouldn't be a very good idea because compiling a kernel on ARM
takes about 6 hours.
For now, the code is living here:
http://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/a…
It will move to the main branch when it was cleaned up a bit and
compiles properly.
Please check it out and try to build it yourself to resolve bugs.
Michael
I had build a booting kernel and bootet the IPFire userspace environment. But at the moment this kernel has no IPTables support. (so it cannot act as nat router) My next task is to search the failing configuration option that prevent the first configuration try (very similar to i586 config) from booting. But this need much time because i had to change some settings, compile and try to boot.
But i can say that the proxy is working (I surf via the guruplug at the moment)
Arne
--
Arne Fitzenreiter
----------------------------------------------
mailto:arne@fitzenreiter.de
http://www.fitzenreiter.de
ICQ: 285-193-731
----------------------------------------------
Tel: +49 179/8603400 (Mo-Do 17-22 Uhr)
Tel: +49 36337/18300 (Wochendende)
sip://493633718300@warriors.homedns.org
----------------------------------------------
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
Documentation for the DreamPlug ARM device that we are trying to get
IPFire running on is located at:
http://people.ipfire.org/~rrodolico/DreamPlug_Documentation_and_Images/
This is all public information that I downloaded from links in the
small, one page document that GlobalScale sent with the DreamPlug. Once
we get a working Fedora image that will run on the DreamPlug, I'll try
to put it out there also.
I did not modify filenames, so some of them have embedded spaces. Sorry
if that bothers anyone.
Also, be aware. The documents are in some places incorrect. I am working
on modified documents, but will not have them finished for a while.
Also, documents are written based on the author's experiences, so some
reference Debian, others reference Fedora, and still others reference
Windows (for connecting to the DreamPlug using the JTag module).
Rod
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
Hello,
this mailing list is for developers who are working on the ARM port of
the IPFire distribution.
For the moment, this port is unofficial and not supported in that way
the i586 version is.
We appreciate any contribution by either developers and testers who want
to improve the distribution as well as hardware vendors who donate
hardware.
--
Michael Tremer <michael.tremer(a)ipfire.org>
IPFire.org