<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/conf, branch hardknott</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=hardknott</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=hardknott'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2022-03-02T00:22:13+00:00</updated>
<entry>
<title>uninative: Upgrade to 3.5</title>
<updated>2022-03-02T00:22:13+00:00</updated>
<author>
<name>Michael Halstead</name>
<email>mhalstead@linuxfoundation.org</email>
</author>
<published>2022-02-11T18:10:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ee5299bca182e86adb513bc80c19bde9b8aade51'/>
<id>urn:sha1:ee5299bca182e86adb513bc80c19bde9b8aade51</id>
<content type='text'>
Add support for glibc 2.35.

(From OE-Core rev: 5bde365accec6837dc5751e1ac01b767898a2c5d)

Signed-off-by: Michael Halstead &lt;mhalstead@linuxfoundation.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 347b8c87fb4e2c398644f900728cf6e22ba4516d)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
(cherry picked from commit eeae63c343c8ebd418679915ee20aa8c02fa0fdc)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>default-distrovars.inc: Switch connectivity check to a yoctoproject.org page</title>
<updated>2022-02-20T15:32:27+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-02-11T17:42:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=35eb6d39517ccf9f69b394fa0d6e51f52d48ebdf'/>
<id>urn:sha1:35eb6d39517ccf9f69b394fa0d6e51f52d48ebdf</id>
<content type='text'>
example.com is proving unreliable at present so switch to our own connectivity
page instead. That page is very simple avoiding app overhead on our web server
which was an original reason for switching to example.com.

(From OE-Core rev: 3d9f68e06736817871d8694fe0c6e779c005872b)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit dc6b043cb75c5751b5a98afd2201aa31f9b4b9f6)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: upgrade to gcc-10.3 version</title>
<updated>2022-01-31T21:56:01+00:00</updated>
<author>
<name>Pgowda</name>
<email>pgowda.cve@gmail.com</email>
</author>
<published>2022-01-22T11:15:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8e1796eef4e6aae3ad0673583d505c47a5563c2a'/>
<id>urn:sha1:8e1796eef4e6aae3ad0673583d505c47a5563c2a</id>
<content type='text'>
gcc-10.2 in Hardknott branch has been upgraded to gcc-10.3 version
that includes many bug fixes.
Regression tested on X86-64, Arm and Aarch64 without issues.

(From OE-Core rev: 87fbe11fbe04a6f2d3e798d282935b26fbc43e77)

Signed-off-by: pgowda &lt;pgowda.cve@gmail.com&gt;
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tune-cortexa72: Drop the redundant cortexa72-crc tune</title>
<updated>2022-01-31T21:56:01+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2022-01-16T14:49:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=962e5227e8b79d61c3d18746ef3c6a8787e4f2bf'/>
<id>urn:sha1:962e5227e8b79d61c3d18746ef3c6a8787e4f2bf</id>
<content type='text'>
We have enabled the crc extension by default for cortexa72 in patch
("tune-cortexa72: Enable the crc extension by default for cortexa72"),
then the cortexa72-crc seems redundant. So drop it. We also rename the
cortexa72-crc-crypto to cortexa72-crypto. With these changes, it will
break the BSPs which used these two tunes, but it should be easy to fix.

(From OE-Core rev: 03cebdd7ef923a8ac5c8b7c12c7cefe7ca0158db)

(From OE-Core rev: ca4070f327068992de24b00810c019e0b118f6ab)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
[Kevin: Convert to the old style override syntax]
Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tune-cortexa72: Enable the crc extension by default for cortexa72</title>
<updated>2022-01-31T21:56:01+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2022-01-16T14:49:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5f6eb7c6d82a9eed5907a3345a2196c085dd35e8'/>
<id>urn:sha1:5f6eb7c6d82a9eed5907a3345a2196c085dd35e8</id>
<content type='text'>
The crc extension is optional for the ARMv8.0 but is mandatory for the
cortexa72, so there is no reason not to enable it for the cortexa72
tune. With this change, the cortexa72-crc seems redundant. But we
had better to keep it to be compatible with the BSP which already used
that tune.

(From OE-Core rev: ca50267ab568d2f688844cb7c6cd867ed34168db)

(From OE-Core rev: 0e80b75064ba2662fdd80332ff3197cd5e3cd3c9)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
[Kevin: Convert to the old style override syntax]
Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tune-cortexa72: remove crypto for the default cortex-a72</title>
<updated>2022-01-31T21:56:01+00:00</updated>
<author>
<name>Jagadeesh Krishnanjanappa</name>
<email>workjagadeesh@gmail.com</email>
</author>
<published>2022-01-16T14:49:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d8385d1db5cc0a1ba512f5d95fe79da8d1a5a2f6'/>
<id>urn:sha1:d8385d1db5cc0a1ba512f5d95fe79da8d1a5a2f6</id>
<content type='text'>
The cryptographic unit is optional for the Cortex-A72, but it was
included by default previously.  This breaks building systems that
lack this functionality when using tune-cortexa72.inc.

To correct this, add a crypto entry in the tune file.  Since CRC is
optional for ARMv8.0, do the same thing while we're at it.

For platforms that had been happily using tune-cortexa72.inc, a slight
degradation of performance will occur using the default.  To correct
this, simply add:
DEFAULTTUNE = "cortexa72-crc-crypto"

(From OE-Core rev: 2568d537087adb0b592aa250bf628a7b48c3a9d3)

(From OE-Core rev: ee249ca4d5020c16100e07ee1b5974237de29e29)

Signed-off-by: Jagadeesh Krishnanjanappa &lt;workjagadeesh@gmail.com&gt;
Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt; (rewording commit message)
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
[Kevin: Convert to the old style override syntax]
Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>armv9a/tune: Add the support for the Neoverse N2 core</title>
<updated>2022-01-25T12:07:01+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2022-01-15T01:50:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6fac5cc9f37d9fc405ea948380581ce313d1d5c9'/>
<id>urn:sha1:6fac5cc9f37d9fc405ea948380581ce313d1d5c9</id>
<content type='text'>
This adds the support for the Neoverse N2 core, even though the
Neoverse N2 core implements the Arm v9.0-A architecture, but the support
of it in GCC is based on the Arm v8.5-A architecture. Please see the
commit 50d9db203bc3 ("aarch64: Add support for Neoverse N2 CPU") in GCC
for more detail.

(From OE-Core rev: 37597397f03b6b0082a702147dc536ff8b2fa7a3)

(From OE-Core rev: 3ceee568313ea7cd3afe33df8119319644e12fa4)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
[Kevin: Convert to the old style override syntax]
Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>arch-armv8-5a.inc: Add tune include for armv8.5a</title>
<updated>2022-01-25T12:07:01+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2022-01-15T01:50:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a87f135041c3258faf5692919716f9219bf99446'/>
<id>urn:sha1:a87f135041c3258faf5692919716f9219bf99446</id>
<content type='text'>
This adds support for the armv8.5a architecture and the crypto
extension.

(From OE-Core rev: 0cb1a6d9cb4c32526d79dad93c8053b3793053f8)

(From OE-Core rev: 8cd6d67c08b275f81a5467aeba1192bce957f604)

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
[Kevin: Convert to the old style override syntax]
Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-extra-exclusions: add db CVEs to exclusion list</title>
<updated>2021-12-15T07:40:29+00:00</updated>
<author>
<name>Steve Sakoman</name>
<email>steve@sakoman.com</email>
</author>
<published>2021-12-05T17:21:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a96b0ad6eb9be742d640638ddd4a9d875d7694c4'/>
<id>urn:sha1:a96b0ad6eb9be742d640638ddd4a9d875d7694c4</id>
<content type='text'>
Since Oracle relicensed bdb, the open source community is slowly but surely replacing bdb with
supported and open source friendly alternatives. As a result these CVEs are unlikely to ever be fixed.

(From OE-Core rev: b3056b937a76ddd6c02cd6b17e7a0c178931add4)

Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 679fc70f907fb221f4541ebf30c1610e937209b7)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>uninative: Add version to uninative tarball name</title>
<updated>2021-12-05T12:35:43+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2021-11-12T13:51:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5648b1612a76dd5fc93a106b7b323bc1ff41e34c'/>
<id>urn:sha1:5648b1612a76dd5fc93a106b7b323bc1ff41e34c</id>
<content type='text'>
uninative works via hashes and doesn't need the version in the tarball name but
it does make things easier to inspect in DL_DIR. There were reasons such as
ease of publication of the build tarballs but we can handle those differently
now and the signature issues from the early code aren't an issue now. From 3.4
onwards we can use a version'd name.

[YOCTO #12970]

(From OE-Core rev: e3ba0041ccb9633ec21241cb6852aa50c2663677)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit dadba70d6a24d8ebb5576598efffa973151c7218)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
