From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Jackson Date: Fri, 12 Apr 2013 20:20:51 +0100 Subject: [U-Boot] How do I use AM335x eth1 rather than eth0 ? In-Reply-To: <20130412160544.GS9914@bill-the-cat> References: <5167E879.4060900@mimc.co.uk> <20130412160544.GS9914@bill-the-cat> Message-ID: <51685E93.2060805@mimc.co.uk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 12/04/13 17:05, Tom Rini wrote: > On Fri, Apr 12, 2013 at 11:56:57AM +0100, Mark Jackson wrote: > >> We have a dual Ethernet board (based on the BeagelBone) but with both Ethernet ports connected. >> >> I'm wanting to use eth1 (rather than eth0), so in my board.c file, I changed:- >> ... assuming that eth0 would now be ignored (as only 1 slave is configured). >> >> But (eg) dhcp still only responds on eth0 !?! >> >> What else do I have to change ? > > Good question, do you have both ports working in Linux yet? The EVM-SK > design supports two interfaces and I know the cpsw driver in the kernel > required some changes to support two. I strongly suspect similar > changes would be required in the U-Boot driver (I don't have any > specific links other than look at the vendor kernel tree). Well, I've realised I needed to change CONFIG_PHY_ADDR in my board config file. So the link up/down portion now works to PHY#2, but I'm still unable to ping anything from our board. I'm guessing there's some hard-coded assumptions in the cpsw.c driver. I've taken quick look at the Ethernet section of the TRM, but that's *waaaay* over my head !?! I've so far been unable to get Linux to see the 2nd port, and there is no "vendor kernel tree" ... I'm the vendor :-) Mark J.