* git tree
@ 2009-06-24 9:34 Ryan
2009-06-24 11:10 ` Tony Lindgren
0 siblings, 1 reply; 10+ messages in thread
From: Ryan @ 2009-06-24 9:34 UTC (permalink / raw)
To: linux-omap
Hi,
Looking at the linux-omap tree using the gitweb interface. Apart
from the "master" branch and tags.
why do we have lots of branches? How and when do they intertact with
each other.
17 hours ago omap1-upstream shortlog | log | tree
17 hours ago omap2-upstream shortlog | log | tree
17 hours ago omap3-boards shortlog | log | tree
17 hours ago omap3-upstream shortlog | log | tree
17 hours ago omap4 shortlog | log | tree
17 hours ago pm shortlog | log | tree
19 hours ago omap-headers shortlog | log | tree
19 hours ago omap-upstream shortlog | log | tree
19 hours ago omap-fixes shortlog | log | tree
47 hours ago master shortlog | log | tree
2 weeks ago omap-decimate shortlog | log | tree
2 weeks ago omapfb-upstream shortlog | log | tree
2 weeks ago omap-pool shortlog | log | tree
3 weeks ago for-next-2.6.30 shortlog | log | tree
4 weeks ago for-next shortlog | log | tree
4 weeks ago iommu shortlog | log | tree
2 months ago omap-2.6.29 shortlog | log | tree
3 months ago clks-testing shortlog | log | tree
3 months ago delete shortlog | log | tree
4 months ago omap-2.6.28 shortlog | log | tree
4 months ago tidspbridge shortlog | log | tree
5 months ago dspgateway shortlog | log | tree
5 months ago linus shortlog | log | tree
6 months ago musb shortlog | log | tree
Can anyone explain what exactly goes into each of them?
Some are straight forward like pm, usb, tidspbridge, gateway. not sure
about for-next-2.6.30, omap-fixes.
Trying to understand things/mode of development in here.
Thank you,
Ryan
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: git tree
2009-06-24 9:34 git tree Ryan
@ 2009-06-24 11:10 ` Tony Lindgren
2009-06-25 14:08 ` Pandita, Vikram
0 siblings, 1 reply; 10+ messages in thread
From: Tony Lindgren @ 2009-06-24 11:10 UTC (permalink / raw)
To: Ryan; +Cc: linux-omap
Hi,
* Ryan <ryanphilips19@googlemail.com> [090624 12:42]:
> Hi,
> Looking at the linux-omap tree using the gitweb interface. Apart
> from the "master" branch and tags.
> why do we have lots of branches? How and when do they intertact with
> each other.
>
>
> 17 hours ago omap1-upstream shortlog | log | tree
> 17 hours ago omap2-upstream shortlog | log | tree
> 17 hours ago omap3-boards shortlog | log | tree
> 17 hours ago omap3-upstream shortlog | log | tree
> 17 hours ago omap4 shortlog | log | tree
> 17 hours ago pm shortlog | log | tree
> 19 hours ago omap-headers shortlog | log | tree
> 19 hours ago omap-upstream shortlog | log | tree
> 19 hours ago omap-fixes shortlog | log | tree
> 47 hours ago master shortlog | log | tree
> 2 weeks ago omap-decimate shortlog | log | tree
> 2 weeks ago omapfb-upstream shortlog | log | tree
> 2 weeks ago omap-pool shortlog | log | tree
> 3 weeks ago for-next-2.6.30 shortlog | log | tree
> 4 weeks ago for-next shortlog | log | tree
> 4 weeks ago iommu shortlog | log | tree
> 2 months ago omap-2.6.29 shortlog | log | tree
> 3 months ago clks-testing shortlog | log | tree
> 3 months ago delete shortlog | log | tree
> 4 months ago omap-2.6.28 shortlog | log | tree
> 4 months ago tidspbridge shortlog | log | tree
> 5 months ago dspgateway shortlog | log | tree
> 5 months ago linus shortlog | log | tree
> 6 months ago musb shortlog | log | tree
>
>
> Can anyone explain what exactly goes into each of them?
> Some are straight forward like pm, usb, tidspbridge, gateway. not sure
> about for-next-2.6.30, omap-fixes.
More or less the various branches are topic branches of patches
going to the mainline kernel. For example, omap-fixes contains fixes to
be sent during the -rc cycle, omap-upstream contains omap common patches
for the next merge window, omap1-upstream omap1 specific patches for
the next merge window and so on.
The master branch is more or less merge of all the topic branches.
Currently missing from it are the pm branch and the dss2 branch.
> Trying to understand things/mode of development in here.
Hope this helps. In general, your should now be able to do almost
all the patches against Linus' mainline kernel. Of course until
we get pm and dss2 into the mainline kernel, those patches need to
be done against pm and dss2 branches.
So everybody, where possible, please base all the patches against
Linus' kernel stable something or -rc someting, that way they are
easy to merge in.
Regards,
Tony
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: git tree
2009-06-24 11:10 ` Tony Lindgren
@ 2009-06-25 14:08 ` Pandita, Vikram
2009-06-25 14:40 ` Tony Lindgren
0 siblings, 1 reply; 10+ messages in thread
From: Pandita, Vikram @ 2009-06-25 14:08 UTC (permalink / raw)
To: Tony Lindgren, Ryan; +Cc: linux-omap@vger.kernel.org
>-----Original Message-----
>From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Tony
>
>Hi,
>
>* Ryan <ryanphilips19@googlemail.com> [090624 12:42]:
>> Hi,
>> Looking at the linux-omap tree using the gitweb interface. Apart
>> from the "master" branch and tags.
>> why do we have lots of branches? How and when do they intertact with
>> each other.
>>
>> Can anyone explain what exactly goes into each of them?
>> Some are straight forward like pm, usb, tidspbridge, gateway. not sure
>> about for-next-2.6.30, omap-fixes.
>
>More or less the various branches are topic branches of patches
>going to the mainline kernel. For example, omap-fixes contains fixes to
>be sent during the -rc cycle, omap-upstream contains omap common patches
>for the next merge window, omap1-upstream omap1 specific patches for
>the next merge window and so on.
>
>The master branch is more or less merge of all the topic branches.
>Currently missing from it are the pm branch and the dss2 branch.
>
>> Trying to understand things/mode of development in here.
>
>Hope this helps. In general, your should now be able to do almost
>all the patches against Linus' mainline kernel. Of course until
>we get pm and dss2 into the mainline kernel, those patches need to
>be done against pm and dss2 branches.
>
>So everybody, where possible, please base all the patches against
>Linus' kernel stable something or -rc someting, that way they are
>easy to merge in.
Are you recommending that future patches posted to l-o list should be based of kernel.org
and not master of l-o?
>
>Regards,
>
>Tony
>--
>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
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: git tree
2009-06-25 14:08 ` Pandita, Vikram
@ 2009-06-25 14:40 ` Tony Lindgren
0 siblings, 0 replies; 10+ messages in thread
From: Tony Lindgren @ 2009-06-25 14:40 UTC (permalink / raw)
To: Pandita, Vikram; +Cc: Ryan, linux-omap@vger.kernel.org
* Pandita, Vikram <vikram.pandita@ti.com> [090625 17:08]:
>
>
> >-----Original Message-----
> >From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Tony
> >
> >Hi,
> >
> >* Ryan <ryanphilips19@googlemail.com> [090624 12:42]:
> >> Hi,
> >> Looking at the linux-omap tree using the gitweb interface. Apart
> >> from the "master" branch and tags.
> >> why do we have lots of branches? How and when do they intertact with
> >> each other.
> >>
> >> Can anyone explain what exactly goes into each of them?
> >> Some are straight forward like pm, usb, tidspbridge, gateway. not sure
> >> about for-next-2.6.30, omap-fixes.
> >
> >More or less the various branches are topic branches of patches
> >going to the mainline kernel. For example, omap-fixes contains fixes to
> >be sent during the -rc cycle, omap-upstream contains omap common patches
> >for the next merge window, omap1-upstream omap1 specific patches for
> >the next merge window and so on.
> >
> >The master branch is more or less merge of all the topic branches.
> >Currently missing from it are the pm branch and the dss2 branch.
> >
> >> Trying to understand things/mode of development in here.
> >
> >Hope this helps. In general, your should now be able to do almost
> >all the patches against Linus' mainline kernel. Of course until
> >we get pm and dss2 into the mainline kernel, those patches need to
> >be done against pm and dss2 branches.
> >
> >So everybody, where possible, please base all the patches against
> >Linus' kernel stable something or -rc someting, that way they are
> >easy to merge in.
>
> Are you recommending that future patches posted to l-o list should be based of kernel.org
> and not master of l-o?
Yeah, for all the patches that do not have dependencies to other topic
branches such as pm, dss2.
Regards,
Tony
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* git tree
@ 2007-07-30 12:14 Luís Vitório Cargnini
2007-07-30 12:37 ` Felipe Balbi
0 siblings, 1 reply; 10+ messages in thread
From: Luís Vitório Cargnini @ 2007-07-30 12:14 UTC (permalink / raw)
To: omap
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear fellows,
Please which git tree I should use ?
I'm using the kernel.org tree and the latest tag is
S v2.6.22-rc4 5b78c77092a6 Linus 2.6.22-rc4
cg-status
Heads:
>master 2a1c4dfbbe9fd7f756e62579bb42d341d340bd0f
R origin 2a1c4dfbbe9fd7f756e62579bb42d341d340bd0f
- --
-
------------------------------------------------------------------------------
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 - Building 30
P.O. Box: 90619-900 - Porto Alegre/RS
Phone: +55 51 3320 3500 extension: 7696
-
---------------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGrdYcKNrSZaSIZoURAkWKAJ0Yc0IKqIBe84ctxtyzgWrZ0ezRjACePtg9
7y+UkKTe6TJYhR3WgbfnRuY=
=nPfw
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: git tree
2007-07-30 12:14 Luís Vitório Cargnini
@ 2007-07-30 12:37 ` Felipe Balbi
0 siblings, 0 replies; 10+ messages in thread
From: Felipe Balbi @ 2007-07-30 12:37 UTC (permalink / raw)
To: Luís Vitório Cargnini; +Cc: omap
Hi,
On 7/30/07, Luís Vitório Cargnini <lvcargnini@ieee.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dear fellows,
> Please which git tree I should use ?
> I'm using the kernel.org tree and the latest tag is
And which other tree should you use??
This is the one and only linux-omap tree, you can get a mirror from
monta vista's servers, but it's the same tree anyway.
This tree is a bit outdated since tony still on vacations afaik... but
soon it'll be upgraded.
regards
>
> S v2.6.22-rc4 5b78c77092a6 Linus 2.6.22-rc4
>
> cg-status
> Heads:
> >master 2a1c4dfbbe9fd7f756e62579bb42d341d340bd0f
> R origin 2a1c4dfbbe9fd7f756e62579bb42d341d340bd0f
> - --
> -
> ------------------------------------------------------------------------------
> Thanks && Regards
> Msc. Bsc. Luís Vitório Cargnini
> IEEE Member
> Electrical Engineer Faculty @ PUCRS
> Ipiranga Avenue, 6681 - Building 30
> P.O. Box: 90619-900 - Porto Alegre/RS
> Phone: +55 51 3320 3500 extension: 7696
> -
> ---------------------------------------------------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.5 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGrdYcKNrSZaSIZoURAkWKAJ0Yc0IKqIBe84ctxtyzgWrZ0ezRjACePtg9
> 7y+UkKTe6TJYhR3WgbfnRuY=
> =nPfw
> -----END PGP SIGNATURE-----
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
--
Best Regards,
Felipe Balbi
felipebalbi@users.sourceforge.net
^ permalink raw reply [flat|nested] 10+ messages in thread
* Git tree
@ 2007-07-17 11:41 Veda N
2007-07-17 12:03 ` Trilok Soni
2007-07-25 15:15 ` Maximus
0 siblings, 2 replies; 10+ messages in thread
From: Veda N @ 2007-07-17 11:41 UTC (permalink / raw)
To: linux-omap-open-source
Hi,
I am using the latest git tree. MTD and nand support for SDP does not
exist.
Am not able to boot out of JFFS file system.
Has anyone tried booting latest git kernel out of JFFS2 filesystem.
Regards,
vedan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Git tree
2007-07-17 11:41 Git tree Veda N
@ 2007-07-17 12:03 ` Trilok Soni
2007-07-25 15:15 ` Maximus
1 sibling, 0 replies; 10+ messages in thread
From: Trilok Soni @ 2007-07-17 12:03 UTC (permalink / raw)
To: Veda N; +Cc: linux-omap-open-source
Hi Veda,
On 7/17/07, Veda N <veda74@gmail.com> wrote:
> Hi,
> I am using the latest git tree. MTD and nand support for SDP does not
> exist.
>
> Am not able to boot out of JFFS file system.
>
> Has anyone tried booting latest git kernel out of JFFS2 filesystem.
Which board are you referring too? Do you mean 3430 or 2430, and I
think for 2430 NAND support is there.
--
--Trilok Soni
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Git tree
2007-07-17 11:41 Git tree Veda N
2007-07-17 12:03 ` Trilok Soni
@ 2007-07-25 15:15 ` Maximus
1 sibling, 0 replies; 10+ messages in thread
From: Maximus @ 2007-07-25 15:15 UTC (permalink / raw)
To: Veda N; +Cc: linux-omap-open-source
On 7/17/07, Veda N <veda74@gmail.com> wrote:
> Hi,
> I am using the latest git tree. MTD and nand support for SDP does not
> exist.
Were you able to boot out of nand flash using the git-tree?.
"make omap_2430sdp_defconfig" does not enable nand support.
one-nand support is enabled. Both are exclusive.
-- john
> Am not able to boot out of JFFS file system.
>
> Has anyone tried booting latest git kernel out of JFFS2 filesystem.
>
>
> Regards,
> vedan
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Git tree
@ 2006-07-13 22:41 Luís Cargnini
0 siblings, 0 replies; 10+ messages in thread
From: Luís Cargnini @ 2006-07-13 22:41 UTC (permalink / raw)
To: OMAP
Please whose git tree i must use the git tree provided bit mvist or
kernel.org ??
the problem compiling the source from kernel.org:
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/compile.h
CC arch/arm/plat-omap/clock.o
arch/arm/plat-omap/clock.c:31: error: static declaration of 'clocks' follows
non-static declaration
include/asm/arch/clock.h:19: error: previous declaration of 'clocks' was
here
arch/arm/plat-omap/clock.c:33: error: static declaration of 'clockfw_lock'
follows non-static declaration
include/asm/arch/clock.h:20: error: previous declaration of 'clockfw_lock'
was here
make[1]: *** [arch/arm/plat-omap/clock.o] Error 1
make: *** [arch/arm/plat-omap] Error 2
persist.
How could i fix this ?
someone mentioned a patch where i found this patch for gcc ?
i'm using the denx toolchain, but thinking im recreate my own toolchain,
someone using 4.1.0 ??
and have a howto or quick-setup ?
compiling gcc.4.1.0 i founded the following:
In file included from ../../gcc-4.1.0/gcc/crtstuff.c:68:
../../gcc-4.1.0/gcc/tsystem.h:90:19: error: stdio.h: No such file or
directory
../../gcc-4.1.0/gcc/tsystem.h:93:23: error: sys/types.h: No such file or
directory
../../gcc-4.1.0/gcc/tsystem.h:96:19: error: errno.h: No such file or
directory
../../gcc-4.1.0/gcc/tsystem.h:103:20: error: string.h: No such file or
directory
../../gcc-4.1.0/gcc/tsystem.h:104:20: error: stdlib.h: No such file or
directory
../../gcc-4.1.0/gcc/tsystem.h:105:20: error: unistd.h: No such file or
directory
../../gcc-4.1.0/gcc/tsystem.h:111:18: error: time.h: No such file or
directory
make[2]: *** [crtbegin.o] Error 1
make[2]: Leaving directory `/home/lvcargnini/puc/instramed/build/b-gcc/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/home/lvcargnini/puc/instramed/build/b-gcc'
but
../gcc-4.1.0/gcc/config/arm/t-linux
....
TARGET_LIBGCC2_CFLAGS = -fomit-frame-pointer -fPIC -Dinhibit_libc
-D__gthr_posix_h
....
and my configure line is
../gcc-4.1.0/configure --prefix=/opt/arm-linux --target=arm-linux
--with-float=soft --with-cpu=arm9tdmi --disable-shared --disable-threads
--with-headers=/opt/arm-linux/arm-linux/include --enable-languages=c
thanks for any help.
--
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2009-06-25 14:40 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-24 9:34 git tree Ryan
2009-06-24 11:10 ` Tony Lindgren
2009-06-25 14:08 ` Pandita, Vikram
2009-06-25 14:40 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2007-07-30 12:14 Luís Vitório Cargnini
2007-07-30 12:37 ` Felipe Balbi
2007-07-17 11:41 Git tree Veda N
2007-07-17 12:03 ` Trilok Soni
2007-07-25 15:15 ` Maximus
2006-07-13 22:41 Luís Cargnini
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox