public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Raphaël Assénat" <raph@8d.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: AM3505/3517 support
Date: Wed, 06 Jul 2011 09:59:22 -0400	[thread overview]
Message-ID: <4E146A3A.5070100@8d.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024D91A50F@dbde02.ent.ti.com>

On 05/07/11 05:59 AM, Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org 
>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Raphaël Assénat
>> Sent: Tuesday, July 05, 2011 12:59 AM
>> To: linux-omap@vger.kernel.org
>> 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?

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-06 13:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 19:29 AM3505/3517 support Raphaël Assénat
2011-07-05  9:59 ` Premi, Sanjeev
2011-07-06 13:59   ` Raphaël Assénat [this message]
2011-07-06 16:15     ` Premi, Sanjeev
2011-07-05 11:19 ` Tony Lindgren
2011-07-05 14:35   ` Raphaël Assénat
2011-07-06  6:56     ` Tony Lindgren
2011-07-06  8:54       ` Premi, Sanjeev
2011-07-06 13:51         ` Raphaël Assénat
2011-07-07  9:14       ` Paul Walmsley
2011-07-07 11:54         ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E146A3A.5070100@8d.com \
    --to=raph@8d.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox