<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/pepe2k/scripts/target-metadata.pl, branch v21.02.1</title>
<subtitle>Staging tree of Piotr Dymacz</subtitle>
<id>https://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.1</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.1'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/'/>
<updated>2021-01-15T08:42:21Z</updated>
<entry>
<title>scripts: target-metadata don't add PROFILES twice</title>
<updated>2021-01-15T08:42:21Z</updated>
<author>
<name>Paul Spooren</name>
</author>
<published>2020-04-15T00:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=4dad3244297d8315b25ef029286681be4e7123a0'/>
<id>urn:sha1:4dad3244297d8315b25ef029286681be4e7123a0</id>
<content type='text'>
Since 4ee3cf2b5a profiles with alternative vendor names may appear
multiple times in `tmp/.targetinfo` or `.targetinfo` (for
ImageBuilders).

The `target-metadata.pl` script adds these profiles then twice to
`PROFILE_NAMES` and the ImageBuilder show the profile twice when running
`make info`.

This patch removes duplicate profile IDs and only adds them once to
`.profiles.mk`.

Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
</content>
</entry>
<entry>
<title>build: define PWM_SUPPORT arch feature flag</title>
<updated>2020-09-25T17:32:33Z</updated>
<author>
<name>Christian Lamparter</name>
</author>
<published>2020-08-29T21:07:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=f6fbc397066e57d180aebc62e6bf52464d06bd76'/>
<id>urn:sha1:f6fbc397066e57d180aebc62e6bf52464d06bd76</id>
<content type='text'>
As the PWM has its own sub-system in the Linux kernel,
I think it should be handled in the same way as GPIO, RTC, PCI...

This patch introduces a specific feature flag "pwm" and the
"leds-pwm" kernel module as the first customer.

Signed-off-by: Christian Lamparter &lt;chunkeey@gmail.com&gt;
</content>
</entry>
<entry>
<title>build: add option to mark devices as BROKEN</title>
<updated>2020-07-30T19:49:07Z</updated>
<author>
<name>Adrian Schmutzler</name>
</author>
<published>2020-07-28T18:47:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=1d5260cf72763d92ba8c4aff61b3605e37af614a'/>
<id>urn:sha1:1d5260cf72763d92ba8c4aff61b3605e37af614a</id>
<content type='text'>
By specifying "BROKEN := 1" or "BROKEN := y" for a device, it will be
hidden (and deselected) by default. By that, it provides a stronger
option to "disable" a device beyond just using DEFAULT := n.

To make these devices visible, just enable the BROKEN option in
developer settings as already implemented for targets and packages.

Signed-off-by: Adrian Schmutzler &lt;freifunk@adrianschmutzler.de&gt;
</content>
</entry>
<entry>
<title>build: allow overriding default selection state for devices</title>
<updated>2019-08-13T20:13:18Z</updated>
<author>
<name>Jonas Gorski</name>
</author>
<published>2019-08-13T10:33:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=7546be60074e452751ba2a48eddbc13910bec708'/>
<id>urn:sha1:7546be60074e452751ba2a48eddbc13910bec708</id>
<content type='text'>
Allow overriding the default selection state for Devices, similar to
setting a default for packages.

E.g. by setting DEFAULT to n, they won't be selected by default anymore
when enabling all device in the multi device profile.

This allows preventing images being built by the default config for
known broken devices, devices without enough RAM/flash, or devices not
working with a certain kernel versions.

This does not prevent the devices from being manually selected or images
being built by the ImageBuilder. These devices often still have worth
with a reduced package-set, or as a device for regression testing, when
no better device is available.

Signed-off-by: Jonas Gorski &lt;jonas.gorski@gmail.com&gt;
</content>
</entry>
<entry>
<title>build: add a config option for enabling a testing version of the target kernel</title>
<updated>2019-05-11T09:37:10Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2019-04-27T17:13:07Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=85017c40f4efce11edd77e0caac14aed0fd690eb'/>
<id>urn:sha1:85017c40f4efce11edd77e0caac14aed0fd690eb</id>
<content type='text'>
If the target supports a newer kernel version that is not used by default
yet, it can be enabled with this option

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
<entry>
<title>build: switch default target from ar71xx to ath79</title>
<updated>2019-04-11T16:14:01Z</updated>
<author>
<name>Kevin Darbyshire-Bryant</name>
</author>
<published>2019-04-11T15:38:01Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=750a57b8364c2ef9e021b9428725585e47864163'/>
<id>urn:sha1:750a57b8364c2ef9e021b9428725585e47864163</id>
<content type='text'>
ar71xx is in the process of being deprecated as a target accepting new
devices.  The replacement target for the same hardware is DTS
based ath79.

Switch the default build target selection from ar71xx to ath79.

This is intended to encourage DTS takeup &amp; support for ath79 and longer
term will also aid kernel upstream support.

Signed-off-by: Kevin Darbyshire-Bryant &lt;ldir@darbyshire-bryant.me.uk&gt;
</content>
</entry>
<entry>
<title>IB: fix generating .profile.mk for profiles without metadata</title>
<updated>2019-03-27T21:53:14Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2019-03-27T21:52:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=7204736076b277977388ad43cd69f221a377ed7e'/>
<id>urn:sha1:7204736076b277977388ad43cd69f221a377ed7e</id>
<content type='text'>
Fixes d6fa04a437 ("IB: include SUPPORTED_DEVICES in 'make info' output")

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>IB: include SUPPORTED_DEVICES in 'make info' output</title>
<updated>2019-03-11T04:32:29Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2019-03-11T04:32:29Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=d6fa04a437033d4bdfa1b0d90a4786bfe492f749'/>
<id>urn:sha1:d6fa04a437033d4bdfa1b0d90a4786bfe492f749</id>
<content type='text'>
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>ib: display whether profile comes with image metadata</title>
<updated>2019-03-06T13:50:42Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2019-03-06T13:45:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=13c379e5c6e37b3822bf6e4e18cc6317e5b40fbb'/>
<id>urn:sha1:13c379e5c6e37b3822bf6e4e18cc6317e5b40fbb</id>
<content type='text'>
Having image metadata (and signature) appended is a condition for
semi-automated sysupgrade, hence IB needs to be able to tell which
images will end up with metadata.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>build: add support for enabling the rootfs/boot partition size option via target feature</title>
<updated>2018-09-03T10:06:24Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2018-08-26T17:36:33Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=00f030a9c67c551e675364d73234a4cba273b420'/>
<id>urn:sha1:00f030a9c67c551e675364d73234a4cba273b420</id>
<content type='text'>
Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
</feed>
