From: vattipalli <praveen.v@easyarm.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] porting xenomai to 3.2 kernel using SOC Ti Am3359
Date: Thu, 24 Apr 2014 12:32:43 +0530 [thread overview]
Message-ID: <5358B713.9040300@easyarm.com> (raw)
In-Reply-To: <535640F8.1040805@xenomai.org>
Hi Gilles,
Thanks for your help.
As per your suggestion, instead of working on linux-3.2 kernel for
Am3359, I want to configure Xenomai for 3.13 kernel. Can i get any
patches for kernel 3.13 kernel. Because I have gone through
ksrc/arch/arm/patches/README in Xenomai 2.6.3 sources, I found patches
for 3.8 kernel for Beaglebone.
Thanks & Regards
Praveen
On Tuesday 22 April 2014 03:44 PM, Gilles Chanteperdrix wrote:
> On 04/22/2014 07:08 AM, vattipalli wrote:
>> hi, I am working on Ti Am3359 processor with linux-3.2 kernel. I am
>> trying to port Xenomai. I have applied ipipe-core-3.2.21-arm-4.patch
>> patch, and compiled the kernel. But when booting uImage it hanged at
>>
>> Uncompressing Linux... done, booting the kernel. I could not see any
>> console after this.
> The I-pipe patch for Linux 3.2 does not support Am33xx processors. And
> in fact has known bugs, so is not recommended at all. We have more
> recent patches for Linux 3.8 and Linux 3.10. See the help for beaglebone
> in ksrc/arch/arm/patches/README in Xenomai 2.6.3 sources.
>
>
>> But the above patch Support for CSR SiRFSoC ARM
>> Cortex A9 Platform.
> I do not understand this sentence.
>
>> Could i get any patch for ARM Cortex A8
>> Platform(Ti AM3359) for linux-3.2 kernel.
> No.
>
next prev parent reply other threads:[~2014-04-24 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 5:08 [Xenomai] porting xenomai to 3.2 kernel using SOC Ti Am3359 vattipalli
2014-04-22 10:14 ` Gilles Chanteperdrix
2014-04-24 7:02 ` vattipalli [this message]
2014-04-24 10:29 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2014-04-22 4:40 vattipalli
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=5358B713.9040300@easyarm.com \
--to=praveen.v@easyarm.com \
--cc=gilles.chanteperdrix@xenomai.org \
--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.