From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by canuck.infradead.org with esmtps (Exim 4.72 #1 (Red Hat Linux)) id 1P3pau-0000gj-Jv for barebox@lists.infradead.org; Thu, 07 Oct 2010 12:29:09 +0000 Received: from octopus.hi.pengutronix.de ([2001:6f8:1178:2:215:17ff:fe12:23b0]) by metis.ext.pengutronix.de with esmtp (Exim 4.71) (envelope-from ) id 1P3par-0000TM-Qf for barebox@lists.infradead.org; Thu, 07 Oct 2010 14:29:05 +0200 Received: from jbe by octopus.hi.pengutronix.de with local (Exim 4.69) (envelope-from ) id 1P3par-0000HU-PX for barebox@lists.infradead.org; Thu, 07 Oct 2010 14:29:05 +0200 From: Juergen Beisert Date: Thu, 7 Oct 2010 14:28:52 +0200 Message-Id: <1286454535-695-1-git-send-email-jbe@pengutronix.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: [RFC] Add MMC support to barebox To: barebox@lists.infradead.org This patch is based on some work Sascha made already. I tried to bring in some light into the MCI framework routines as they are based on code from another project. Bear with me, if I didn't add useful comments all over the code. I just wasn't able to understand what happen... If someone has more knowledge about MCI cards, please take a look at the FIXME/TODOs and make me understand why the code does what it does. There is no regular user, yet. The first platform (S3C2440 based) I did the tests on, is not part of barebox (and will not) and the other platfrom (i.MX23 ChumbOne) is not yet part of barebox. But will coming soon. Regards, Juergen _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox