From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <512BE5A2.3090505@xenomai.org> Date: Mon, 25 Feb 2013 23:28:50 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <512BFD9E.5010501@crubille.lautre.net> In-Reply-To: <512BFD9E.5010501@crubille.lautre.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai] Linux port to ARM Allwinner A13 List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Cc: xenomai@xenomai.org On 02/26/2013 01:11 AM, Paul wrote: >=20 > Here is a first port for OLINUXINO A13 board. >=20 > http://www.crubille.lautre.net/xenomai_sun5i/ipipe-linuxsun5i-3.4.24.be= ta.patch >=20 > and apply the standart xenomai-2.6.2.1 procedure on a sunxi linux kerne= l=20 > from : > "git clone git://github.com/linux-sunxi/linux-sunxi.git -b sunxi-3.4" Hi, good news the I-pipe patch for ARM is ported to yet another board! If you wish the patch to be distributed with Xenomai, please generate a -pre and -post patches. If you generate pre and post patches, we can update the I-pipe patch with your pre and post patches remaining valid. If you do otherwise, your patch will bitrot fast. Since I have been talking about it so many times, I guess we should provide a script to generate the -pre and -post patches. >=20 > I think that the A10/A13 port in the official linux tree is still too=20 > unstable to port on it. >=20 >=20 > The patch is a basic but functionnal version. I attempt to use priority= =20 > interrupt, but go in trouble. > If i can have comments about this point? Probably not much more than what you can find in the porting guide. >=20 > If somebody is interested in it for A10, it is very easy to adapt, and = i=20 > can do it and send the patch. >=20 > Paul Crubill=C3=A9 >=20 > -----------------------------------------------------------------------= ---------------------------- >=20 > Running it, i get >=20 >=20 > latency -t 2 -p 100 > =3D=3D Sampling period: 100 us > =3D=3D Test mode: in-kernel timer handler > =3D=3D All results in microseconds > RTT| 00:00:01 (in-kernel timer handler, 100 us period, priority 99) > RTH|----lat min|----lat avg|----lat max|-overrun|---msw|---lat=20 > best|--lat worst > RTD| 5.583| 6.265| 11.167| 0| 0| 5.583| = =20 > 11.167 > RTD| 6.125| 6.258| 10.917| 0| 0| 5.583| = =20 > 11.167 > RTD| 5.500| 6.270| 12.000| 0| 0| 5.500| = =20 > 12.000 >=20 >=20 > "lat worst" is mostly under 20 us but can go up for 30 ns. >=20 > latency -p 100 > =3D=3D Sampling period: 100 us > =3D=3D Test mode: periodic user-mode task > =3D=3D All results in microseconds > warming up... > RTT| 00:00:01 (periodic user-mode task, 100 us period, priority 99) > RTH|----lat min|----lat avg|----lat max|-overrun|---msw|---lat=20 > best|--lat worst > RTD| 11.999| 12.708| 21.333| 0| 0| 11.999| = =20 > 21.333 > RTD| 12.624| 12.791| 21.541| 0| 0| 11.999| = =20 > 21.541 > RTD| 12.458| 12.791| 26.458| 0| 0| 11.999| = =20 > 26.458 >=20 > "lat worst" is mostly under 40 us but can go up for 80 ns. Tests done without load are meaningless, try xeno-test or dohell. --=20 Gilles.