From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Wed, 06 Oct 2010 15:54:37 +0200 Subject: [U-Boot] Mvbge driver broken on kirkwood platforms after ARM relocation In-Reply-To: <20101006133003.6D05C1539A0@gemini.denx.de> References: <1286230940-26976-1-git-send-email-albert.aribaud@free.fr> <4CAB9B40.7090008@free.fr> <4CAC0E62.8030101@free.fr> <20101006133003.6D05C1539A0@gemini.denx.de> Message-ID: <4CAC7F9D.8020904@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 06/10/2010 15:30, Wolfgang Denk a ?crit : > Dear Prafulla Wadaskar, > > In message you wrote: >> >> After rebasing to new ARM relocation code base and updating Kirkwood board support. >> I am unable to get my network driver through (mvgbe) >> >> Have you tested this on edminv2 platform? >> If it is working at your end? Can you please cross check the same with Kirkwood platform? I am positive that mvgbe driver works, because it initially did not on my edminiv2, and I traced the root cause to gd being trashed between board_init_f and board_init_r; that was fixed before I submitted this patch. I will test on the openrd platform. > Try running the "dcache off" command before accessing the network and > see if this changes anything. Good suggestion. FTR, I did all of my tests with dcache off only -- never tried to activate any cache. > Best regards, > > Wolfgang Denk Amicalement, -- Albert.