Pending April patches

Pending April patches

[Dirk Behme]

I decided to 'reset' my list of pending OMAP patches this month and to 
remove all 'old' stuff. Therefore, I have only two patches in my April 
list:

Pending OMAP patches April 2007
-------------------------------

1. [PATCH] SPI: Merge improved clock management from N800 tree into 
OMAP2 McSPI
http://linux.omap.com/pipermail/linux-omap-open-source/2007-April/009497.html

2. [PATCH] Updating 2430 SDP default config
http://linux.omap.com/pipermail/linux-omap-open-source/2007-April/009662.html

As usual, please correct or update if I missed anything. I think for 
'older' patches, best way to get attention for them again is to resend 
them.

Best regards

Dirk

Re: Pending April patches

[Jarkko Nikula]

On Tue, 01 May 2007 15:40:09 +0200
"ext Dirk Behme" <dirk.behme@googlemail.com> wrote:

> 1. [PATCH] SPI: Merge improved clock management from N800 tree into 
> OMAP2 McSPI
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-April/009497.html
> 
This is committed already. See 2d417941a60768fbf586792837c758292afec719


	Jarkko

Re: Pending April patches

[Budhee Jamaich]

Hello!

On 5/2/07, Jarkko Nikula <jarkko.nikula@nokia.com> wrote:
> This is committed already. See 2d417941a60768fbf586792837c758292afec719

Can you please explain me against what source tree you people are
sending patches here ?

is it one of these:
http://linux.omap.com/pub/kernel/2430sdp/source/
?

or is it this:
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=tree;h=52cbee1227465a23c586734fb1226276bfee877b;hb=52cbee1227465a23c586734fb1226276bfee877b

?

Thank you

>
>
>        Jarkko
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>

Re: Pending April patches

[Trilok Soni]

On 5/2/07, Budhee Jamaich <budheej@gmail.com> wrote:
> Hello!
>
> On 5/2/07, Jarkko Nikula <jarkko.nikula@nokia.com> wrote:
> > This is committed already. See 2d417941a60768fbf586792837c758292afec719
>
> Can you please explain me against what source tree you people are
> sending patches here ?
>
> is it one of these:
> http://linux.omap.com/pub/kernel/2430sdp/source/
> ?
>
> or is it this:
> http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=tree;h=52cbee1227465a23c586734fb1226276bfee877b;hb=52cbee1227465a23c586734fb1226276bfee877b
>

It is the second one you have mentioned. OMAP Community works on GIT
tree available on source.mvista.com/git only and it is preferred that
patches to be generated against it for submission.

-- 
--Trilok Soni

Re: Pending April patches

[Budhee Jamaich]

On 5/2/07, Trilok Soni <soni.trilok@gmail.com> wrote:
> On 5/2/07, Budhee Jamaich <budheej@gmail.com> wrote:
> > Can you please explain me against what source tree you people are
> > sending patches here ?
> > is it one of these:
> > http://linux.omap.com/pub/kernel/2430sdp/source/
> > or is it this:
> > http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=tree;h=52cbee1227465a23c586734fb1226276bfee877b;hb=52cbee1227465a23c586734fb1226276bfee877b
>
> It is the second one you have mentioned. OMAP Community works on GIT
> tree available on source.mvista.com/git only and it is preferred that
> patches to be generated against it for submission.

Hmm ok. and is this source tree good for any OMAP ? 2430 too ?

Thank You
>
> --
> --Trilok Soni
>

Re: Pending April patches

[Trilok Soni]

On 5/2/07, Budhee Jamaich <budheej@gmail.com> wrote:
> On 5/2/07, Trilok Soni <soni.trilok@gmail.com> wrote:
> > On 5/2/07, Budhee Jamaich <budheej@gmail.com> wrote:
> > > Can you please explain me against what source tree you people are
> > > sending patches here ?
> > > is it one of these:
> > > http://linux.omap.com/pub/kernel/2430sdp/source/
> > > or is it this:
> > > http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=tree;h=52cbee1227465a23c586734fb1226276bfee877b;hb=52cbee1227465a23c586734fb1226276bfee877b
> >
> > It is the second one you have mentioned. OMAP Community works on GIT
> > tree available on source.mvista.com/git only and it is preferred that
> > patches to be generated against it for submission.
>
> 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.

-- 
--Trilok Soni

Re: Pending April patches

[Budhee Jamaich]

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 ?

and another question - is there an OMAP-based product, of a big brand,
 that uses (or used) this git tree as a basis of their kernel ?


Thank YOU very much !!
>
> --
> --Trilok Soni
>

Re: Pending April patches

[Trilok Soni]

On 5/2/07, Budhee Jamaich <budheej@gmail.com> wrote:
> 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 ?

Yes and No. Always more code is better, so we take from this tarball
when needed and improve it or sometime write from scratch.

>
> and another question - is there an OMAP-based product, of a big brand,
>  that uses (or used) this git tree as a basis of their kernel ?
>

Check Nokia N770 and N800. http://www.maemo.org http://www.nseries.com/n800

-- 
--Trilok Soni

Re: Pending April patches

[Budhee Jamaich]

On 5/2/07, Trilok Soni <soni.trilok@gmail.com> wrote:
> > 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 ?
>
> Yes and No. Always more code is better, so we take from this tarball
> when needed and improve it or sometime write from scratch.

This is very very interesting.
Is it recommended to use the git tree for an OMAP based product
(the other alternative is naturally TI's tarballs) ?

Who are the main contributors to this git tree besides Nokia ?

> > and another question - is there an OMAP-based product, of a big brand,
> >  that uses (or used) this git tree as a basis of their kernel ?
> Check Nokia N770 and N800. http://www.maemo.org http://www.nseries.com/n800

do you know what OMAP version are these products based on ?

Thank You!!

>
> --
> --Trilok Soni
>

RE: Pending April patches

[Syed Mohammed, Khasim]

Hi Budhee,

You have crossed questions limit for today :) Kidding.

Can you be clearer on what product you are working on and what kind of software support you exactly expect for your product? OMAP GIT is more vast has lots of history which is kind of difficult to discuss on mailing list.

Let us know your requirements we can try to see what can be done for the same.

Thanks & Regards,
Khasim

>-----Original Message-----
>From: linux-omap-open-source-bounces+x0khasim=ti.com@linux.omap.com
>[mailto:linux-omap-open-source-bounces+x0khasim=ti.com@linux.omap.com] On
>Behalf Of Budhee Jamaich
>Sent: Wednesday, May 02, 2007 6:28 AM
>To: Trilok Soni
>Cc: linux-omap-open-source@linux.omap.com
>Subject: Re: Pending April patches
>
>On 5/2/07, Trilok Soni <soni.trilok@gmail.com> wrote:
>> > 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 ?
>>
>> Yes and No. Always more code is better, so we take from this tarball
>> when needed and improve it or sometime write from scratch.
>
>This is very very interesting.
>Is it recommended to use the git tree for an OMAP based product
>(the other alternative is naturally TI's tarballs) ?
>
>Who are the main contributors to this git tree besides Nokia ?
>
>> > and another question - is there an OMAP-based product, of a big brand,
>> >  that uses (or used) this git tree as a basis of their kernel ?
>> Check Nokia N770 and N800. http://www.maemo.org
>http://www.nseries.com/n800
>
>do you know what OMAP version are these products based on ?
>
>Thank You!!
>
>>
>> --
>> --Trilok Soni
>>
>_______________________________________________
>Linux-omap-open-source mailing list
>Linux-omap-open-source@linux.omap.com
>http://linux.omap.com/mailman/listinfo/linux-omap-open-source

Abt git trees and ti sources (was Re: Pending April patches)

[Nishanth Menon]

Budhee,
Budhee Jamaich stated on 5/2/2007 6:07 AM:
> Let me see I understand this.
> TI has published two kernel tarballs - 2.6.10 and 2.6.14 which fully
> supports the OMAP.
Depends on which omap you are speaking of... in short - yes. TI gives
its own variant of the kernel to the community.
> 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 ?
Not necessarily. Tricky part in a development to a new h/w is the exact
registers and sequence of operation. It is really great to get a
reference code in this respect. But, some stuff we'd need to do it
ourselves. Think of TI code more as a reference code. what you see there
need not be the same as to what u'd see in the git. Dont ask me which
one is better (supported and code wise too)... each has its own + and -.
>
> and another question - is there an OMAP-based product, of a big brand,
> that uses (or used) this git tree as a basis of their kernel ?
Aaaah... Now, can git kernel be a successful base for a production code?
Here is one big reality of a production quality code (kernel/application
or anything): stability. Any code can only be stable if we refuse to add
features and go through a long stage of testing... but  as you'd know
the git always moves forward... where would u draw a line and stop other
people's development on the tree for ur product? This is part of the
dilema most companies could face using opensource git as a product
model. The risk ofcourse is obsolote kernel variant.... in comparison to
the latest kernel ofcourse.

Now, the right question you can ask in this list is: will the git tree
boot up in any OMAP-based branded product? the answer would be a yes -
atleast I have seen nokia: N800(2420 I think), N770(1710 i think)
patches on this list... Now if your question is: are there OMAP-based
branded products using "git based" code(not necessarily back in our git
tree)... I suspect there could be many out there in the wild...

I am sure there are folks on this list more capable than I to explain
this more...
Regards,
Nishanth Menon

Re: Pending April patches

[Tony Lindgren]

* 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

RE: Pending April patches

[Woodruff, Richard]

> 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.

The root of all 2.6 trees is kernel.org, then linux-omap tree.  The TI
_downloadable_ trees branch off at a point in time as Tony said, usually
for pre/new-silicon or other major engagements which are not easily done
on the live tree.  Then beyond that you will have vendor trees like
MontaVista or WindRiver. These vendors combine aspects off all trees
into their final bundles. In cases I'm familiar with these final trees
are what go into production in multi-million quantities.

Depending on your _goals_ and _capabilities_ trees anywhere along the
line can be useful for you.

2.4 trees in production devices pre-date the omap-linux tree but
otherwise have a similar flow.

Regards,
Richard W.

Re: Pending April patches

[Budhee Jamaich]

On 5/2/07, Woodruff, Richard <r-woodruff2@ti.com> wrote:
> The root of all 2.6 trees is kernel.org, then linux-omap tree.  The TI
> _downloadable_ trees branch off at a point in time as Tony said, usually
> for pre/new-silicon or other major engagements which are not easily done
> on the live tree.  Then beyond that you will have vendor trees like
> MontaVista or WindRiver. These vendors combine aspects off all trees
> into their final bundles. In cases I'm familiar with these final trees
> are what go into production in multi-million quantities.

Thank you so much people for the help.
I'm really trying to understand the hows the process works, and you really
help.
One last questions please:
What is the process of moving new code from Linus' git tree to
the linux-omap tree ?
I bet it is not simple to merge many of Linus' commits..
Thank you once again and sorry for the questions...
Budhee.

>
> Regards,
> Richard W.
>
>

Re: Pending April patches

[Tony Lindgren]

* Budhee Jamaich <budheej@gmail.com> [070503 05:26]:
> On 5/2/07, Woodruff, Richard <r-woodruff2@ti.com> wrote:
> >The root of all 2.6 trees is kernel.org, then linux-omap tree.  The TI
> >_downloadable_ trees branch off at a point in time as Tony said, usually
> >for pre/new-silicon or other major engagements which are not easily done
> >on the live tree.  Then beyond that you will have vendor trees like
> >MontaVista or WindRiver. These vendors combine aspects off all trees
> >into their final bundles. In cases I'm familiar with these final trees
> >are what go into production in multi-million quantities.
> 
> Thank you so much people for the help.
> I'm really trying to understand the hows the process works, and you really
> help.
> One last questions please:
> What is the process of moving new code from Linus' git tree to
> the linux-omap tree ?
> I bet it is not simple to merge many of Linus' commits..
> Thank you once again and sorry for the questions...

We pull from Linus' tree to linux-omap on regular basis, usually every
time there's a new -rc release or something important gets merged.

Then we try to send all omap patches upstream, so eventually we should
be using Linus' tree + some omap driver patches.

Tony

Re: Pending April patches

[Tony Lindgren]

* Dirk Behme <dirk.behme@googlemail.com> [070501 13:45]:
> 
> I decided to 'reset' my list of pending OMAP patches this month and to 
> remove all 'old' stuff. Therefore, I have only two patches in my April 
> list:
> 
> Pending OMAP patches April 2007
> -------------------------------
> 
> 1. [PATCH] SPI: Merge improved clock management from N800 tree into 
> OMAP2 McSPI
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-April/009497.html
> 
> 2. [PATCH] Updating 2430 SDP default config
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-April/009662.html

And this patch needs the gpio and keypad drivers merged first.

> As usual, please correct or update if I missed anything. I think for 
> 'older' patches, best way to get attention for them again is to resend 
> them.

Yeah, please refresh and resend any patches that have been ignored.

Regards,

Tony