public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Budhee Jamaich <budheej@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending April patches
Date: Wed, 2 May 2007 17:21:08 +0000	[thread overview]
Message-ID: <20070502172108.GD3520@atomide.com> (raw)
In-Reply-To: <57314e840705020407q4823911i508d7ad24da47302@mail.gmail.com>

* Budhee Jamaich <budheej@gmail.com> [070502 11:13]:
> On 5/2/07, Trilok Soni <soni.trilok@gmail.com> wrote:
> 
> >> > > Can you please explain me against what source tree you people are
> >> > > sending patches here ?
> >> > > 
> >http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=tree;h=52cbee1227465a23c586734fb1226276bfee877b;hb=52cbee1227465a23c586734fb1226276bfee877b
> >> Hmm ok. and is this source tree good for any OMAP ? 2430 too ?
> >>
> >
> >It depends on what are the "good" things you are expecting from
> >particular OMAP support in this GIT tree. OMAP2430 core and TWL4030
> >support is included in GIT tree, and Syed is working on adding GPIO
> >and Keypad driver.
> >
> >You can help by porting the drivers/support you want to see in latest
> >kernel by porting them from TI's kernel tarballs.
> 
> Let me see I understand this.
> TI has published two kernel tarballs - 2.6.10 and 2.6.14 which fully
> supports the OMAP.
> But - the community is working on this git source tree, which is up-to-date
> with current kernel, and slowly port code from TI's code into the git tree ?

Well the TI trees are also based on older snapshots of the linux-omap tree.

Ideally there would be only minimal lag between the linux-omap tree and
TI's product snapshot trees of course.

But you can actually use most of the omap boards with the linux-omap
tree, you may need to apply few driver patches and the PM support
varies.

Regards,

Tony

  parent reply	other threads:[~2007-05-02 17:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:40 Pending April patches Dirk Behme
2007-05-02  5:47 ` Jarkko Nikula
2007-05-02  6:17   ` Budhee Jamaich
2007-05-02  8:34     ` Trilok Soni
2007-05-02  8:49       ` Budhee Jamaich
2007-05-02  9:46         ` Trilok Soni
2007-05-02 11:07           ` Budhee Jamaich
2007-05-02 11:19             ` Trilok Soni
2007-05-02 11:28               ` Budhee Jamaich
2007-05-02 15:33                 ` Syed Mohammed, Khasim
2007-05-02 11:30             ` Abt git trees and ti sources (was Re: Pending April patches) Nishanth Menon
2007-05-02 17:21             ` Tony Lindgren [this message]
2007-05-02 18:00               ` Pending April patches Woodruff, Richard
2007-05-03  5:26                 ` Budhee Jamaich
2007-05-03 16:44                   ` Tony Lindgren
2007-05-02 18:26 ` 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=20070502172108.GD3520@atomide.com \
    --to=tony@atomide.com \
    --cc=budheej@gmail.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