<Playing some post-vacation catch-up> I just want to address this point real quick. Take a look at the board conversion patches, it's not a big deal to hook in to this, it's just a matter of calling the init function, on top of any "normal" hook up work you had to do.
-- Tom ________________________________________ From: Marek Vasut [marek.va...@gmail.com] Sent: Tuesday, August 30, 2011 12:19 AM To: u-boot@lists.denx.de Cc: Premi, Sanjeev; Rini, Tom Subject: Re: [U-Boot] [PATCH 9/9] OMAP3: Remove legacy mmc driver On Tuesday, August 30, 2011 06:59:24 AM Premi, Sanjeev wrote: > > -----Original Message----- > > From: u-boot-boun...@lists.denx.de > > [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Rini, Tom > > Sent: Tuesday, August 23, 2011 3:44 AM > > To: u-boot@lists.denx.de > > Subject: [U-Boot] [PATCH 9/9] OMAP3: Remove legacy mmc driver > > > > Now that all platforms have been migrated to the new MMC > > driver, remove > > the old one. > > > > Signed-off-by: Tom Rini <tr...@ti.com> > > --- > > > > drivers/mmc/Makefile | 1 - > > drivers/mmc/omap3_mmc.c | 570 > > > > ----------------------------------------------- > > > > drivers/mmc/omap3_mmc.h | 233 ------------------- > > 3 files changed, 0 insertions(+), 804 deletions(-) > > delete mode 100644 drivers/mmc/omap3_mmc.c > > delete mode 100644 drivers/mmc/omap3_mmc.h > > Similar patch was posted earlier in the month: > http://marc.info/?l=u-boot&m=131220851719468&w=2 > > You may still want to keep the "legacy" mmc driver. Should help > the new boards during early development. How? Really, protecting legacy stuff won't help anyone ... and if those people want it, they can pull it from git history. Cheers > > ~sanjeev > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
