From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Fri, 01 Jun 2012 13:00:58 -0600 Subject: [U-Boot] [PATCH] mmc: tegra: fix boards that used old CONFIG_TEGRA2_MMC build switch In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F379C4162B2@HQMAIL04.nvidia.com> References: <1338570686-29429-1-git-send-email-twarren@nvidia.com> <4FC9009D.5000506@wwwdotorg.org> <5FBF8E85CA34454794F0F7ECBA79798F379C4162B2@HQMAIL04.nvidia.com> Message-ID: <4FC9116A.20509@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 06/01/2012 12:09 PM, Tom Warren wrote: > Stephen Warren wrote at Friday, June 01, 2012 10:49 AM: >> On 06/01/2012 11:11 AM, Tom Warren wrote: ... >> Grep'ing for the symbols that got renamed in the current u-boot-tegra/next >> still shows a lot of hits. For MMC those are all include guards so it >> probably doesn't cause bugs. For SPI, there are some #defines in the driver >> that didn't get converted.. Should those fixes be included in this patch >> too? > > Current (as of right now) u-boot-tegra/next (which is where this patch lives) doesn't have any instances of CONFIG_TEGRA2_MMC nor CONFIG_TEGRA2_SPI that I can find. Were you using an older /next? All T20 boards build fine from /next w/MAKEALL -s tegra2. I can't test MMC on the Tamonten/Paz00/etc. boards since I don't have any, but I believe I've fixed all the TEGRA2_MMC instances so they should work fine. Yeah, I guess that's true. I was grep'ing for just TEGRA2_MMC/SPI/GPIO, not CONFIG_*.