<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/blogic/config, branch master</title>
<subtitle>John Crispins staging tree</subtitle>
<id>https://git.openwrt.org/openwrt/staging/blogic/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/blogic/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/'/>
<updated>2019-07-02T14:32:47Z</updated>
<entry>
<title>Make linux kernel builds reproducible when BUILDBOT selected</title>
<updated>2019-07-02T14:32:47Z</updated>
<author>
<name>Alexander Couzens</name>
</author>
<published>2019-06-12T00:59:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=fdd0a8d49118134070c13231b6d10ec88b9105da'/>
<id>urn:sha1:fdd0a8d49118134070c13231b6d10ec88b9105da</id>
<content type='text'>
The linux kernel is not reproducible because the build user
and domain is included into the kernel. Set the build user
to `builder` and build domain to buildhost.

It's also possible to build reproducible builds by setting
KERNEL_BUILD_USER KERNEL_BUILD_DOMAIN to static values.

Signed-off-by: Alexander Couzens &lt;lynxis@fe80.eu&gt;
</content>
</entry>
<entry>
<title>build: enable gzipped images for armvirt and malta</title>
<updated>2019-06-25T14:12:22Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2019-06-25T05:54:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=9c8e0b0e8af9827dc83989f3b18b4b18c47eb554'/>
<id>urn:sha1:9c8e0b0e8af9827dc83989f3b18b4b18c47eb554</id>
<content type='text'>
As we're now going to pad all images by default to 128MiB let's enable
compression of the images for armvirt and malta in order to save some
space and bandwidth.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>build: make TARGET_ROOTFS_PARTSIZE 128MiB by default</title>
<updated>2019-06-25T14:12:21Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2019-06-22T06:13:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=469ba337a73586573699be3999bfdf6f9ebe404f'/>
<id>urn:sha1:469ba337a73586573699be3999bfdf6f9ebe404f</id>
<content type='text'>
As we're now going to pad all images by default, lets decrease the
default rootfs partition size from 256MiB to 128MiB in order to save
some space.

I'm keeping it above 100MiB in order to keep current behavior, where
overlay filesystem is using F2FS.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>build: remove TARGET_IMAGES_PAD option</title>
<updated>2019-06-25T14:12:21Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2019-03-27T10:31:14Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=d03ef97c1b57b2b5588115d3b7c7355399874aa3'/>
<id>urn:sha1:d03ef97c1b57b2b5588115d3b7c7355399874aa3</id>
<content type='text'>
It's being used only in x86 target to produce combined images, where
it's mandatory to have padded images in order to produce working
squashfs combined images usable in QEMU.

Currently we're producing unusable x86 combined squashfs images
(18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD,
thus providing very small space for the overlay filesystem, leading to
the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU:

 root@(none):/# mount | egrep 'root|overlay'
  /dev/root on /rom type squashfs
  /dev/loop0 on /overlay type ext4
  overlayfs:/overlay on / type overlay

 root@(none):/# df -h | egrep 'root|overlay|Size'
  Filesystem                Size      Used Available Use% Mounted on
  /dev/root                 2.5M      2.5M         0 100% /rom
  /dev/loop0              113.0K      8.0K     97.0K   8% /overlay
  overlayfs:/overlay      113.0K      8.0K     97.0K   8% /

So we should rather ensure proper image padding in image generation code
and we shouldn't rely on config options in order to generate usable
images.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>config: enable some useful features on !SMALL_FLASH devices</title>
<updated>2019-06-12T21:33:45Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2018-12-29T05:51:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=fcb41decf6c622482b20af45a77e62db8d95046e'/>
<id>urn:sha1:fcb41decf6c622482b20af45a77e62db8d95046e</id>
<content type='text'>
enable kernel features needed for procd-ujail, procd-seccomp, lxc and
more on devices with big enough flash. Those packages are currently
useless in binary builds due to missing kernel features.
Enable the features on devices which can bare with the extra space
consumption.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>lantiq/xrx200: enable initramfs images</title>
<updated>2019-05-15T11:34:23Z</updated>
<author>
<name>Stijn Segers</name>
</author>
<published>2019-04-27T16:23:21Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=5cd49395d35eade0d07b9db8c5ea47037de8db2f'/>
<id>urn:sha1:5cd49395d35eade0d07b9db8c5ea47037de8db2f</id>
<content type='text'>
Commit eae6cac6a3 ("lantiq: add support for AVM FRITZ!Box 7362 SL"), but
one needs an initramfs image to flash OpenWrt from stock firmware (as
described in the commit log). This patch has the initramfs image built
by default.

Thanks to blogic (for pointing to the FEATURES declaration in the target
Makefiles) and Musashino on the forum for suggesting
config/Config-images.in needed editing too. While at it, reorder the
TARGET_INITRAMFS_COMPRESSION_LZMA declarations alphabetically.

This patch will result in initramfs images for all lantiq subtargets
that have the ramdisk flag set. I tested on the falcon and ase
subtargets, which lack that flag, to confirm they don't produce any
initramfs images with this patch - which they do not.

Given the limited scope of the lantiq (sub)target(s), blogic indicated
this should be OK.

Signed-off-by: Stijn Segers &lt;foss@volatilesystems.org&gt;
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
[fixed the wrong reference to eae6cac6a3 commit]
</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/blogic/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>config: kernel: Add KPROBE_EVENTS config option</title>
<updated>2019-05-05T12:41:49Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2019-04-10T15:07:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=97d3f800a85ef341787eb1dcff41d0ad3fd7b7d0'/>
<id>urn:sha1:97d3f800a85ef341787eb1dcff41d0ad3fd7b7d0</id>
<content type='text'>
Upstream has renamed KPROBE_EVENT to KPROBE_EVENTS in the following
commit:

 commit 6b0b7551428e4caae1e2c023a529465a9a9ae2d4
 Author: Anton Blanchard &lt;anton@samba.org&gt;
 Date:   Thu Feb 16 17:00:50 2017 +1100

     perf/core: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS

     We have uses of CONFIG_UPROBE_EVENT and CONFIG_KPROBE_EVENT as
     well as CONFIG_UPROBE_EVENTS and CONFIG_KPROBE_EVENTS.

     Consistently use the plurals.

So I'm adding this plural option in order to make kconfig happy and stop
asking about it if kernel is compiled with verbose logging:

  Enable kprobes-based dynamic events (KPROBE_EVENTS) [Y/n/?] (NEW)

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>mvebu: make bootfs size for sdcard image configurable</title>
<updated>2019-04-06T14:31:10Z</updated>
<author>
<name>Tomasz Maciej Nowak</name>
</author>
<published>2019-03-28T17:07:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=910eb994eb6db33998cf1877f6a258ae49f9a67a'/>
<id>urn:sha1:910eb994eb6db33998cf1877f6a258ae49f9a67a</id>
<content type='text'>
Let's take this oportunity to implement boot-part and rootfs-part feature
flags.

Signed-off-by: Tomasz Maciej Nowak &lt;tomek_n@o2.pl&gt;
</content>
</entry>
<entry>
<title>build: remove leftovers from previous x86 commits</title>
<updated>2019-02-17T17:22:40Z</updated>
<author>
<name>Tomasz Maciej Nowak</name>
</author>
<published>2019-01-13T20:37:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blogic/commit/?id=bb0e4f9fb0c101b86b1a0c2785fec9b38b19fd02'/>
<id>urn:sha1:bb0e4f9fb0c101b86b1a0c2785fec9b38b19fd02</id>
<content type='text'>
VBoxManage is not used and the image is created with proper permisions:
0f5d0f6  image: use internal qemu-img for vmdk and vdi images drop host
         dependencies on qemu-utils and VirtualBox

Unreachable config symbols:
9e0759e  x86: merge all geode based subtargets into one

No need to define those symbols since x86_64 is subtarget of x86:
196fb76  x86: make x86_64 a subtarget instead of a standalone target

Unreachable config symbols, so remove GRUB_ROOT:
371b382  x86: remove the xen_domu subtarget

Signed-off-by: Tomasz Maciej Nowak &lt;tomek_n@o2.pl&gt;
</content>
</entry>
</feed>
