From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Paul <paul@crubille.lautre.net>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Linux port to ARM Allwinner A13
Date: Wed, 10 Apr 2013 00:05:53 +0200 [thread overview]
Message-ID: <516490C1.9070608@xenomai.org> (raw)
In-Reply-To: <513E5AB9.3060203@crubille.lautre.net>
On 03/11/2013 11:29 PM, Paul wrote:
> Hello Gilles,
>
> On 11/03/2013 08:47, Gilles Chanteperdrix wrote:
>> On 03/11/2013 10:15 AM, Paul wrote:
>>
>>> Hello,
>>>
>>> Here are pre and post patch for xenomai on sun5i (allwinner A13). It
>>> should work for sun4i (allwinner A10) too, but is not tested for this
>>> proc.
>>>
>>> The tested kernels are
>>>
>>> wget
>>> https://github.com/linux-sunxi/linux-sunxi/archive/sunxi-v3.4.24-r1.tar.gz
>>>
>>>
>>
>> and
>>
>>> wget
>>> https://github.com/linux-sunxi/linux-sunxi/archive/sunxi-v3.4.24-r2.tar.gz
>>
>>
>>
>> Fine,
>>
>>
>> but the pre patch touches a lot of things which I believe it
>> should not be touching, like entry.S.
>>
>> Is it because your patch is based on 3.2.24 and not 3.2.21? If that is
>> the case, the post patch should undo the changes made by the pre patch.
>
> The patch is based on 3.4.24 and the ipipe patch is noted to be a 3.4.6,
> but there is no such kernel for the sunxi.
> So most of the patch fail are from the different linux version but
> curiously, vfp/entry.S are differents in the sunxi3.4.24 and in the
> vanill3.4.24..
>
>>
>> The coding style you use is not really the kernel coding style, see:
>> Documentation/CodingStyle
> OK, I would do it.
>>
>> For sunxi_enable_irqdesc/sunxi_disable_irqdesc, you could use a switch
>> case, or even better, define a macro SW_INT_SRCPRIO_REG(n) that gives
>> the address of the nth register, and avoid the ifs completely.
> strange, but i copy/paste this part of code from the sunxi part (and
> found that bad):
> My first idea was to mask, shift and use the result as index in a
> register index.
> To stay close to the actual style, ok to use switch (it is not a so
> performance critical part).
>>
>> You do not need to manually call enable_irqdesc for the timer irq, it
>> should be called automatically. Maybe your problem is that your
>> "pic_muter_init" function is called too late, if that is the case, you
>> should call it in the function which declares the Linux timer, this one
>> should be called early enough.
> I add this in an attempt to solve a problem which have nothing to do
> with it, and it stay here.
> To be removed.
>>
>> ipipe_ns_delay is ugly, you can probably get away much more simply with
>> ipipe_tsc_get, or can not you simply wait for a PLL lock bit or
>> somehting? If you want to maintain ipipe_ns_delay, plase call it
>> ipipe_mach_something, and fix the coding style.
> I dont know about ipipe_tsc_get, so i will test with it.
>>
>> Please avoid dead code, and C++ comments. And the cartouches.
>
>
> FROM THE FOLLOWING MAIL:
>> Also, you seem to have duplicated the timer code, this should not be
>> needed, right?
> The initialisation is very close, but i think the linux-sunxi
> timer_set_mode is broken.
Hi Paul,
do you plan to send revised pre and post patches in say, the next few weeks?
Regards.
--
Gilles.
next prev parent reply other threads:[~2013-04-09 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 0:11 [Xenomai] Linux port to ARM Allwinner A13 Paul
2013-02-25 22:28 ` Gilles Chanteperdrix
2013-03-11 9:15 ` Paul
2013-03-11 7:47 ` Gilles Chanteperdrix
2013-03-11 8:15 ` Gilles Chanteperdrix
2013-03-11 22:29 ` Paul
2013-04-09 22:05 ` Gilles Chanteperdrix [this message]
2013-03-11 22:47 ` Paul
2013-03-12 4:56 ` Gilles Chanteperdrix
2013-03-12 5:06 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2013-05-06 12:56 kunming yang
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=516490C1.9070608@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=paul@crubille.lautre.net \
--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.