All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
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: Sat, 17 Aug 2013 17:45:43 -0400	[thread overview]
Message-ID: <20130817214543.GS4931@edge> (raw)
In-Reply-To: <CAFZh4h8gDV9r6PzrANuj4ZWJCnpibh5DtK4OmoYqwO_vAdY-_g@mail.gmail.com>

On Fri, Aug 16, 2013 at 05:39:49PM -0400, Brian Hutchinson wrote:
> I can confirm that the Kevin Hilman mailbox patch that I posted the URL to
> on the e2e site fixes the mbox problem and my 2.6.37 kernel built with the
> OE Core toolchain (gcc 4.8) does in fact boot now!  I have a login prompt!

BTW, didn't I tell you to look for a possible fix in one of those TI81x repos 
on arago-project.org? :) It was right there, the third from the top!

http://arago-project.org/git/projects/?p=linux-dvr-rdk-dm81xx.git;a=commitdiff;h=b5c066e7c670e830c322693b2c9da65508c189b2


> So to recap.  Sakoman head.S patch, the two memset patches Khem mentioned,
> and this Hilman mailbox patch is what I applied.
> 
> Thank you guys for putting up with me :)

Congratulations, you persistence has paid off! :)

Looking forward to seeing patches from you, along with taking maintainership 
of TI81x platform in meta-ti... :)

-- 
Denys


  parent reply	other threads:[~2013-08-17 21:45 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
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 [this message]
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=20130817214543.GS4931@edge \
    --to=denys@ti.com \
    --cc=b.hutchman@gmail.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.