On 07.04.2013, at 22:11, Roger Whittaker wrote:
On Sun, Apr 07, 2013 at 07:56:30PM +0200, Alexander Graf wrote:
Is there a general user-level howto on this stuff anywhere that you could recommend? (i.e. when you need to set an arcNumber, when you need to do this .dts / .dtb stuff).
As this changes pretty much any day, I don't think you'll find any sensible howto. The general rule of thumb is that old code always based off of arcNumbers. Very new code only runs with dtb. Code that had arcNumbers upstream, but got converted to dtb may work with both. Keep in mind that the important notion here is _upstream_. If someone did a downstream port somewhere, you don't get any guarantees what happens upstream with the same target.
I have a dreamplug and I've been confused in the process of trying to get modern versions of Linux to run on it, somewhat similarly to the problems described in this thread. Fedora 18 works fine with the original u-boot, but not with a new u-boot (then it hangs after "Uncompressing Linux..." ).
Odd... Does the new u-boot change the arcNumber? Some times people chose random numbers and only later got an official ID reserved. So maybe your old u-boot version exposes an unofficial arcNumber - which your kernel expects - but new u-boot exposes a new official arcNumber, that your kernel doesn't know about?
Ideally of course I would like to get openSUSE running on it, with an up-to-date u-boot.
Very happy to hear that :). Marrying embedded ideology with a general purpose distro obviously is nothing for the faint of heart. Also keep in mind that the dreamplug is an ARMv5 device. As such, it again lives under even different rules than ARMv7 ones. For ARMv5 devices, I don't think anyone's really going through efforts to convert anything to device trees. At least I'm not aware of any efforts, but I like to be proven wrong :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org