Hi Simon,
On Mon, Mar 14, 2011 at 10:28 AM, Simon Horman wrote:
> Hi Magnus,
>
> are the following also sh7372 specific?
>
> #define SDHI1_BASE (void __iomem *)0xe686
> #define SDHI_BASE SDHI1_BASE
Yes, you want to specify the base address of the SDHI hardware blo
Hi Magnus,
are the following also sh7372 specific?
#define SDHI1_BASE (void __iomem *)0xe686
#define SDHI_BASESDHI1_BASE
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo i
On Thu, Mar 10, 2011 at 05:07:17PM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Thu, Mar 10, 2011 at 4:58 PM, Simon Horman wrote:
> > This allows a ROM-able zImage to be written to eSD and for SuperH Mobile
> > ARM to boot directly from the SDHI hardware block.
> >
> > This is achieved by the Mas
Hi Simon,
On Thu, Mar 10, 2011 at 4:58 PM, Simon Horman wrote:
> This allows a ROM-able zImage to be written to eSD and for SuperH Mobile
> ARM to boot directly from the SDHI hardware block.
>
> This is achieved by the MaskROM loading the first portion of the image into
> MERAM and then jumping t
This allows a ROM-able zImage to be written to eSD and for SuperH Mobile
ARM to boot directly from the SDHI hardware block.
This is achieved by the MaskROM loading the first portion of the image into
MERAM and then jumping to it. This portion contains loader code which
copies the entire image to
