From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>
Cc: yocto@yoctoproject.org
Subject: Re: About running old kernels with Yoctoo 1.2 or 1.3
Date: Wed, 24 Apr 2013 08:53:31 -0400 [thread overview]
Message-ID: <5177D5CB.8060706@windriver.com> (raw)
In-Reply-To: <364D31930BDB974AB40E22C5C2E584ED011E6155@asterix.SPINETIX.local>
On 13-04-24 06:46 AM, Diego Santa Cruz wrote:
> Hi there,
>
> We are starting the development of a product based on TI DM814x SoC and
> considering using Yocto to base our development on.
>
> Unfortunately, TI does has only included support for this SoC on a derivative
> of the 2.6.37 kernel and has not pushed the SoC specifics upstream to
> mainline, so we are stuck to use that kernel as we cannot engage in porting
> all the support to a newer kernel at this time.
>
> I am new to Yocto, but as far as I got from the documentation versions 1.2
> and 1.3 use a 3.4 kernel as the supported kernel. Would Yocto work with a
> 2.6.37 kernel or are new features that have been introduced in newer kernel
> version required to run Yocto 1.2 or 1.3?
Each Yocto release uses a sliding set of kernel's that have had at least
some level of testing with the associated userspace of the release.
1.4 is: 3.2, 3.4 and 3.8
1.3 was: 3.4, 3.2 and 3.0
1.2 was: 3.2, 3.0 and 2.6.37
But obviously, the linux kernel has a very stable userspace ABI, so there
shouldn't be any big compatibility issues with other kernel versions.
It's just that we don't know for sure.
It is true that each of these releases with have a linux-libc-headers
that is newer than the 2.6.x kernel you are talking about, which could
expose syscalls or other interfaces to userspace that aren't supported
in your kernel, but this typically degrades gracefully and the issue
detected when you try your applications.
Cheers,
Bruce
>
> Sincerely,
>
> Diego
>
> --
> Diego Santa Cruz, PhD
> Technology Architect
> _________________________________
> SpinetiX S.A.
> Rue des Terreaux 17
> 1003, Lausanne, Switzerland
> T +41 21 341 15 50
> F +41 21 311 19 56
> diego.santacruz@spinetix.com
> http://www.spinetix.com
> http://www.youtube.com/SpinetiXTeam
> _________________________________
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-04-24 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:46 About running old kernels with Yoctoo 1.2 or 1.3 Diego Santa Cruz
2013-04-24 12:53 ` Bruce Ashfield [this message]
2013-04-24 13:35 ` Paul Eggleton
2013-04-25 12:27 ` Diego Santa Cruz
2013-04-25 13:03 ` Burton, Ross
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=5177D5CB.8060706@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=Diego.SantaCruz@spinetix.com \
--cc=yocto@yoctoproject.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.