Hi,<br><br>I'm working on kernel package for ARM devices. It's my bachelor thesis. I have dreamplug, so now im trying to get build dreamplug kernel subpackage. Currently i have problems with configuration, but i'm working on it. After that i'll probably work on beagle board subpackage..<br>
<br>If anybody has any suggestions for me I'll be glad to hear them. Any advice is appreciated.<br><br>Peter<br><br><div class="gmail_quote">On Fri, Oct 14, 2011 at 11:06 PM, <a href="mailto:rihoward1@gmail.com">rihoward1@gmail.com</a> <span dir="ltr"><<a href="mailto:rihoward1@gmail.com">rihoward1@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On Oct 14, 2011, at 1:07 PM, David A. Marlin wrote:<br>
<br>
> Gordan Bobic wrote:<br>
>> On 10/14/2011 07:05 PM, Brendan Conoboy wrote:<br>
>><br>
>>> On 10/14/2011 10:54 AM, Chris Tyler wrote:<br>
>>><br>
>>>> Note that the GuruPlug ships with a broken uboot, which uses the wrong<br>
>>>> machine identifier. To use a mainline kernel, you must munge the kernel<br>
>>>> machine ID or update the GuruPlug's uboot.<br>
>>>><br>
<br>
</div>The guruplug comes with a very old kernel, as do most if not all of the kirkwood boards, and does a lot of things differently from the mainline kernel.<br>
All you have to do is change a couple of uboot parameters to use a mainline kernel and it is well documented.<br>
<br>
setenv mainlineLinux yes<br>
setenv arcNumber xxxx where xxxx can be found at <a href="http://www.arm.linux.org.uk/developer/machines/" target="_blank">http://www.arm.linux.org.uk/developer/machines/</a> for the particular board.<br>
<br>
The mainline uboot from <a href="http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary" target="_blank">http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary</a> has support for number<br>
of kirkwood boards and more are being added. It is for most people non-trivial to update but there is documentation supplied by the board manufacturers that explains how to do it.<br>
<br>
I wonder if it would be possible to get the board suppliers to refresh the image they are installing in new items?<br>
<div class="im"><br>
<br>
>>> Ooh, good to know.<br>
>>><br>
>>><br>
>>>> The phrase "the kernel we're working with" caught my eye. Which kernel<br>
>>>> are we talking about?<br>
>>>><br>
>>> I'm specifically thinking of David Marlin's kernel as referenced here:<br>
>>><br>
>>> <a href="http://fedoraproject.org/wiki/Architectures/Fedora_ARM_Kernels" target="_blank">http://fedoraproject.org/wiki/Architectures/Fedora_ARM_Kernels</a><br>
>>><br>
>>><br>
>>>> (I've heard but have not verified that the Kirkwood and OMAP patch sets<br>
>>>> used to be pretty much mutually-exclusive; I haven't tried to build a<br>
>>>> unified kernel and hope this has been fixed).<br>
>>>><br>
>>> Yuck. I know David has been endeavoring to make his changes mesh easily<br>
>>> with additional parties adding their own pet board to the SRPM. Most of<br>
>>> our systems are omap and tegra based so we haven't seriously looked into<br>
>>> kirkwood support. If somebody wants to add kirkwood support they should<br>
>>> bear in mind your warning about the broken uboot.<br>
>>><br>
>><br>
>> I'm pretty sure that Kirkwood support required for the SheevaPlug has<br>
>> been in mainline since at least 2.6.35, possibly earlier. Whether OMAP<br>
>> patches break this, I don't know.<br>
>><br>
<br>
</div>Krkwood support for multiple boards is available in the mainline code.<br>
The following is what is supported in 3.0.3 :-<br>
<br>
CONFIG_MACH_DB88F6281_BP=y<br>
CONFIG_MACH_RD88F6192_NAS=y<br>
CONFIG_MACH_RD88F6281=y<br>
CONFIG_MACH_MV88F6281GTW_GE=y<br>
CONFIG_MACH_SHEEVAPLUG=y<br>
CONFIG_MACH_ESATA_SHEEVAPLUG=y<br>
CONFIG_MACH_GURUPLUG=y<br>
CONFIG_MACH_TS219=y<br>
CONFIG_MACH_TS41X=y<br>
CONFIG_MACH_DOCKSTAR=y<br>
CONFIG_MACH_OPENRD=y<br>
CONFIG_MACH_OPENRD_BASE=y<br>
CONFIG_MACH_OPENRD_CLIENT=y<br>
CONFIG_MACH_OPENRD_ULTIMATE=y<br>
CONFIG_MACH_NETSPACE_V2=y<br>
CONFIG_MACH_INETSPACE_V2=y<br>
CONFIG_MACH_NETSPACE_MAX_V2=y<br>
CONFIG_MACH_D2NET_V2=y<br>
CONFIG_MACH_NET2BIG_V2=y<br>
CONFIG_MACH_NET5BIG_V2=y<br>
CONFIG_MACH_T5325=y<br>
<br>
I have noticed that some changes to OMAP continue to go into the mainline ARM kernel source tree and tegra is very active at the moment. There has been some work to add support for additional kirkwood boards.<br>
See <a href="http://lists.infradead.org/mailman/listinfo/linux-arm-kernel" target="_blank">http://lists.infradead.org/mailman/listinfo/linux-arm-kernel</a><br>
<div><div></div><div class="h5"><br>
>> In fact, Kirkwood is one of the few SoCs that has complete support for<br>
>> all of the extras, too, in the mainline kernel, too (e.g. crypto engine).<br>
>><br>
> Someone built a 2.6.39 kernel for kirkwood (Dreamplug) by adding a<br>
> couple of patches to one of my earlier kernel SRPMs (which was also<br>
> tested on Panda/OMAP), but when we tried it on a 2.6.40 (3.0-based)<br>
> kernel SRPM the resultant image failed to boot.<br>
><br>
> I can probably dig up those packages if anyone who has a kirkwood system<br>
> wants to work on it.<br>
><br>
><br>
> d.marlin<br>
> =========<br>
><br>
> _______________________________________________<br>
> arm mailing list<br>
> <a href="mailto:arm@lists.fedoraproject.org">arm@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a><br>
<br>
_______________________________________________<br>
arm mailing list<br>
<a href="mailto:arm@lists.fedoraproject.org">arm@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>:wq<br>