From: Denys Dmytriyenko <denys@ti.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>,
Chris Larson <clarson@kergoth.com>
Subject: Re: Stumped. Can't get 2.6.37 TI kernel to boot when built with toolchain from denzil or Linaro gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/
Date: Thu, 15 Aug 2013 15:34:28 -0400 [thread overview]
Message-ID: <20130815193427.GJ2190@edge> (raw)
In-Reply-To: <CAFZh4h9xR44AvSW91eg_ecH0kR=760e5v1MC97r4hsjaB09Htw@mail.gmail.com>
On Thu, Aug 15, 2013 at 03:26:55PM -0400, Brian Hutchinson wrote:
> On Thu, Aug 15, 2013 at 3:06 PM, Denys Dmytriyenko <denys@ti.com> wrote:
>
> >
> > Yes, it is often a PITA to get old kernels build ...
> >
>
> What do you mean "old kernels" It is from a TI PSP released not that long
> ago! Wink, wink. I'd love to use a 3+ kernel, know where I can find one ;)
So, cross-referencing the 2.6.37 release date of January 4, 2011 against gcc
releases shows that you can only expect 4.4 or 4.5 to work properly out of
the box w/o patching... :)
And I have already answered the "newer TI81x kernel" question many times,
including the last email in this thread :)
--
Denys
next prev parent reply other threads:[~2013-08-15 19:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 15:52 Stumped. Can't get 2.6.37 TI kernel to boot when built with toolchain from denzil or Linaro gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/ Brian Hutchinson
2013-08-15 16:25 ` Chris Larson
2013-08-15 19:06 ` Denys Dmytriyenko
2013-08-15 19:14 ` Brian Hutchinson
2013-08-15 19:26 ` Brian Hutchinson
2013-08-15 19:34 ` Denys Dmytriyenko [this message]
2013-08-15 19:39 ` Brian Hutchinson
2013-08-15 19:10 ` Brian Hutchinson
2013-08-15 19:22 ` Denys Dmytriyenko
2013-08-15 19:32 ` Brian Hutchinson
2013-08-15 21:14 ` Brian Hutchinson
2013-08-15 21:32 ` Khem Raj
2013-08-15 21:41 ` Brian Hutchinson
2013-08-15 21:48 ` Brian Hutchinson
2013-08-15 21:33 ` Brian Hutchinson
2013-08-16 15:12 ` Brian Hutchinson
2013-08-16 15:37 ` Khem Raj
2013-08-16 16:25 ` Brian Hutchinson
2013-08-16 20:58 ` Brian Hutchinson
2013-08-16 21:33 ` Khem Raj
2013-08-16 21:04 ` Brian Hutchinson
2013-08-16 21:39 ` Brian Hutchinson
2013-08-16 21:44 ` Maupin, Chase
2013-08-16 21:46 ` Brian Hutchinson
2013-08-16 21:59 ` Khem Raj
2013-08-21 1:42 ` Brian Hutchinson
2013-08-21 4:11 ` Khem Raj
2013-08-21 16:51 ` Brian Hutchinson
2013-08-22 2:46 ` Denys Dmytriyenko
2013-08-22 15:23 ` Brian Hutchinson
2013-08-22 15:38 ` Denys Dmytriyenko
2013-08-22 17:08 ` Brian Hutchinson
2013-08-22 18:41 ` Brian Hutchinson
2013-08-22 18:54 ` Denys Dmytriyenko
2013-08-22 19:35 ` Brian Hutchinson
2013-08-22 20:13 ` Brian Hutchinson
2013-08-16 22:00 ` Khem Raj
2013-08-17 21:45 ` Denys Dmytriyenko
2013-08-17 22:20 ` Brian Hutchinson
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=20130815193427.GJ2190@edge \
--to=denys@ti.com \
--cc=b.hutchman@gmail.com \
--cc=clarson@kergoth.com \
--cc=meta-ti@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.