From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Stephan Kappertz <stephan.kappertz@kabelmail.de>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Raspberry and Beaglebone patches
Date: Fri, 03 May 2013 20:19:31 +0200 [thread overview]
Message-ID: <5183FFB3.1000006@xenomai.org> (raw)
In-Reply-To: <12E434B4-4F26-44AC-8D50-2CF70B5089E1@kabelmail.de>
On 05/03/2013 04:28 PM, Stephan Kappertz wrote:
>
> Am 02.05.2013 um 20:34 schrieb Gilles Chanteperdrix:
>
>> On 05/02/2013 02:19 PM, Stephan Kappertz wrote:
>>
>>>
>>> Am 16.04.2013 um 20:06 schrieb Gilles Chanteperdrix:
>>>
>>>> On 04/16/2013 12:26 PM, Stephan Kappertz wrote:
>>>>
>>>>> Am 15.04.2013 um 08:57 schrieb Gilles Chanteperdrix:
>>>>>
>>>>>>
>>>>>> Hi Stephan, Paul,
>>>>>>
>>>>>> we have a problem with the patches for Raspberry and
>>>>>> BeagleBone: they are based on the 3.2.21 patch, which we
>>>>>> know is broken. So, we can not really ship the next version
>>>>>> of Xenomai with these patches.
>>>>>>
>>>>>> There are two ways we could keep patches for these
>>>>>> machines: - you could send patches for 3.4 or 3.5, or even
>>>>>> 3.8 - we could backport the fixes to 3.2, but as already
>>>>>> discussed on this list, this would cost some time to
>>>>>> re-validate the 3.2 patch on all architectures. However, if
>>>>>> you do the backport, validate it on your side, I could
>>>>>> validate the result on my test boards, and we would release
>>>>>> a new version of the patch for 3.2 only for the ARM
>>>>>> architecture.
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>> -- Gilles.
>>>>>>
>>>>>
>>>>> Hi Gilles,
>>>>>
>>>>> there's a 3.8.7 branch available for beagleBone at
>>>>> https://github.com/beagleboard/kernel/tree/3.8.
>>>>>
>>>>> I can look into updating the beagleBone patch for that
>>>>> repository. Where do I find the latest ipipe patch for 3.8 on
>>>>> ARM?
>>>>
>>>>
>>>> ipipe-gch repository, for-core-3.8 branch.
>>>>
>>>> -- Gilles.
>>>>
>>>
>>> Hi Gilles, do you have a script to create the ipipe patch file?
>>> Can't find any in the pipe-gch repository.
>>
>>
>> It is not yet in the repository, if you want the definitive patch,
>> please wait a bit, the patch should be released soon.
>>
>>
>> -- Gilles.
>>
>
> Hi Gilles,
>
> I have created a ipipe post patch for the beagleBone kernel v3.8.10
> found here:
>
> https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8, branch
> am33x-v3.8
>
> Your pipe-gch repository is based on 3.8 while the upper repository
> is at 3.8.10. Thus I had to apply a few minor changes to the patch
> file created from your git. Are you going to rebase the ipipe patch
> to 3.8.10 or higher before releasing it?
I do not know, Philippe is going to make the patch, he will decide on
which version he rebases.
> If so, the beagleBone patch
> gets reduced to the post patch below:
Ok, several remarks:
- can not we put that code in the mainline kernel (meaning, does
soc_is_am33xx() exist in the mainline kernel, if it does not exist, can
not we add it?)
- the coding style for the tsc declaration is bad, braces are not put on
separate lines in the Linux kernel coding style;
- since the only difference between am33xx and other omaps is
OMAP_TIMER_CAPTURE_REG vs OMAP_TIMER_COUNTER_REG, why not put this in a
local variable and use it twice?
--
Gilles.
next prev parent reply other threads:[~2013-05-03 18:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 6:57 [Xenomai] Raspberry and Beaglebone patches Gilles Chanteperdrix
2013-04-15 10:52 ` Paul
2013-04-15 19:46 ` Gilles Chanteperdrix
2013-04-20 23:44 ` Paul
2013-04-21 0:01 ` Jason Kridner
2013-04-16 10:26 ` Stephan Kappertz
2013-04-16 18:06 ` Gilles Chanteperdrix
[not found] ` <F484004F-9908-449C-A4DA-CB73E47EE764@kabelmail.de>
[not found] ` <5182B1B5.1000107@xenomai.org>
2013-05-03 14:28 ` Stephan Kappertz
2013-05-03 18:19 ` Gilles Chanteperdrix [this message]
2013-05-03 20:41 ` Stephan Kappertz
2013-05-08 18:27 ` Gilles Chanteperdrix
2013-05-10 11:53 ` Stephan Kappertz
2013-05-10 13:21 ` Gilles Chanteperdrix
2013-05-10 14:43 ` Stephan Kappertz
2013-05-10 14:44 ` Gilles Chanteperdrix
2013-05-10 16:40 ` Stephan Kappertz
2013-05-10 16:48 ` Gilles Chanteperdrix
2013-05-10 17:02 ` Gilles Chanteperdrix
2013-05-13 10:37 ` Stephan Kappertz
2013-05-13 11:20 ` Stephan Kappertz
2013-05-14 6:41 ` Gilles Chanteperdrix
2013-05-14 6:50 ` Gilles Chanteperdrix
2013-05-14 7:33 ` Stephan Kappertz
2013-05-14 7:53 ` Gilles Chanteperdrix
2013-05-14 9:11 ` Stephan Kappertz
2013-05-14 9:20 ` Jan Kiszka
2013-05-14 9:44 ` Stephan Kappertz
2013-05-14 10:35 ` Jan Kiszka
2013-05-14 11:02 ` Gilles Chanteperdrix
2013-05-14 11:11 ` Jan Kiszka
2013-05-14 11:26 ` Gilles Chanteperdrix
2013-05-14 11:53 ` Jan Kiszka
2013-05-14 11:19 ` Stephan Kappertz
2013-05-14 11:26 ` Jan Kiszka
2013-05-14 18:30 ` Gilles Chanteperdrix
2013-05-15 7:34 ` Stephan Kappertz
2013-05-14 8:06 ` Stephan Kappertz
2013-05-13 11:22 ` Gilles Chanteperdrix
2013-05-13 11:52 ` Gilles Chanteperdrix
2013-05-13 22:49 ` Gilles Chanteperdrix
2013-05-18 15:04 ` Gilles Chanteperdrix
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=5183FFB3.1000006@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=stephan.kappertz@kabelmail.de \
--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.