Thanks Gilles.
Before I start messing around with the prepare-kernel.sh can someone
review the proposal please?
add --board flag:
tells the script about the target board. If unspecified, no board
specific patches will be applied.
suggest to modify prepare-kernel.sh in the following way:
- construct pre ipipe patch name:
patches/$board/ipipe-core-$linux_version-$board-pre-*
- construct post ipipe patch name similar to above
- if pre patch exist - apply before ipipe_patch
- if post patch exist - apply after ipipe_patch
This calls for board patch standards. Is there a standard for patch
names currently in place?
My I suggest ipipe-core-$linux_version-$board-{pre,post}-*
This above might not work if custom adeos patch is specified. Should we care?
Thanks,
Gregory
On 28 March 2014 14:34, Gilles Chanteperdrix
<[email protected]> wrote:
> On 03/28/2014 03:22 PM, Gregory Dymarek wrote:
>>
>> Ok, I think I'm on top of it. Will post all the patches once I test
>> them properly.
>>
>> Another question on the topic of PRE and POST patches. Is there a
>> reason why prepare-kernel.sh cannot invoke PRE and POST patches
>> automatically?
>>
>> I'm trying to get this into a buildroot and it does not support pre
>> and post patches. Also, I'm getting a push back on adding the support
>> for pre- and post- ipipe patches into buildroot.
>
>
> No reason except the fact that -pre and -post patches are a temporary
> solution while the support for the board is integrated into the mainline
> kernel. Now, given the evolution pace of ARM platforms, it seems we will
> always have -pre and -post patches, so it would make sense to add this
> support to prepare-kernel.sh. So, the answer to your question is "patch
> welcome".
>
>
> --
> Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
