Pull request for new TI machines, angstrom and qt4 fixes
Tom,
Please pull these 8 commits for the external Angstrom toolchain fix, qt4 security advisory fix, as well as for addition of new TI machines. All are cherry picked from oe.dev
Pull URL: git://arago-project.org/git/people/denix/openembedded.git
Branch: 2011.03-maintenance
Browse: http://arago-project.org/git/people/?p=denix/openembedded.git;a=shortlog;h=refs/heads/2011.03-maintenance
Thanks,
Denys Dmytriyenko <[email protected]>
---
Chase Maupin (6):
ti814x: Add new machine definitions
linux-omap3: add PSP recipe for am387x-evm
u-boot: Add PSP version for am387x-evm
sort: Add ti814x machine types
am-benchmarks: Add support for am387x-evm machine
matrix-gui: Add support for am387x-evm machine
Denys Dmytriyenko (2):
external-toolchain-angstrom: don't stage .la files
qt4: security advisory - blacklist fraudulent comodo certificates
conf/machine/am387x-evm.conf | 5 + conf/machine/c6a814x-evm.conf | 5 + conf/machine/dm814x-evm.conf | 5 + conf/machine/include/ti814x.inc | 26 + contrib/angstrom/sort.sh | 2 +- .../ti814x/defconfig | 1927 ++++++++++++++++++++ recipes/linux/linux-omap3_2.6.37-psp04.01.00.03.bb | 10 + recipes/meta/external-toolchain-angstrom.bb | 4 +- ...klist-fraudulent-comodo-certificates-patch.diff | 134 ++ recipes/qt4/qt-4.6.3.inc | 8 +- recipes/qt4/qt-4.7.1.inc | 3 +- recipes/qt4/qt4-embedded_4.6.3.bb | 2 +- recipes/qt4/qt4-embedded_4.7.1.bb | 2 +- recipes/ti/am-benchmarks_1.2.bb | 5 +- recipes/ti/matrix-gui-common.inc | 5 +- recipes/ti/matrix-gui-e.inc | 5 +- recipes/ti/matrix-gui.inc | 5 +- recipes/u-boot/u-boot_2010.06-psp04.01.00.03.bb | 14 + 18 files changed, 2149 insertions(+), 18 deletions(-) create mode 100644 conf/machine/am387x-evm.conf create mode 100644 conf/machine/c6a814x-evm.conf create mode 100644 conf/machine/dm814x-evm.conf create mode 100644 conf/machine/include/ti814x.inc create mode 100644 recipes/linux/linux-omap3-2.6.37-psp04.01.00.03/ti814x/defconfig create mode 100644 recipes/linux/linux-omap3_2.6.37-psp04.01.00.03.bb create mode 100644 recipes/qt4/files/blacklist-fraudulent-comodo-certificates-patch.diff create mode 100644 recipes/u-boot/u-boot_2010.06-psp04.01.00.03.bb
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 5 lines · Denys Dmytriyenko
Tom,
Please pull these 8 commits for the external Angstrom toolchain fix, qt4 security advisory fix, as well as for addition of new TI machines. All are cherry picked from oe.dev
Merging it like this creates a few broken commits because the machines were added first. Is that really what we want?
regards,
Koen
Quoted 42 lines
Pull URL:
git://arago-project.org/git/people/denix/openembedded.git
Branch: 2011.03-maintenance
Browse: http://arago-project.org/git/people/?p=denix/openembedded.git;a=shortlog;h=refs/heads/2011.03-maintenanceThanks,
Denys Dmytriyenko <[email protected]>
---Chase Maupin (6):
ti814x: Add new machine definitions
linux-omap3: add PSP recipe for am387x-evm
u-boot: Add PSP version for am387x-evm
sort: Add ti814x machine types
am-benchmarks: Add support for am387x-evm machine
matrix-gui: Add support for am387x-evm machineDenys Dmytriyenko (2):
external-toolchain-angstrom: don't stage .la files
qt4: security advisory - blacklist fraudulent comodo certificatesconf/machine/am387x-evm.conf | 5 + conf/machine/c6a814x-evm.conf | 5 + conf/machine/dm814x-evm.conf | 5 + conf/machine/include/ti814x.inc | 26 + contrib/angstrom/sort.sh | 2 +- .../ti814x/defconfig | 1927 ++++++++++++++++++++ recipes/linux/linux-omap3_2.6.37-psp04.01.00.03.bb | 10 + recipes/meta/external-toolchain-angstrom.bb | 4 +- ...klist-fraudulent-comodo-certificates-patch.diff | 134 ++ recipes/qt4/qt-4.6.3.inc | 8 +- recipes/qt4/qt-4.7.1.inc | 3 +- recipes/qt4/qt4-embedded_4.6.3.bb | 2 +- recipes/qt4/qt4-embedded_4.7.1.bb | 2 +- recipes/ti/am-benchmarks_1.2.bb | 5 +- recipes/ti/matrix-gui-common.inc | 5 +- recipes/ti/matrix-gui-e.inc | 5 +- recipes/ti/matrix-gui.inc | 5 +- recipes/u-boot/u-boot_2010.06-psp04.01.00.03.bb | 14 + 18 files changed, 2149 insertions(+), 18 deletions(-)
Quoted 8 lines
create mode 100644 conf/machine/am387x-evm.conf create mode 100644 conf/machine/c6a814x-evm.conf create mode 100644 conf/machine/dm814x-evm.conf create mode 100644 conf/machine/include/ti814x.inc create mode 100644 recipes/linux/linux-omap3-2.6.37-psp04.01.00.03/ti814x/defconfig create mode 100644 recipes/linux/linux-omap3_2.6.37-psp04.01.00.03.bb create mode 100644 recipes/qt4/files/blacklist-fraudulent-comodo-certificates-patch.diff create mode 100644 recipes/u-boot/u-boot_2010.06-psp04.01.00.03.bb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNlEUgMkyGM64RGpERAhOlAJ9tJlo2fwsBqsjssEj7HAaY7kpZSACggC6j Gb+UFuH/tfqpAutXsgc0DQk=
=jBqk
-----END PGP SIGNATURE-----
Adding new machines on a maintenance branch seems somewhat odd as new somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?
Frans
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 3 lines · Frans Meulenbroeks
Adding new machines on a maintenance branch seems somewhat odd as new somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?
Since you aren't using, developing or supporting 2011.03-maintenance, I strongly object to your usage of 'we'.
Furthermore, this isn't the first time that new machines would get added to 2011.03-maintenance.
People really should read
http://wiki.openembedded.org/index.php/2011.03-maintenance
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNlF/PMkyGM64RGpERAh/tAKCwDlaBHSrMDziiP1j/lHAga2zyqQCfT+Ke FRylHre7/eQRdNlkDw3Xe94=
=6IbX
-----END PGP SIGNATURE-----
2011/3/31 Koen Kooi <[email protected]>:
Quoted 10 lines
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 3 lines · Frans Meulenbroeks
Adding new machines on a maintenance branch seems somewhat odd as new somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?Since you aren't using, developing or supporting 2011.03-maintenance, I strongly object to your usage of 'we'.
I don't think you know what I am using, let alone what I am developing at the moment, or my plans to support things.
Also the we was a general tone of voice meaning "we as OE".
But somehow I guess this is the hostile and unfriendly response to be expected from you.
Instead of stimulating people to think with you, you bash them away. And then tomorrow complain that people do not participate. Now how would that come?
Quoted 3 lines
Furthermore, this isn't the first time that new machines would get added to 2011.03-maintenance.
which might not be a good plan either.
Quoted 3 lines
People really should read
http://wiki.openembedded.org/index.php/2011.03-maintenance
Which does not speficy what should and should not be added (apart from:
"Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). "
)
Frans,
Before this spins into a long thread of who did what to who, let's try reinterpreting Koen's answer;
The pull request is in line with the policy from this branch defined in the wiki. Also, prior requests have also added new machines.
If you disagree with the policies that this branch is using, you may ask if the people using and maintaining the branch would like to update the policy to reflect no new machines will be added. If they disagree with you, and you still feel strongly, start your own support branch.
Philip
Quoted 44 lines · Frans Meulenbroeks
2011/3/31 Koen Kooi<[email protected]>:
Quoted 10 lines
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 3 lines · Frans Meulenbroeks
Adding new machines on a maintenance branch seems somewhat odd as new somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?Since you aren't using, developing or supporting 2011.03-maintenance, I strongly object to your usage of 'we'.
I don't think you know what I am using, let alone what I am developing at the moment, or my plans to support things.
Also the we was a general tone of voice meaning "we as OE".
But somehow I guess this is the hostile and unfriendly response to be expected from you.
Instead of stimulating people to think with you, you bash them away. And then tomorrow complain that people do not participate. Now how would that come?Quoted 3 lines
Furthermore, this isn't the first time that new machines would get added to 2011.03-maintenance.
which might not be a good plan either.
Quoted 3 lines
People really should read
http://wiki.openembedded.org/index.php/2011.03-maintenanceWhich does not speficy what should and should not be added (apart from:
"Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). "
)_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 3 lines · Frans Meulenbroeks
Adding new machines on a maintenance branch seems somewhat odd as new somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?
To be clear, I do not have a problem with backporting support for new hardware nor support for new recipes to 2011.03-maintenance so long as (as stated on the wiki page) they are first and foremost backports and secondly something the the users of the branch desire.
- --
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNlLALAAoJEI4NMjfc3nJxrIQH/3yOQmPPBXVjZjYo4wHtZF1Q xZ8MZAK6X5NoDkBMZGwMZP0uGAHYeq4FW+C5oMhGQ/Woq0mXHL7MVUUThXL5gGUi 0wH82tw/Pp8hEJjtWey4f9I2sKXDKI0Twa0At5+Ux+VhYsHtIbO3G6Ats029x1dJ XcXSGvAjZbEcB/GZE8j5UXY9OZZmJXwRQMrz2DGLOMzT4BR5V2aLzyCSPGKD/N1u D1DgiOJ/xgzOsNmK0yvfWtszyc84GbFKmwbZ3nRvz5FB/fyuW00kB6R6f3a9LQmf eWMXXy4zI0bLcU+S/TL7kR9ZSnEHqbwZnnYM+ubw0PAqFuDY2XP9TyCjS+U78WQ= =3EPj
-----END PGP SIGNATURE-----
2011/3/31 Tom Rini <[email protected]>:
Quoted 5 lines
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On 03/31/2011 03:51 AM, Frans Meulenbroeks wrote:
Quoted 8 lines
Quoted 3 lines
Adding new machines on a maintenance branch seems somewhat odd as new somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?To be clear, I do not have a problem with backporting support for new hardware nor support for new recipes to 2011.03-maintenance so long as (as stated on the wiki page) they are first and foremost backports and secondly something the the users of the branch desire.
Tom, Philip, thanks for your explanation.
As it stands we have no backported patches yet, but they might show up. Koen's rude reply mostly vaporized my interest to contribute (and instead keep my patches locally), but your reply at least encourages it to reconsider.
Best regards, Frans.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 9 lines · Koen Kooi
Quoted 5 lines · Denys Dmytriyenko
Tom,
Please pull these 8 commits for the external Angstrom toolchain fix, qt4 security advisory fix, as well as for addition of new TI machines. All are cherry picked from oe.dev
Merging it like this creates a few broken commits because the machines were added first. Is that really what we want?
We do not. Denys, please re-order the commits so that things are building in each commit. Thanks!
- --
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNlK+EAAoJEI4NMjfc3nJxFiAIAKTxXOFRRJ1EmYy3meXOX3yJ WVaXrFmCYcFSU+E9YcFuW9NPd1k4rpSZfI7n4Ezdsqo+GiwMmNwFbAm63DL0al99 t/aEsSHxXsaoj++M529hTmnyS66WodqlYgIxbi8nzNx/ETYDyenQN1I278Ums3b3 RtTIsYJVHCthQTK0991lmjyqC9cFGKSyW2j4J3bLrozdP2tOIqt5j/rXOAnsTNK0 O/OonrOewcqolzSpEFRmwgvKTiB77q7VDYTJRWSZ/tZ2sx8Z1ZJ59Ms2KMB+CvMJ MBT0zQgtJrSwizrCNUemeLYyDBdRb771e2A9trOEcFw54TeenMzeYm8Z60+iQQE= =j3tp
-----END PGP SIGNATURE-----
Quoted 11 lines · Tom Rini
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 7 lines · Koen Kooi
Quoted 5 lines · Denys Dmytriyenko
Tom,
Please pull these 8 commits for the external Angstrom toolchain fix, qt4 security advisory fix, as well as for addition of new TI machines. All are cherry picked from oe.dev
Quoted 5 lines
Quoted 2 lines
Merging it like this creates a few broken commits because the machines were added first. Is that really what we want?
We do not. Denys, please re-order the commits so that things are building in each commit. Thanks!
Done. Please check the same tree and branch. Or do you want me to send a new pull request?
Signature · 1 line
Denys