<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-raspberrypi.git/conf, branch dunfell</title>
<subtitle>Mirror of http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi</subtitle>
<id>https://git.enea.com/cgit/linux/meta-raspberrypi.git/atom?h=dunfell</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/atom?h=dunfell'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/'/>
<updated>2021-06-07T11:59:57+00:00</updated>
<entry>
<title>layer.conf: Define LAYERDEPENDS</title>
<updated>2021-06-07T11:59:57+00:00</updated>
<author>
<name>Andrei Gherzan</name>
<email>andrei@gherzan.com</email>
</author>
<published>2021-05-25T17:39:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=ee5a06b7f0c1a3fa0a3f7c3b047f02b9deacbb67'/>
<id>urn:sha1:ee5a06b7f0c1a3fa0a3f7c3b047f02b9deacbb67</id>
<content type='text'>
We should currently only depend on core - everything should be handled
through dynamic layers.

Signed-off-by: Andrei Gherzan &lt;andrei@gherzan.com&gt;
</content>
</entry>
<entry>
<title>Revert "libcamera: Define packageconfig to enable rpi pipeline"</title>
<updated>2020-11-09T11:02:58+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2020-11-06T21:05:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=987993209716302eb8f314f69a2a3340555f94d8'/>
<id>urn:sha1:987993209716302eb8f314f69a2a3340555f94d8</id>
<content type='text'>
This reverts commit a27f10b76cb1dbf089a3f0980e97f1931b090f17.

This was backported to dunfell together with many other changes in:
https://github.com/agherzan/meta-raspberrypi/pull/754

but 202002 version in dunfell fails with:
ERROR: QA Issue: libcamera: configure was passed unrecognised options: pipelines [unknown-configure-option]

202008 version in gatesgarth is fine, it was added in March:
https://git.linuxtv.org/libcamera.git/commit/meson_options.txt?id=ee7e2c93dfbf34b3500c895115c516e5e90d3e31

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>rpi-default-settings: Replace default parselogs with parselogs_rpi</title>
<updated>2020-11-04T12:09:34+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2020-10-06T04:25:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=67baec35a3cabb0b92dea31d71c59752ae8123f7'/>
<id>urn:sha1:67baec35a3cabb0b92dea31d71c59752ae8123f7</id>
<content type='text'>
rpi kernel spits out additional errors in kernel logs which should be
ignored, there is no easy way to extend parselogs testcase other than
inheriting it into another testcase and use that testcase instead

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>libcamera: Define packageconfig to enable rpi pipeline</title>
<updated>2020-11-04T12:09:34+00:00</updated>
<author>
<name>Madhavan Krishnan</name>
<email>madhavan.krishnan@linaro.org</email>
</author>
<published>2020-08-28T14:07:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=a27f10b76cb1dbf089a3f0980e97f1931b090f17'/>
<id>urn:sha1:a27f10b76cb1dbf089a3f0980e97f1931b090f17</id>
<content type='text'>
libcamera middleware has supported many pipelines for video frames capturing.
So defined the packageconfig, to enable the rpi pipeline and to capture frames
using the rpi camera sensor.

Signed-off-by: Madhavan Krishnan &lt;madhavan.krishnan@linaro.org&gt;
</content>
</entry>
<entry>
<title>layer.conf: Remove older releases from LAYERSERIES_COMPAT</title>
<updated>2020-11-03T15:24:09+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2020-11-01T15:45:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=806575fc1d1ea3a6852210b83be9f2999d93b0da'/>
<id>urn:sha1:806575fc1d1ea3a6852210b83be9f2999d93b0da</id>
<content type='text'>
* since
  https://github.com/agherzan/meta-raspberrypi/commit/36c3c2e7ca09806da460328767565bbf872a6ad8
  which renamed gstreamer1.0-omx_1.14%.bbappend to gstreamer1.0-omx_1.16%.bbappend it didn't
  parse with zeus and older
* with zeus it parses OK, but I believe people who use meta-raspberrypi
  from dunfell branch in zeus builds should rather ask for backports they
  are missing in zeus branch

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>rpi-default-versions: Switch defaults to 5.4</title>
<updated>2020-08-26T12:53:39+00:00</updated>
<author>
<name>Pierre-Jean Texier</name>
<email>pjtexier@koncepto.io</email>
</author>
<published>2020-07-26T11:58:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=659b33b3d03d30fc17927e56675ff46132079d57'/>
<id>urn:sha1:659b33b3d03d30fc17927e56675ff46132079d57</id>
<content type='text'>
Linux Kernel 5.4 is now considered stable.

See [1] to check the current apt stable kernel.

[1] - https://github.com/raspberrypi/firmware/blob/stable/extra/uname_string7

Signed-off-by: Pierre-Jean Texier &lt;pjtexier@koncepto.io&gt;
</content>
</entry>
<entry>
<title>Generalize the naming of the bootfiles deploy directory</title>
<updated>2020-08-10T10:10:11+00:00</updated>
<author>
<name>Jeff Ithier</name>
<email>ithijme@gmail.com</email>
</author>
<published>2020-07-25T06:56:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=4869bb1b9565d10a12e46fd0c306c15e2e0bafeb'/>
<id>urn:sha1:4869bb1b9565d10a12e46fd0c306c15e2e0bafeb</id>
<content type='text'>
The raspberry pi 4 variant has a BCM2711 chip, however it still
uses the same boot files as the BCM2835 used in previous generations.
This change generalizes the naming of the directory generated in the
$DEPLOY_DIR to avoid the implication that the files are only
meant for the BCM2835.

Signed-off-by: Jeff Ithier &lt;ithijme@gmail.com&gt;
</content>
</entry>
<entry>
<title>conf/machine/include/rpi-base.inc: Added can1 interface to bsp</title>
<updated>2020-08-10T10:10:11+00:00</updated>
<author>
<name>colin</name>
<email>colinmca242@gmail.com</email>
</author>
<published>2020-07-09T14:13:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=c2b2d783ac4e87a9875efa096baab1a6a2440bae'/>
<id>urn:sha1:c2b2d783ac4e87a9875efa096baab1a6a2440bae</id>
<content type='text'>
The device tree only supports a single CAN interface.  This prevents
compatiblity with dual-CAN boards like the PiCAN2 Duo.

The mcp2515-can1 device tree blob for overlay was added to RPI_KERNEL_DEVICETREE_OVERLAYS in order to support dual-CAN hats.

Signed-off-by: Colin McAllister &lt;colinmca242@gmail.com&gt;
</content>
</entry>
<entry>
<title>Revert "Generalize the naming of the bootfiles deploy directory"</title>
<updated>2020-08-10T10:10:11+00:00</updated>
<author>
<name>Andrei Gherzan</name>
<email>andrei@gherzan.ro</email>
</author>
<published>2020-08-06T10:53:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=7a2624d5ba0e9d7f8a4b5f120e1e13759373f652'/>
<id>urn:sha1:7a2624d5ba0e9d7f8a4b5f120e1e13759373f652</id>
<content type='text'>
This reverts commit a907c3261ef583f898803706cd596d372c6644cb.
</content>
</entry>
<entry>
<title>Generalize the naming of the bootfiles deploy directory</title>
<updated>2020-07-27T17:02:17+00:00</updated>
<author>
<name>Jeff Ithier</name>
<email>ithijme@gmail.com</email>
</author>
<published>2020-07-25T06:56:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-raspberrypi.git/commit/?id=a907c3261ef583f898803706cd596d372c6644cb'/>
<id>urn:sha1:a907c3261ef583f898803706cd596d372c6644cb</id>
<content type='text'>
The raspberry pi 4 variant has a BCM2711 chip, however it still
uses the same boot files as the BCM2835 used in previous generations.
This change generalizes the naming of the directory generated in the
$DEPLOY_DIR to avoid the implication that the files are only
meant for the BCM2835.

Signed-off-by: Jeff Ithier &lt;ithijme@gmail.com&gt;
</content>
</entry>
</feed>
