<br>Hello Uwe,<br><div class="gmail_quote">2010/10/14 Uwe Kleine-König <span dir="ltr"><<a href="mailto:u.kleine-koenig@pengutronix.de">u.kleine-koenig@pengutronix.de</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br>
<div><div></div><div class="h5"><br>
On Thu, Oct 14, 2010 at 09:05:39PM +0800, xiao jiang wrote:<br>
> Hi,<br>
> 2010/10/14 Fabio Estevam <<a href="mailto:festevam@gmail.com">festevam@gmail.com</a>><br>
><br>
> > Hi Xiao Jiang,<br>
> ><br>
> > 2010/10/14 Uwe Kleine-König <<a href="mailto:u.kleine-koenig@pengutronix.de">u.kleine-koenig@pengutronix.de</a>>:<br>
> > > Hello Xiao (hoping this is the part of your name corresponding to your<br>
> > > first name),<br>
> > ><br>
> > > On Thu, Oct 14, 2010 at 12:06:25AM -0400, xiao jiang wrote:<br>
> > >> I saw the mach-mx35_3ds.c are come from you, so I think you are the<br>
> > right<br>
> > >> person to answer my queston, :).<br>
> > > It was me, who renamed the file and touched it a few times when cleaning<br>
> > > up and reorganising things for the i.MX machines. Initially it was<br>
> > > Fabio Estevam who brought the machine into mainline.<br>
> ><br>
> > I suggest you to look at MX51 3stack board or MX31 3stack boards, as<br>
> > they have support for LAN9217 controller.<br>
> ><br>
> ><br>
> Uwe,<br>
> I forgot to subscribe the list, now it is ok after done it.:)<br>
><br>
> Fabio,<br>
> Thanks for your hint, I can boot the kernel thru lan9217 now, only a few<br>
> lines added.<br>
><br>
> diff --git a/arch/arm/mach-mx3/mach-mx35_3ds.c<br>
> b/arch/arm/mach-mx3/mach-mx35_3ds.c<br>
> index 1c30d72..7e30a4e 100644<br>
> --- a/arch/arm/mach-mx3/mach-mx35_3ds.c<br>
> +++ b/arch/arm/mach-mx3/mach-mx35_3ds.c<br>
> @@ -35,6 +35,7 @@<br>
> #include <mach/hardware.h><br>
> #include <mach/common.h><br>
> #include <mach/iomux-mx35.h><br>
> +#include <mach/3ds_debugboard.h><br>
><br>
> #include "devices-imx35.h"<br>
> #include "devices.h"<br>
> @@ -86,6 +87,7 @@ static struct fsl_usb2_platform_data usb_pdata = {<br>
> /*<br>
> * Board specific initialization.<br>
> */<br>
> +#define EXPIO_PARENT_INT 65<br>
> static void __init mxc_board_init(void)<br>
> {<br>
> mxc_iomux_v3_setup_multiple_pads(mx35pdk_pads,<br>
> ARRAY_SIZE(mx35pdk_pads));<br>
> @@ -95,6 +97,10 @@ static void __init mxc_board_init(void)<br>
> imx35_add_imx_uart0(&uart_pdata);<br>
><br>
> mxc_register_device(&mxc_otg_udc_device, &usb_pdata);<br>
> +<br>
> + if (!mxc_expio_init(MX35_CS5_BASE_ADDR, EXPIO_PARENT_INT))<br>
> + printk(KERN_WARNING "Init of the debugboard failed, all "<br>
> + "devices on the board are unusable.\n");<br>
</div></div>If you intend this patch to go mainline please use pr_warn instead of<br>
printk(KERN_WARNING ...).<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div>Ok, but I don't want to use hard-code for EXPIO_PARENT_INT, and found there is no related definition for MX35_GPIO1_1 pin, do I need to create it like MX31_PIN_GPIO1_1?<br>
<br>Best Regards,<br>Xiao Jiang<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5">
Best regards<br>
Uwe<br>
<br>
--<br>
Pengutronix e.K. | Uwe Kleine-König |<br>
Industrial Linux Solutions | <a href="http://www.pengutronix.de/" target="_blank">http://www.pengutronix.de/</a> |<br>
</div></div></blockquote></div><br>