From: Gary Thomas <gary@mlbassoc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Missing ethernet
Date: Thu, 19 Apr 2012 08:49:14 -0600 [thread overview]
Message-ID: <4F9025EA.2090209@mlbassoc.com> (raw)
In-Reply-To: <00a201cd1e33$d14b97d0$73e2c770$@pont@sdcsystems.com>
On 2012-04-19 07:53, Andy Pont wrote:
> Gary wrote...
>
>> I'm trying to update U-boot on my board from v2011.06 to v2011.12
>> It's an OMAP 3530, much like the BeagleBoard, with SMSC911x networking.
>
> So not a BeagleBoard then but something different.
>
> Is the board you are using one of the boards supported in the mainline
> U-Boot tree or is it an out-of-tree port? If it is in mainline then have
> you chosen the correct configuration to use?
It's my own board, not in the mainline.
>
>> I've looked through the 'bootm' path and I can't see what might
>> have changed that would cause such behaviour. As far as I can
>> tell, everything else is working in Linux with the new U-Boot,
>> just not the SMSC device.
>
> If you try to use TFTP in U-Boot does that work? If not then I would guess
> there is a configuration issue with the devices that you have enabled in
> U-Boot rather than it being an issue with the bootm command.
As I said, U-Boot works fine. The problem comes when Linux boots.
I've bisected it down to this change:
commit 81bdc155c72ef9e093b388b90c58d8134d870976
Author: Sanjeev Premi <premi@ti.com>
Date: Thu Sep 8 10:47:25 2011 -0400
omap: gpio: Use generic API
That let me figure out the problem - I had to modify my board code
for the new GPIO functions and somehow that's where the problem is.
Still working out the details, but now I know where to look.
Thanks for the help
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2012-04-19 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 12:45 [U-Boot] Missing ethernet Gary Thomas
2012-04-19 13:44 ` Gary Thomas
2012-04-19 13:53 ` Andy Pont
2012-04-19 14:49 ` Gary Thomas [this message]
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=4F9025EA.2090209@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox