<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">i think the openmoko freerunner is what u need to develop on:) <br><br><br>--- On <b>Fri, 10/9/09, Stuart Winter <i><m-lists@biscuit.org.uk></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Stuart Winter <m-lists@biscuit.org.uk><br>Subject: Re: [ARMedslack] Question/suggestions regarding ARMedslack<br>To: "Slackware ARM port" <armedslack@lists.armedslack.org><br>Date: Friday, October 9, 2009, 3:22 AM<br><br><div class="plainMail"><br>Hi Thomas<br><br>> enterprise-grade VPN devices out of SheevaPlugs (implementing HA,<br>> Atateful failovers, Firewall, QoS on a single vlan-tagged interface).<br><br>Cool. Have you looked at the OpenRD which has 2Gbit interfaces?<br>They're more expensive than the SheevaPlug and the kernel support isn't<br>finished yet, but I
plan to make ARMedslack installable on that too.<br><br>> used is 2.6.31.1. Is there any plan at using the 2.6.32 kernel for the<br>> next release,<br><br>There won't be a Slackware ARM 13.0 release because the EABI port is too<br>new and untested -- I only completed it last month; whilst it's been<br>totally stable for me during development, I expect there to be problems<br>I don't yet know about.<br>Slackware 13.1 may be the next release if I think it's stable enough by<br>that time. For the time being, Slackware ARM -current will keep in sync<br>with Intel -current.<br><br>Slackware ARM usually has the latest stable kernel though, which usually<br>isn't in sync with Slackware x86 because as you say, the newer Kernels<br>usually contain ARM fixes.<br><br>> would feel much more comfortable using a cross-compile environment - I<br>> used to run one from a PowerPC (YDL) for my OpenWRT router and it was<br>> pretty nice. If there's no
documentation specific to ARMEdslack I will<br>> build one as I'd like to create images from my dev platform (x86) and<br>> use them straight in Qemu/Sheeva (I'll probably hack the installer too...).<br><br>I'm not sure what you mean here. Why would you need to do anything to the<br>installer? The installer is not related to any compilation environment.<br><br>ARMedslack's packages are compiled on a SheevaPlug (or what ever machine<br>is free which is the correct release and has the most up to date<br>installation), and using distcc is sent to a cluster of x86 machines<br>running a cross compiler that has the identical versions of glibc,<br>binutils and gcc as the Slackware ARM host. So I get the benefits of<br>having fast compilation times and having the packages work correctly.<br><br>If you're building an entire OS, cross compiling really isn't much fun<br>because many packages' build systems aren't made to cross compile so
you'd<br>have to modify them. The best part is when the Makefile tries to execute<br>a binary just compiled in order to process some data -- an example of<br>which is ncurses. This is why the first ARMedslack was built inside of<br>"Scratchbox" - www.scratchbox.org<br><br>I don't know of any distribution apart from Emdebian, which does not build<br>their packages natively.<br><br>> Also it looks like the kernel support UBIFS but there's no instructions<br>> for using it. IMHO it should not only be documented but also the<br>> recommended filesystem as it is much better in many technical aspects.<br><br>You're talking about installation of the OS onto the NAND flash on the<br>SheevaPlug? I don't know how to support that for a couple of reasons:<br> 1. I didn't spend enough time looking<br> 2. The NAND on the SheevaPlug is 512MB in size which isn't enough to<br> put a full installation of Slackware (~4GB) on
to. A full<br> installation is the recommended way to install Slackware.<br> Therefore I'd have to maintain a list of packages of a slimmed<br> down installation.<br><br>If somebody wanted to maintain a list of packages that could fit inside<br>512MB and still leave enough space for the running system, then the "tag<br>files" could be added to the installer image and presented as an<br>installation option.<br>I'd *like* to be able to do it because I believe it'd be useful<br>but I don't have time to maintain it.<br><br>> PS: Could the mailing list be linked to from the main ARMedslack page?<br>> I'm not sure if I missed something but I had to do a Google search to<br>> find it.<br><br>It is on the front page of www.armedslack.org.<br><br>-- <br>Stuart Winter<br>Slackware ARM: www.armedslack.org<br>_______________________________________________<br>ARMedslack mailing list<br><a
ymailto="mailto:ARMedslack@lists.armedslack.org" href="/mc/compose?to=ARMedslack@lists.armedslack.org">ARMedslack@lists.armedslack.org</a><br><a href="http://lists.armedslack.org/mailman/listinfo/armedslack" target="_blank">http://lists.armedslack.org/mailman/listinfo/armedslack</a><br></div></blockquote></td></tr></table><br>