public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Andray Kaganovsky <andrayk@fcibroadband.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: most recent kernel version to use with OMAP2420
Date: Tue, 26 Jun 2007 23:29:10 -0700	[thread overview]
Message-ID: <20070627062908.GA2225@atomide.com> (raw)
In-Reply-To: <1182892909.3642.21.camel@linux>

* Andray Kaganovsky <andrayk@fcibroadband.com> [070626 14:25]:
> Hello,
> 
> I am trying to figure out which kernel version should I use with
> my OMAP2420 board (I would prefer one of the most recent versions).
> 
> I have downloaded repository from
> git://source.mvista.com/git/linux-omap-2.6.git, and found that
> it contains few dozens of kernel versions; ten of them
> have "omap" as part of their names:  
> 
>     v2.6.13-omap1
>     v2.6.14-rc1-omap1
>     v2.6.15-omap2
>     v2.6.16-omap1
>     v2.6.16-omap2
>     v2.6.17-omap1
>     v2.6.17-omap2
>     v2.6.18-omap1
>     v2.6.19-omap1
>     v2.6.21-omap1
> 
> Are the "omap" versions specifically patched for OMAP boards ? Do
> I have a better chance of getting "omap" versions to work with
> OMAP2420 board then the versions which don't have "omap" in their
> names ?

Yes, -omap kernels are "stable" snapshots from linux-omap tree.
They have more boards and drivers compared to Linus' tree.
I recommend using the linux-omap git tree or latest stable
release.

> Does anybody actually got any of these versions to work with
> OMAP2420 ?

At least TI H4 and Nokia N800 are well supported in the
linux-omap tree. Adding new boards is trivial.

> Thanks in advance and regards,

No problem,

Tony

      reply	other threads:[~2007-06-27  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26 21:21 most recent kernel version to use with OMAP2420 Andray Kaganovsky
2007-06-27  6:29 ` Tony Lindgren [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=20070627062908.GA2225@atomide.com \
    --to=tony@atomide.com \
    --cc=andrayk@fcibroadband.com \
    --cc=linux-omap-open-source@linux.omap.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