From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Thomas Date: Thu, 19 Apr 2012 08:49:14 -0600 Subject: [U-Boot] Missing ethernet In-Reply-To: <00a201cd1e33$d14b97d0$73e2c770$@pont@sdcsystems.com> References: <4F9008D5.40708@mlbassoc.com> <00a201cd1e33$d14b97d0$73e2c770$@pont@sdcsystems.com> Message-ID: <4F9025EA.2090209@mlbassoc.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 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 ------------------------------------------------------------