From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dirk Behme <dirk.behme@gmail.com>
Date: Sat, 22 Sep 2012 08:21:16 +0200
Subject: [U-Boot] [PATCH V2 00/21] Add mx6solo/mx6duallite support
In-Reply-To: <1348281558-19520-1-git-send-email-troy.kisky@boundarydevices.com>
References: <1348012989-19674-1-git-send-email-troy.kisky@boundarydevices.com>
	<1348281558-19520-1-git-send-email-troy.kisky@boundarydevices.com>
Message-ID: <505D58DC.9090901@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Troy,

On 22.09.2012 04:38, Troy Kisky wrote:
> After this series the same binary will run on a
> Saberlite board using any of the pin compatible processors
> mx6 quad, mx6 duallite, or mx6 solo. This is accomplished
> using a plugin and a table built by mkimage.

Could you briefly explain or give a link to some documentation how 
this does work? It sounds to me that the plugin concept is something 
the boot ROM has to understand? Or in other words: How does the boot 
ROM decide on which processor it runs and which DCD table to execute then?

Sorry if I misunderstood something, I'm not so familiar with the boot 
ROM options.

Many thanks

Dirk