RE: AM3505/3517 support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Raphaël Assénat [mailto:raph@xxxxxx] 
> Sent: Wednesday, July 06, 2011 7:29 PM
> To: Premi, Sanjeev
> Cc: linux-omap@xxxxxxxxxxxxxxx
> Subject: Re: AM3505/3517 support
> 
> On 05/07/11 05:59 AM, Premi, Sanjeev wrote:
> >> -----Original Message-----
> >> From: linux-omap-owner@xxxxxxxxxxxxxxx 
> >> [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of 
> Raphaël Assénat
> >> Sent: Tuesday, July 05, 2011 12:59 AM
> >> To: linux-omap@xxxxxxxxxxxxxxx
> >> Subject: AM3505/3517 support
> >>
> >> Hello,
> >>
> >> We have a custom designed based on the AM3505 and we wish to 
> >> run a modern kernel
> >> on it. Unfortunately, it seems a lot of efforts have been 
> >> made to support other 
> >> OMAP chips and that some work is still required to support 
> >> the AM3505/3517 
> >> completely. (does not boot as-is)
> >>
> >> Is there anyone working on this right now? Not knowing, I 
> >> have already started
> >> working on it.
> >>
> >> The am3505 is apparently so similar to the 3430 that it was 
> >> treated as such 
> >> (omap_chip.oc was being set to CHIP_IS_OMAP3430ES3_1). There 
> >> are however a
> >> few differences that need to be addressed. I have therefore 
> >> created a new
> >> CHIP_IS and patched clocks, hwmod and power management 
> related files
> >> consequently. My system now boots until it complains that it 
> >> is unable 
> >> to mount its root filesystem.
> >>
> >> I will send my patches in a moment for comments and 
> >> hopefully, after a 
> >> few iterations, they will be acceptable. I know a lot of 
> cleanup is 
> >> happening right now and as a result my patches may not apply 
> >> or conflict. 
> >> Please let me know and I will be happy to rebase them as needed.
> >>
> >> Looking forward to your comments and help. 
> >>
> >> One of the next things I'll look at is how to properly 
> >> support the ZCN package.
> >> Right now, the CBB package is used (board-am3517evm.c for 
> >> instance) but there
> >> are differences that prevent some GPIOs from being configured 
> >> properly. It would
> >> be nice to know if someone is working on this before I start...
> > 
> > Raphael,
> > 
> > The AM35x support has been trailing on the linux-omap. Usually,
> > due to delays in dependency resolution:
> > 
> > If you are not specifically looking for the latest kernel,
> > revision you can get the sources from:
> > http://arago-project.org/git/projects/?p=linux-omap3.git
> > 
> > Use the tag: v2.6.37_OMAPPSP_04.02.00.07
> > 
> > This tree is supported by TI. The patches contained here, are
> > being reworked for upstream submission...
> When possible, I prefer working on the latest version. But at least
> I'll have a look to make sure I'm not duplicating anyone's work.
> 
> By the way, is there a specific mailing list for discussing
> this git tree?

[sp] There is no mailing list. But you can use the e2e.ti.com.
     Select "Linux Forum" under "Embedded Software" to post query.

~sanjeev

> 
> Best regards,
> Raphaël Assénat
> --
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux