All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Tim Cussins <timcussins@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Marvell sheeva support
Date: Wed, 21 Jul 2010 08:23:21 +0200	[thread overview]
Message-ID: <4C469259.3000708@domain.hid> (raw)
In-Reply-To: <1279623645.2187.35.camel@domain.hid>

Tim Cussins wrote:
>>> We can also provide you with a root filesystem for validating this platform.
> 
> That would be brilliant. I imagine I'll be iterating though uImages on
> an SD card loaded with your rootfs. Sound ok? Let me know how to obtain
> the rootfs (or better, show me how you prefer to do it, so I learn
> something! Ta.)

You will find the rootfs for orion SOCs, here:
http://www.xenomai.org/~gch/pub/rootfs-orion.tar.bz2

Edit etc/inittab to modify the serial console it needs (if it is not
/dev/ttyS0 running at 115200 bauds). The rootfs is meant to be booted by
NFS with the kernel IP auto-configuration, so, if you want to boot it on
an SD card, you will have to connect to the serial console once the
board is booted, and run "udhcpc" to configure the network by DHCP, or
use ifconfig to configure it by hand, then launch "telnetd" to be able
to connect to that board through telnet (if the kernel booted by NFS,
the telnet server will have been launched automatically)

In a first telnet session, run:
latency
In a second telnet session, if you have FCSE disabled, run:
dohell
if you have FCSE enabled, run:
noltp_hell 14400
(14400 means that you will generate some load during 14400s, that is 4
hours).
When either noltp_hell or dohell displays the line:
Listening on any address 5566
On the host, run:
netcat <target-ip> 5566 > /dev/null

Now you can return to the telnet session running latency. When the test
is finished the latency program should stop.

As for generating the root filesystem, it is not that it is really hard,
but it is a bit tedious. So, we made a tool to build a root filesystem
which suits our needs, that is testing Xenomai under load. I have just
finished working on a version of this tool (called mkrootfs, but I think
we should find a better name, as this one already exists) user-friendly
enough to be published. Currently, it is still lacking a documentation.
You will find it here:

http://www.xenomai.org/~gch/pub/mkrootfs.tar.bz2

However, to use it, you will need a few explanations. It is based on
Kbuild, the Linux kernel build system, so, it will build the same way.
Create a build directory, cd to it, then run:

make -C /path/to/mkrootfs O=`pwd` xconfig

Tweak the configuration. Then run:
make

It should build everything.

It does not download and patch the sources of the packages it uses, you
have to do this yourself, then pass the path where to look for them to
the configuration system. We use standard versions of the packages,
except for LTP, which we modified a bit to run on low-end platforms, and
which you can find here:

http://www.xenomai.org/~gch/ltp-20081130-patched.tar.bz2


>> You can also use the patch below as a starting point for your port:
>> http://download.gna.org/adeos/patches/tmp/adeos-ipipe-2.6.29-mv88f6290.patch
> 
> I've tried applying this to vanilla 2.6.29 and 2.6.29.6 - it doesn't
> apply cleanly (well, fails :P). Am I approaching this the wrong way?
> Also tried chucking the patch into the xenomai tree and getting
> prepare_kernel.sh to try: still no joy.

It probably does not apply to vanilla because vanilla has no support for
the Sheevaplug board. Or am I missing something?

-- 
					    Gilles.


  reply	other threads:[~2010-07-21  6:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 14:10 [Xenomai-help] Marvell sheeva support Tim Cussins
2010-07-15 11:53 ` Gilles Chanteperdrix
2010-07-15 16:11   ` Philippe Gerum
2010-07-20 11:00     ` Tim Cussins
2010-07-21  6:23       ` Gilles Chanteperdrix [this message]
2010-08-11 14:58         ` Tim Cussins
2010-08-11 15:25           ` Gilles Chanteperdrix
2010-08-11 16:33             ` Tim Cussins
2010-08-11 15:28           ` Philippe Gerum
2010-08-11 16:24             ` Tim Cussins
     [not found]               ` <1281544161.1730.23.camel@domain.hid>
2010-08-11 16:44                 ` Tim Cussins
2010-08-11 16:56                   ` Gilles Chanteperdrix
2010-08-12 15:04                     ` Tim Cussins
2010-08-12 15:11                       ` Gilles Chanteperdrix
2010-08-11 16:30             ` Philippe Gerum
2010-08-12 15:45           ` Tim Cussins
2010-08-12 15:58             ` Philippe Gerum
2010-08-12 16:03               ` Philippe Gerum
2010-08-12 16:21                 ` Tim Cussins
2010-08-16 11:00         ` Tim Cussins
2010-07-21  9:50       ` Philippe Gerum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C469259.3000708@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=timcussins@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.