All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm] u-boot-fslc maintainer?
Date: Fri, 02 May 2014 13:06:13 -0600	[thread overview]
Message-ID: <5363ECA5.8000804@mlbassoc.com> (raw)
In-Reply-To: <CAOMZO5AdLoH8QcRO7c7maVTF7NR6yz1fjdi=YsiyV1yaQB02sA@mail.gmail.com>

On 2014-05-01 17:19, Fabio Estevam wrote:
> On Thu, May 1, 2014 at 8:08 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I'm having some issues with U-Boot on my [own design] board
>> (clone of SabreLite) with the latest branch/patches.
>>
>> Where/who best to ask these questions?
>>
>> Bottom line: when I was using v2013.10, everything worked.
>> Now that I'm using v2014.01, the FEC ethernet does not work
>> on power-up (in U-Boot).  Once I boot into Linux (and reboot),
>> the FEC ethernet works fine in U-Boot.
>>
>> Any ideas?
>
> Try to run git bisect between v2013.10 and v2014.01 to find out the
> exact commit that gives you problems.
>

Tedious, but this did the job for me.  I narrowed it down to the
changes I had to make in reaction to this commit:

   commit 10fda48779fc86e74e4482cbc7667431237cf60c
   Author: Eric Nelson <eric.nelson@boundarydevices.com>
   Date:   Mon Nov 4 17:00:51 2013 -0700
       i.MX6DQ/DLS: replace pad names with their Linux kernel equivalents
       Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>

Once I figured out what I had done wrong, my boards work again.

Thanks for the pointer (which I should have thought of myself!)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2014-05-02 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 23:08 [meta-fsl-arm] u-boot-fslc maintainer? Gary Thomas
2014-05-01 23:19 ` Fabio Estevam
2014-05-02 19:06   ` Gary Thomas [this message]
2014-05-03 15:38     ` Eric Nelson

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=5363ECA5.8000804@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=meta-freescale@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.