From: "Mark A. Greer" <mgreer@animalcreek.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "alan@alanlee.org" <alan@alanlee.org>, linux-omap@vger.kernel.org
Subject: Re: Stable version and repository loc
Date: Mon, 30 Apr 2012 16:10:11 -0700 [thread overview]
Message-ID: <20120430231011.GD19256@animalcreek.com> (raw)
In-Reply-To: <20120430194417.GE3739@atomide.com>
On Mon, Apr 30, 2012 at 12:44:17PM -0700, Tony Lindgren wrote:
> Hi,
>
> * alan@alanlee.org <alan@alanlee.org> [120430 11:24]:
> >
> > What is the latest version of the Linux kernel OMAP tree that is considered
> > stable? I'm in the middle of bringing up a bare-metal roll of Linux on a
> > derivative of the AM3517 family (Jacinto 3) on a commercial automotive radio.
> > I'm new to Linux on OMAP but old to Linux kernel development itself (since
> > pre-1.0). It appears the latest PSP from TI contains a version of 2.6.37 but
> > it's main line cousin is more than a year old now. And from lurking here on the
> > very active Linux OMAP list, that's likely a enormous number of changes. I'm
> > just looking for the most current stable starting point and working up from
> > there as technical problems dictate.
>
> The stable version is most recent mainline Linux kernel tree, that is
> v3.3 currently. All the other branches are development branches for the
> upcoming merge window, or some legacy patches that we still carry around
> that are not ready to be merged yet.
Alan, you should be aware that there are some issues with am35x support.
They are being worked on but aren't there yet. To get by for now, make
sure you add 'nohlt' to your kernel cmdline and do not enable
CONFIG_CPU_IDLE. If you want to suspend/resume (i.e., suspend-to-RAM),
you will have more issues so avoid doing that if you can.
Mark
prev parent reply other threads:[~2012-04-30 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 18:20 Stable version and repository loc alan
2012-04-30 19:44 ` Tony Lindgren
2012-04-30 23:10 ` Mark A. Greer [this message]
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=20120430231011.GD19256@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=alan@alanlee.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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