On Tue, Aug 18, 2009 at 10:28:04AM +0800, Tiejun Chen wrote:
>To support cuImage, we need to initialize the required sections and 
>ensure that it is built.
>
>-              cuboot-acadia.c cuboot-amigaone.c
>+              cuboot-acadia.c cuboot-amigaone.c cuboot-kilauea.c
> src-boot := $(src-wlib) $(src-plat) empty.c
>
> src-boot := $(addprefix $(obj)/, $(src-boot))
>@@ -192,6 +192,7 @@ image-$(CONFIG_DEFAULT_UIMAGE)             += uImage
> image-$(CONFIG_EP405)                 += dtbImage.ep405
> image-$(CONFIG_WALNUT)                        += treeImage.walnut
> image-$(CONFIG_ACADIA)                        += cuImage.acadia
>+image-$(CONFIG_KILAUEA)               += cuImage.kilauea

I'm not thrilled with this part as cuImage is really the secondary
solution if the U-Boot that comes with a board if FDT aware.  If you
have a different board that needs this, perhaps you could add the
target when that board support gets upstream?

>+static void kilauea_fixups(void)
>+{
>+      /*TODO: Please change this as the real. Note that should be 
>33MHZ~100MHZ.*/

What does that mean?

josh
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to