* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-05-29 1:29 Bruce Ashfield
2020-05-29 1:29 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.42 Bruce Ashfield
` (4 more replies)
0 siblings, 5 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi Richard,
As discussed earlier, this is the pull request which contains a temporary
revert of the CONFIG_IKHEADERS config change that was causing the
periodic issues.
I added a kernel feature that can be used to enable the configuration from
a recipe, that way I won't leave anyone broken while I continue to debug,
since this still is a problem for anyone that is doing reproducible builds
and wants ikheaders.
This went through AB quick and came back green.
Bruce
The following changes since commit 392ba004f42be2fd9dcf121d3dfa5b414ff83f93:
ref-manual: add PACKAGE_ADD_METADATA documentation (2020-05-27 11:05:04 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.42
linux-yocto-rt/5.4: update to rt24
linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels
linux-yocto: gather reproducibility configs into a fragment
linux-yocto/5.4: update to v5.4.43
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 1/5] linux-yocto/5.4: update to v5.4.42
2020-05-29 1:29 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
@ 2020-05-29 1:29 ` Bruce Ashfield
2020-05-29 1:29 ` [PATCH 2/5] linux-yocto-rt/5.4: update to rt24 Bruce Ashfield
` (3 subsequent siblings)
4 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
1cdaf895c99d Linux 5.4.42
ecb3f529a554 bpf: Test_progs, fix test_get_stack_rawtp_err.c build
aee43146cc10 selftest/bpf: fix backported test_select_reuseport selftest changes
35d9107ad30b libbpf: Extract and generalize CPU mask parsing logic
10cfaa7456d7 Makefile: disallow data races on gcc-10 as well
9972e851b9f4 KVM: x86: Fix off-by-one error in kvm_vcpu_ioctl_x86_setup_mce
9d2487643b4f bpf: Fix sk_psock refcnt leak when receiving message
d41689a34a9d SUNRPC: Revert 241b1f419f0e ("SUNRPC: Remove xdr_buf_trim()")
3a8efe589bb6 ARM: dts: r8a7740: Add missing extal2 to CPG node
cd8ae9b73258 arm64: dts: renesas: r8a77980: Fix IPMMU VIP[01] nodes
c580f2fe3270 ARM: dts: r8a73a4: Add missing CMT1 interrupts
8972721aea41 arm64: dts: imx8mn: Change SDMA1 ahb clock for imx8mn
764715615178 arm64: dts: rockchip: Rename dwc3 device nodes on rk3399 to make dtc happy
64ad7ef3a6e5 arm64: dts: rockchip: Replace RK805 PMIC node name with "pmic" on rk3328 boards
af518b5b77fd arm64: dts: meson-g12-common: fix dwc2 clock names
9b9c52752a11 arm64: dts: meson-g12b-khadas-vim3: add missing frddr_a status property
01febb33cb6e clk: Unlink clock if failed to prepare or enable
e2084a8d5fee Revert "ALSA: hda/realtek: Fix pop noise on ALC225"
5e553801462b usb: gadget: legacy: fix error return code in cdc_bind()
7e5c1db8ad15 usb: gadget: legacy: fix error return code in gncm_bind()
8228b6736964 usb: gadget: audio: Fix a missing error return value in audio_bind()
8ef452001769 usb: gadget: net2272: Fix a memory leak in an error handling path in 'net2272_plat_probe()'
9f65d776756e fanotify: fix merging marks masks with FAN_ONDIR
20a6d2455cde dwc3: Remove check for HWO flag in dwc3_gadget_ep_reclaim_trb_sg()
4f6815e429a8 clk: rockchip: fix incorrect configuration of rk3228 aclk_gpu* clocks
553a2cbca7c3 exec: Move would_dump into flush_old_exec
136353c5066c x86/unwind/orc: Fix error handling in __unwind_start()
91b9ce04ff1f x86: Fix early boot crash on gcc-10, third try
f8e370ccab35 cifs: fix leaked reference on requeued write
4e06196336a1 powerpc/32s: Fix build failure with CONFIG_PPC_KUAP_DEBUG
57aa19acfc22 drm/amd/display: add basic atomic check for cursor plane
97e43314763d ARM: dts: imx6dl-yapp4: Fix Ursa board Ethernet connection
215589310fa2 ARM: dts: imx27-phytec-phycard-s-rdk: Fix the I2C1 pinctrl entries
e1409dc95410 ARM: dts: dra7: Fix bus_dma_limit for PCIe
da55eeb3245a Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()
c6a1ce81b43e usb: xhci: Fix NULL pointer dereference when enqueuing trbs from urb sg list
6bb054f006c3 USB: gadget: fix illegal array access in binding with UDC
e6be4400ac34 usb: cdns3: gadget: prev_req->trb is NULL for ep0
f1a9bed7969a usb: host: xhci-plat: keep runtime active when removing host
b96a62f506ee usb: core: hub: limit HUB_QUIRK_DISABLE_AUTOSUSPEND to USB5534B
93dda4f0e2ff ALSA: usb-audio: Add control message quirk delay for Kingston HyperX headset
3fa58fc9f8c4 ALSA: rawmidi: Fix racy buffer resize under concurrent accesses
04ccdf6b031d ALSA: hda/realtek - Add COEF workaround for ASUS ZenBook UX431DA
c9709800eeeb ALSA: hda/realtek - Limit int mic boost for Thinkpad T530
c737b7533596 USB: usbfs: fix mmap dma mismatch
0432f7632a24 usb: usbfs: correct kernel->user page attribute mismatch
dca0ae3900b3 gcc-10: avoid shadowing standard library 'free()' in crypto
6cbb91bdd3a2 gcc-10: mark more functions __init to avoid section mismatch warnings
7955081a3a65 gcc-10 warnings: fix low-hanging fruit
dff2ce17934c gcc-10: disable 'restrict' warning for now
b8e7b93333db gcc-10: disable 'stringop-overflow' warning for now
9ba07a72fc5e gcc-10: disable 'array-bounds' warning for now
a740b68fd169 gcc-10: disable 'zero-length-bounds' warning for now
8f6a84167e86 Stop the ad-hoc games with -Wno-maybe-initialized
ab638a49a9f3 net/rds: Use ERR_PTR for rds_message_alloc_sgs()
b597815ce1e8 pnp: Use list_for_each_entry() instead of open coding
d4e58131829f NFSv3: fix rpc receive buffer size for MOUNT call
e26e2a3febcb mm, memcg: fix inconsistent oom event behavior
46a22f3ea146 s390/ism: fix error return code in ism_probe()
e1608af17030 hwmon: (da9052) Synchronize access with mfd
6e7253dc4562 RDMA/iw_cxgb4: Fix incorrect function parameters
08f187dbd223 RDMA/core: Fix double put of resource
ee7ce7d7e7c7 IB/core: Fix potential NULL pointer dereference in pkey cache
b491aeec55fe IB/mlx4: Test return value of calls to ib_get_cached_pkey
eaad00390ff9 RDMA/rxe: Always return ERR_PTR from rxe_create_mmap_info()
da532ce587c7 netfilter: nft_set_rbtree: Add missing expired checks
1c235d0eb1f0 netfilter: nft_set_rbtree: Introduce and use nft_rbtree_interval_start()
6259b1c1bca5 SUNRPC: Signalled ASYNC tasks need to exit
d1538d8d6325 nfs: fix NULL deference in nfs4_get_valid_delegation
ea7c4d9e542f arm64: fix the flush_icache_range arguments in machine_kexec
1222b257654b drm/i915/gvt: Fix kernel oops for 3-level ppgtt guest
a308d6e6861d netfilter: conntrack: avoid gcc-10 zero-length-bounds warning
b526c01b38ae NFSv4: Fix fscache cookie aux_data to ensure change_attr is included
021f5799de53 nfs: fscache: use timespec64 in inode auxdata
ef8195ee1618 NFS: Fix fscache super_cookie index_key from changing after umount
32b9de3e935d drm/amdgpu: force fbdev into vram
e1b2b93243ca fork: prevent accidental access to clone3 features
f256dea07774 gfs2: More gfs2_find_jhead fixes
18541e49f70b mmc: block: Fix request completion in the CQE timeout path
e8eb122b9f43 mmc: core: Fix recursive locking issue in CQE recovery path
fdf547a591f5 mmc: core: Check request type before completing the request
3a8bc2ae2f79 mmc: sdhci-pci-gli: Fix can not access GL9750 after reboot from Windows 10
e0830bb37734 mmc: alcor: Fix a resource leak in the error path for ->probe()
62f217e0a9c8 bpf, sockmap: bpf_tcp_ingress needs to subtract bytes from sg.size
ce3193bf8964 bpf, sockmap: msg_pop_data can incorrecty set an sge length
af1f11fe6667 drm/i915: Don't enable WaIncreaseLatencyIPCEnabled when IPC is disabled
0d9bc7986366 i40iw: Fix error handling in i40iw_manage_arp_cache()
95827ac65244 ALSA: firewire-lib: fix 'function sizeof not defined' error of tracepoints format
5d47b3d6b4d2 bpf: Fix error return code in map_lookup_and_delete_elem()
5b96668b63c0 pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler
aec927836c7d pinctrl: qcom: fix wrong write in update_dual_edge
604ad1bb8aae pinctrl: baytrail: Enable pin configuration setting for GPIO chip
960d609dd4dd pinctrl: sunrisepoint: Fix PAD lock register offset for SPT-H
e529b8db9684 ACPI: EC: PM: Avoid premature returns from acpi_s2idle_wake()
9e54afec08f7 IB/hfi1: Fix another case where pq is left on waitlist
d942a6a18463 mmc: sdhci-pci-gli: Fix no irq handler from suspend
171bf6ef038b gfs2: Another gfs2_walk_metadata fix
87954aacd585 ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse
05aae468d31a ipc/util.c: sysvipc_find_ipc() incorrectly updates position index
3c3ade92b62a drm/amdgpu: invalidate L2 before SDMA IBs (v2)
938489ef2902 drm/amdgpu: simplify padding calculations (v2)
eefe5e0bb7b7 drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper()
94cce94badf7 drm/amd/display: Update downspread percent to match spreadsheet for DCN2.1
f4164b29dc08 drm/amd/display: check if REFCLK_CNTL register is present
65f3108cbb1d drm/amd/powerplay: avoid using pm_en before it is initialized revised
8c5f11093ef4 ALSA: hda/hdmi: fix race in monitor detection during probe
4d1a83cb5afe cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once
d12d7bf92b08 selftests/ftrace: Check the first record for kprobe_args_type.tc
2b313699e7a9 dmaengine: mmp_tdma: Reset channel error on release
6c414ddee7f0 dmaengine: mmp_tdma: Do not ignore slave config validation errors
de76c0d4a03c dmaengine: pch_dma.c: Avoid data race between probe and irq handler
c096a8645e3f riscv: fix vdso build with lld
2fffdf4dded1 umh: fix memory leak on execve failure
44ee727013d5 r8169: re-establish support for RTL8401 chip version
e03d3510f45c nfp: abm: fix error return code in nfp_abm_vnic_alloc()
2fbd6eca3711 net: tcp: fix rx timestamp behavior for tcp_recvmsg
fc800ec491c3 netprio_cgroup: Fix unlimited memory leak of v2 cgroups
cab607a627cf net: ipv4: really enforce backoff for redirects
d375d99f8902 net: dsa: loop: Add module soft dependency
b2e8946250c3 hinic: fix a bug of ndo_stop
d07987924a04 dpaa2-eth: prevent array underflow in update_cls_rule()
84916465b0f0 virtio_net: fix lockdep warning on 32 bit
23300d6a39d7 tcp: fix SO_RCVLOWAT hangs with fat skbs
cb4f78986065 tcp: fix error recovery in tcp_zerocopy_receive()
f152793058b5 Revert "ipv6: add mtu lock check in __ip6_rt_update_pmtu"
5f93b45fa58c pppoe: only process PADT targeted at local interfaces
ecb8356aafba net: stmmac: fix num_por initialization
4300e210b005 net: phy: fix aneg restart in phy_ethtool_set_eee
debcbc56fdfc netlabel: cope with NULL catmap
60a4f2ce0596 net: fix a potential recursive NETDEV_FEAT_CHANGE
97e860545e24 dpaa2-eth: properly handle buffer size restrictions
425853cc1160 mmc: sdhci-acpi: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA for AMDI0040
a761f65879e8 selftests/bpf: fix goto cleanup label not defined
2d6d0ce4de03 scsi: sg: add sg_remove_request in sg_write
7d8da6d7d90c net_sched: fix tcm_parent in tc filter dump
e2824505a813 sun6i: dsi: fix gcc-4.8
645b44b6b3b3 virtio-blk: handle block_device_operations callbacks after hot unplug
fbe2c2c50914 drop_monitor: work around gcc-10 stringop-overflow warning
23a0a0914a1e ftrace/selftests: workaround cgroup RT scheduling issues
dbd667a322ac net: moxa: Fix a potential double 'free_irq()'
2bcd4df42d5d net/sonic: Fix a resource leak in an error handling path in 'jazz_sonic_probe()'
e15d3d42900a SUNRPC: Fix GSS privacy computation of auth->au_ralign
3bf0794e7309 SUNRPC: Add "@len" parameter to gss_unwrap()
3c605abef3ee gpio: pca953x: Fix pca953x_gpio_set_config
163b48932571 KVM: arm: vgic: Synchronize the whole guest on GIC{D,R}_I{S,C}ACTIVER read
7abefa3f9a4b net: phy: microchip_t1: add lan87xx_phy_init to initialize the lan87xx phy.
a12f3ad8d952 shmem: fix possible deadlocks on shmlock_user_lock
723090ae8ea6 net: dsa: Do not make user port errors fatal
cbaf23699561 Linux 5.4.41
9bd5a84ceba3 fanotify: merge duplicate events on parent and child
4638e0ff0fa4 fsnotify: replace inode pointer with an object id
03447528a390 bdi: add a ->dev_name field to struct backing_dev_info
25390a31983c bdi: move bdi_dev_name out of line
c1af2c13a4ac mm, memcg: fix error return value of mem_cgroup_css_alloc()
1642f114ce2d scripts/decodecode: fix trapping instruction formatting
2e86e3841c3c iommu/virtio: Reverse arguments to list_add
1a31c4456af9 objtool: Fix stack offset tracking for indirect CFAs
30a38059cdd4 netfilter: nf_osf: avoid passing pointer to local var
4ccbd9c859dd netfilter: nat: never update the UDP checksum when it's 0
634c950c624d arch/x86/kvm/svm/sev.c: change flag passed to GUP fast in sev_pin_memory()
4cbb69b45cad KVM: x86: Fixes posted interrupt check for IRQs delivery modes
db00b1d9d71a x86/unwind/orc: Fix premature unwind stoppage due to IRET frames
c9473a0260b2 x86/unwind/orc: Fix error path for bad ORC entry type
1b4bd44645ac x86/unwind/orc: Prevent unwinding before ORC initialization
511261578b8b x86/unwind/orc: Don't skip the first frame for inactive tasks
162e9f141d96 x86/entry/64: Fix unwind hints in rewind_stack_do_exit()
16aace664b27 x86/entry/64: Fix unwind hints in kernel exit path
07c4cd680c0b x86/entry/64: Fix unwind hints in register clearing code
d8eb5a1cde35 batman-adv: Fix refcnt leak in batadv_v_ogm_process
13f968c8b762 batman-adv: Fix refcnt leak in batadv_store_throughput_override
b71348105899 batman-adv: Fix refcnt leak in batadv_show_throughput_override
bee7e9da58ba batman-adv: fix batadv_nc_random_weight_tq
34ca080088e2 iocost: protect iocg->abs_vdebt with iocg->waitq.lock
d8c7f015d1a9 riscv: set max_pfn to the PFN of the last page
480534e03061 coredump: fix crash when umh is disabled
b8fe132bae66 staging: gasket: Check the return value of gasket_get_bar_index()
53f453031a20 ceph: demote quotarealm lookup warning to a debug message
3fd9f902c08a ceph: fix endianness bug when handling MDS session feature bits
e991f7ded4e1 mm: limit boost_watermark on small zones
4b49a9660d26 mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous()
ee922a2f6be9 eventpoll: fix missing wakeup for ovflist in ep_poll_callback
5d77631de15a epoll: atomically remove wait entry on wake up
1f3aa3e028c5 ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
65f96f4b797e drm: ingenic-drm: add MODULE_DEVICE_TABLE
0eae1647f145 arm64: hugetlb: avoid potential NULL dereference
e983c6064a0a KVM: arm64: Fix 32bit PC wrap-around
3ae9279d725a KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER
152d97d0b26f KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path
3f23f781290b KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction
eb0373fc3871 crypto: arch/nhpoly1305 - process in explicit 4k chunks
8b166a6f6286 tracing: Add a vmalloc_sync_mappings() for safe measure
72886ae16a75 USB: serial: garmin_gps: add sanity checking for data length
4f4dc27c09cd usb: chipidea: msm: Ensure proper controller reset using role switch API
2419a955172c USB: uas: add quirk for LaCie 2Big Quadra
b60a086ec733 HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT
613045bfc63d HID: usbhid: Fix race between usbhid_close() and usbhid_stop()
1017955fab5b Revert "HID: wacom: generic: read the number of expected touches on a per collection basis"
a204d577be70 sctp: Fix bundling of SHUTDOWN with COOKIE-ACK
3fc16b5b1947 HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices
0aeae7ad9450 net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del()
b2930c86ee2b net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx()
d595dd5ba909 net/mlx5: Fix command entry leak in Internal Error State
11dd1d0ebfdd net/mlx5: Fix forced completion access non initialized command entry
18cfbcdf1f41 net/mlx5: DR, On creation set CQ's arm_db member to right value
6ab4dd433b61 bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features().
cf07e0ccffde bnxt_en: Return error when allocating zero size context memory.
76737d877fab bnxt_en: Improve AER slot reset.
ab1c944361b4 bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF.
2be3a9e71ce4 bnxt_en: Fix VF anti-spoof filter setup.
a882d44e5bad tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040
e9edd5a0f5f5 tipc: fix partial topology connection closure
f2d581951775 sch_sfq: validate silly quantum values
017242e3bdb3 sch_choke: avoid potential panic in choke_reset()
66f7e30273ef nfp: abm: fix a memory leak bug
8fc441d16183 net: usb: qmi_wwan: add support for DW5816e
4107cd9a869f net/tls: Fix sk_psock refcnt leak when in tls_data_ready()
a15ccc88e516 net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict()
4124b1317f26 net: tc35815: Fix phydev supported/advertising mask
7bbf73e918be net: stricter validation of untrusted gso packets
b51b394f4ab1 net_sched: sch_skbprio: add message validation to skbprio_change()
c78c166748e9 net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc()
57f6c4340aad net: macsec: preserve ingress frame ordering
301d6eb32d81 net: macb: fix an issue about leak related system resources
5ffd49c52bad net: dsa: Do not leave DSA master with NULL netdev_ops
e781af2fdc2e neigh: send protocol value in neighbor create notification
89469cf72fae mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly
5d7e1e23efb6 ipv6: Use global sernum for dst validation with nexthop objects
45b6af95aae7 fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks
429a89625693 dp83640: reverse arguments to list_add_tail
6ee2fdf2ba4d devlink: fix return value after hitting end in region read
b586a95e2606 tty: xilinx_uartps: Fix missing id assignment to the console
8ca4302bc663 vt: fix unicode console freeing with a common interface
f4d20b01eaf6 drm/amdgpu: drop redundant cg/pg ungate on runpm enter
c973b108912a drm/amdgpu: move kfd suspend after ip_suspend_phase1
8e16ede5b7a1 net: macb: Fix runtime PM refcounting
eb6f88cd81ac tracing/kprobes: Fix a double initialization typo
56fc76893f87 nvme: fix possible hang when ns scanning fails during error recovery
fb1b41128c70 nvme: refactor nvme_identify_ns_descs error handling
a5d53ad84eb5 USB: serial: qcserial: Add DW5816e support
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index f6acb291fe..ba72377596 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "5db46f8cf9b485f320287147ce593789ee0b5447"
-SRCREV_meta ?= "4ed477131e6e508d335d70c070eb84a5c3d673e5"
+SRCREV_machine ?= "3d6fc5e71f0a3a21dacd90094f04d57a4fd59e60"
+SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
-LINUX_VERSION ?= "5.4.40"
+LINUX_VERSION ?= "5.4.42"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index f797aa1df5..1645906034 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
require recipes-kernel/linux/linux-yocto.inc
-LINUX_VERSION ?= "5.4.40"
+LINUX_VERSION ?= "5.4.42"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine_qemuarm ?= "b84f9483ed29096cd9bb6b1922666e8a275dd496"
-SRCREV_machine ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_meta ?= "4ed477131e6e508d335d70c070eb84a5c3d673e5"
+SRCREV_machine_qemuarm ?= "80606f0432a35225e7bff188a890b836018bae61"
+SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 65afdc32fa..068cebca2c 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86 ?= "v5.4/standard/base"
KBRANCH_qemux86-64 ?= "v5.4/standard/base"
KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "cbe84f8dbb7fe4a67a337795d81cca735346f4c8"
-SRCREV_machine_qemuarm64 ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_machine_qemumips ?= "b0ad6cf1238ec97860a9e26a6da1aa431c5b96fb"
-SRCREV_machine_qemuppc ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_machine_qemuriscv64 ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_machine_qemux86 ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_machine_qemux86-64 ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_machine_qemumips64 ?= "5247564ab2b897a678ed0cd8fb2905c918fc64df"
-SRCREV_machine ?= "29f44c85c379c38f15e544828e7e77b3c008f378"
-SRCREV_meta ?= "4ed477131e6e508d335d70c070eb84a5c3d673e5"
+SRCREV_machine_qemuarm ?= "a076e375d8ad4e5fdfa2de876e760868bfb56362"
+SRCREV_machine_qemuarm64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_machine_qemumips ?= "fd673ca3d8d41867ffc9869cba2fa407e7be1b2a"
+SRCREV_machine_qemuppc ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_machine_qemuriscv64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_machine_qemux86 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_machine_qemux86-64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_machine_qemumips64 ?= "2da40cf3f065512eea3729172f8e3f0cf1857160"
+SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
+SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.40"
+LINUX_VERSION ?= "5.4.42"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
DEPENDS += "openssl-native util-linux-native"
--
2.19.1
^ permalink raw reply related [flat|nested] 59+ messages in thread
* [PATCH 2/5] linux-yocto-rt/5.4: update to rt24
2020-05-29 1:29 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-29 1:29 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.42 Bruce Ashfield
@ 2020-05-29 1:29 ` Bruce Ashfield
2020-05-29 1:29 ` [PATCH 3/5] linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels Bruce Ashfield
` (2 subsequent siblings)
4 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Integrating the following commit(s) to linux-yocto-rt/5.4:
3d70f110c590 Linux 5.4.40-rt24
6445e48533d9 Linux 5.4.39-rt23
0a6ba32d4177 Linux 5.4.37-rt22
35c686fb7671 Linux 5.4.34-rt21
e54886570abd Linux 5.4.33-rt20
307ba149ec47 v5.4.28-rt19
8d488719e24a mm/compaction: Disable compact_unevictable_allowed on RT (Update)
d1d2315e077c v5.4.28-rt18
78028bc22d31 v5.4.26-rt17
815bfc775961 swait: Remove the warning with more than two waiters
b23b7f974955 powerpc: Fix lazy preemption for powerpc 32bit
a79a552889de mm/page_alloc: Use migrate_disable() in drain_local_pages_wq()
5e488daa19cb mm: Revert the DEFINE_PER_CPU_PAGEVEC implementation
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index ba72377596..760ded446a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,7 +11,7 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "3d6fc5e71f0a3a21dacd90094f04d57a4fd59e60"
+SRCREV_machine ?= "3d70f110c590b38219843a3a0815a232fd542cec"
SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
--
2.19.1
^ permalink raw reply related [flat|nested] 59+ messages in thread
* [PATCH 3/5] linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels
2020-05-29 1:29 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-29 1:29 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.42 Bruce Ashfield
2020-05-29 1:29 ` [PATCH 2/5] linux-yocto-rt/5.4: update to rt24 Bruce Ashfield
@ 2020-05-29 1:29 ` Bruce Ashfield
2020-05-29 1:29 ` [PATCH 4/5] linux-yocto: gather reproducibility configs into a fragment Bruce Ashfield
2020-05-29 1:29 ` [PATCH 5/5] linux-yocto/5.4: update to v5.4.43 Bruce Ashfield
4 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
We had a commit that enabled IKHEADERS, since bpf requires them on
target.
This is still causing incremental reproducibility errors during the
module compilation phase of the build.
We are temporarily turning this off, so we can integrate -stable
and other related changes. A replacement feature "reproducibility"
is also being added to this can be conditionally enabled while
we debug.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 760ded446a..e6366ee36d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -12,7 +12,7 @@ python () {
}
SRCREV_machine ?= "3d70f110c590b38219843a3a0815a232fd542cec"
-SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
+SRCREV_meta ?= "6d128007a79cdbecb66c5d8d186c0bbc41496526"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index 1645906034..4a37c758b2 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
SRCREV_machine_qemuarm ?= "80606f0432a35225e7bff188a890b836018bae61"
SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
+SRCREV_meta ?= "6d128007a79cdbecb66c5d8d186c0bbc41496526"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 068cebca2c..2bba72df77 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -21,7 +21,7 @@ SRCREV_machine_qemux86 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
SRCREV_machine_qemux86-64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
SRCREV_machine_qemumips64 ?= "2da40cf3f065512eea3729172f8e3f0cf1857160"
SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_meta ?= "2647d22ea8ac2d3af6fe3b0d635cf84ee06f95e3"
+SRCREV_meta ?= "6d128007a79cdbecb66c5d8d186c0bbc41496526"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
--
2.19.1
^ permalink raw reply related [flat|nested] 59+ messages in thread
* [PATCH 4/5] linux-yocto: gather reproducibility configs into a fragment
2020-05-29 1:29 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (2 preceding siblings ...)
2020-05-29 1:29 ` [PATCH 3/5] linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels Bruce Ashfield
@ 2020-05-29 1:29 ` Bruce Ashfield
2020-05-29 1:29 ` [PATCH 5/5] linux-yocto/5.4: update to v5.4.43 Bruce Ashfield
4 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating the meta SRCREV to pickup the following fix:
commit 9e68afb48b16a447dcd3996ffa350f3e79e44257 (HEAD -> master)
Author: Bruce Ashfield <bruce.ashfield@gmail.com>
Date: Thu May 28 11:22:22 2020 -0400
features: add reproducibility fragement
Creating an initial feature fragment that can be included when a
reproducible kernel build is desired. This is currently only one
option, but will have more in the future.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index e6366ee36d..a78d333e31 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -12,7 +12,7 @@ python () {
}
SRCREV_machine ?= "3d70f110c590b38219843a3a0815a232fd542cec"
-SRCREV_meta ?= "6d128007a79cdbecb66c5d8d186c0bbc41496526"
+SRCREV_meta ?= "d62979d9e2d30640c777438bebb40d98e03c331a"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index 4a37c758b2..db2e82efe4 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
SRCREV_machine_qemuarm ?= "80606f0432a35225e7bff188a890b836018bae61"
SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_meta ?= "6d128007a79cdbecb66c5d8d186c0bbc41496526"
+SRCREV_meta ?= "d62979d9e2d30640c777438bebb40d98e03c331a"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 2bba72df77..6c991558ce 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -21,7 +21,7 @@ SRCREV_machine_qemux86 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
SRCREV_machine_qemux86-64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
SRCREV_machine_qemumips64 ?= "2da40cf3f065512eea3729172f8e3f0cf1857160"
SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_meta ?= "6d128007a79cdbecb66c5d8d186c0bbc41496526"
+SRCREV_meta ?= "d62979d9e2d30640c777438bebb40d98e03c331a"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
--
2.19.1
^ permalink raw reply related [flat|nested] 59+ messages in thread
* [PATCH 5/5] linux-yocto/5.4: update to v5.4.43
2020-05-29 1:29 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (3 preceding siblings ...)
2020-05-29 1:29 ` [PATCH 4/5] linux-yocto: gather reproducibility configs into a fragment Bruce Ashfield
@ 2020-05-29 1:29 ` Bruce Ashfield
4 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
e0d81ce76004 Linux 5.4.43
b5100186021a sched/fair: Fix enqueue_task_fair() warning some more
8b13f5657fa8 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
a2ad232aa6a9 sched/fair: Reorder enqueue/dequeue_task_fair path
f4520daa3c5a tpm: check event log version before reading final events
68b7b8183c12 rxrpc: Fix ack discard
283eb0016f97 rxrpc: Trace discarded ACKs
f2da8c0dfe81 iio: adc: stm32-dfsdm: fix device used to request dma
7b5af65ca246 iio: adc: stm32-dfsdm: Use dma_request_chan() instead dma_request_slave_channel()
692001a867b6 iio: adc: stm32-adc: fix device used to request dma
8e8836b2b782 iio: adc: stm32-adc: Use dma_request_chan() instead dma_request_slave_channel()
1084eee4dc5d x86/unwind/orc: Fix unwind_get_return_address_ptr() for inactive tasks
860fe59783a9 flow_dissector: Drop BPF flow dissector prog ref on netns cleanup
bd6f0c799f4d s390/kexec_file: fix initrd location for kdump kernel
834d24ec3a0a rxrpc: Fix a memory leak in rxkad_verify_response()
23ae6e3e8aeb rxrpc: Fix the excessive initial retransmission timeout
c2a26769b43e kasan: disable branch tracing for core runtime
86217fecc4b7 rapidio: fix an error in get_user_pages_fast() error handling
689dacb2b09d device-dax: don't leak kernel memory to user space after unloading kmem
9e451933bba9 s390/kaslr: add support for R_390_JMP_SLOT relocation type
72f3241508ac s390/pci: Fix s390_mmio_read/write with MIO
9c84884cd5dc ipack: tpci200: fix error return code in tpci200_register()
46f47dda27bc mei: release me_cl object reference
f505a3e24c6a tty: serial: add missing spin_lock_init for SiFive serial console
a5b4b3f97de7 misc: rtsx: Add short delay after exit from ASPM
e64b205035fb iio: adc: ti-ads8344: Fix channel selection
9af65dc54b9b iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()'
d54e5a4ff04c iio: sca3000: Remove an erroneous 'get_device()'
56cff2ac7c9d staging: greybus: Fix uninitialized scalar variable
a41e02cb4232 staging: kpc2000: fix error return code in kp2000_pcie_probe()
dee81110a488 staging: iio: ad2s1210: Fix SPI reading
76296dc723ef media: fdp1: Fix R-Car M3-N naming in debug message
4adb7a2b3161 Revert "gfs2: Don't demote a glock until its revokes are written"
bb6524537dc2 kbuild: Remove debug info from kallsyms linking
ee71c590dd8d bpf: Avoid setting bpf insns pages read-only when prog is jited
4c732e81bd4d powerpc/64s: Disable STRICT_KERNEL_RWX
b67da9dbdb89 powerpc: Remove STRICT_KERNEL_RWX incompatibility with RELOCATABLE
9bcfbd8ba2b5 drm/i915: Propagate error from completed fences
5e171483e947 drm/i915/gvt: Init DPLL/DDI vreg for virtual display instead of inheritance.
0e1d5f67253e vsprintf: don't obfuscate NULL and error pointers
4b1b34621998 dmaengine: owl: Use correct lock in owl_dma_get_pchan()
0fcbe108b01a dmaengine: dmatest: Restore default for channel
57c32a52c3fe drm/etnaviv: Fix a leak in submit_pin_objects()
432b103596bd dmaengine: tegra210-adma: Fix an error handling path in 'tegra_adma_probe()'
870a45e0b507 apparmor: Fix aa_label refcnt leak in policy_update
054934aa9faa apparmor: fix potential label refcnt leak in aa_change_profile
97d817b9ef13 apparmor: Fix use-after-free in aa_audit_rule_init
3b1e38dfbc9f drm/etnaviv: fix perfmon domain interation
53683907ef68 arm64: Fix PTRACE_SYSEMU semantics
96e56055a2f0 scsi: target: Put lun_ref at end of tmr processing
818657105a0b scsi: qla2xxx: Do not log message when reading port speed via sysfs
d54c5eff8795 ALSA: hda/realtek - Add more fixup entries for Clevo machines
80f5822c2bf3 ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme
1b17a0f98ad0 ALSA: pcm: fix incorrect hw_base increase
a44cb2581718 ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option
99e392a4979b KVM: x86: Fix pkru save/restore when guest CR4.PKE=0, move it to x86.c
1c3d707d7d12 ALSA: hda/realtek: Enable headset mic of ASUS UX581LV with ALC295
26a3a3053332 ALSA: hda/realtek - Enable headset mic of ASUS UX550GE with ALC295
c5742497dcd2 ALSA: hda/realtek - Enable headset mic of ASUS GL503VM with ALC295
2523e9010d2b ALSA: hda/realtek: Add quirk for Samsung Notebook
6cc4dd44e207 ALSA: hda/realtek - Add HP new mute led supported for ALC236
0d189b31c4d7 ALSA: hda/realtek - Add supported new mute Led for HP
69d5dc286d05 ALSA: hda: Manage concurrent reg access more properly
1efaaf74528c ALSA: hda: patch_realtek: fix empty macro usage in if block
749e58bd2b09 ALSA: hda - constify and cleanup static NodeID tables
02ebbd1da394 scripts/gdb: repair rb_first() and rb_last()
9eff404a4382 ARM: futex: Address build warning
67a5c3104d12 KVM: selftests: Fix build for evmcs.h
4f48af814798 drm/amd/display: Prevent dpcd reads with passive dongles
e0bb3075f91b iommu/amd: Call domain_flush_complete() in update_domain()
e1efb9893bdd platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA
c8d323578e36 USB: core: Fix misleading driver bug report
42b32a43529e stmmac: fix pointer check after utilization in stmmac_interrupt
b68d27c5fffd ceph: fix double unlock in handle_cap_export()
df0df8ee2ac7 HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock
8a5de4a391e4 gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp()
7932168ec08e x86/apic: Move TSC deadline timer debug printk
1ae9f1a62a50 ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set
2eac9d3dc23f ibmvnic: Skip fatal error reset after passive init
f82a3013226e x86/mm/cpa: Flush direct map alias during cpa
632db044ab99 HID: i2c-hid: reset Synaptics SYNA2393 on resume
acd3efa17d96 scsi: ibmvscsi: Fix WARN_ON during event pool release
6ef21295dc20 net/ena: Fix build warning in ena_xdp_set()
d0db69f9d132 component: Silence bind error on -EPROBE_DEFER
7a5f60dc3a67 aquantia: Fix the media type of AQC100 ethernet controller in the driver
445437b417b6 vhost/vsock: fix packet delivery order to monitoring devices
dcec6678c3b1 configfs: fix config_item refcnt leak in configfs_rmdir()
2b52a61adb38 scsi: qla2xxx: Delete all sessions before unregister local nvme port
d2430cb7f2d4 scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV
7b481b802a8f HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead
a08626f6e982 HID: alps: Add AUI1657 device ID
68988c00b153 HID: multitouch: add eGalaxTouch P80H84 support
cc6428803d22 gcc-common.h: Update for GCC 10
3c140d22e3c2 net: drop_monitor: use IS_REACHABLE() to guard net_dm_hw_report()
87863a7426b2 kbuild: avoid concurrency issue in parallel building dtbs and dtbs_check
44fd02a3d719 mtd: Fix mtd not registered due to nvmem name collision
496c7c61bd64 afs: Don't unlock fetched data pages until the op completes successfully
17c9595cca71 ubi: Fix seq_file usage in detailed_erase_block_info debugfs file
274cd3c7b5d3 i2c: mux: demux-pinctrl: Fix an error handling path in 'i2c_demux_pinctrl_probe()'
dd540f2d7c2d evm: Fix a small race in init_desc()
f96ab0d1f3ec iommu/amd: Fix over-read of ACPI UID from IVRS table
33769c19feba i2c: fix missing pm_runtime_put_sync in i2c_device_probe
9f885f17501d ubifs: remove broken lazytime support
ac6f94d3be65 fix multiplication overflow in copy_fdtable()
725b0bb0f94d mtd: spinand: Propagate ECC information to the MTD structure
e3637eb6a351 ACPI: EC: PM: Avoid flushing EC work when EC GPE is inactive
3be8ece11440 ubifs: fix wrong use of crypto_shash_descsize()
48bbd44f5fa9 ima: Fix return value of ima_write_policy()
1066327bf936 evm: Check also if *tfm is an error pointer in init_desc()
4aedc534b608 ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash()
ac46cea606d5 KVM: SVM: Fix potential memory leak in svm_cpu_init()
1bed86cfe5cb i2c: dev: Fix the race between the release of i2c_dev and cdev
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index a78d333e31..a9213c2439 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "3d70f110c590b38219843a3a0815a232fd542cec"
-SRCREV_meta ?= "d62979d9e2d30640c777438bebb40d98e03c331a"
+SRCREV_machine ?= "1afad41c91e13f957bbe61fa7fdc05a77e84d489"
+SRCREV_meta ?= "aafb8f095e97013d6e55b09ed150369cbe0c6476"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
-LINUX_VERSION ?= "5.4.42"
+LINUX_VERSION ?= "5.4.43"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index db2e82efe4..aab53bed6a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
require recipes-kernel/linux/linux-yocto.inc
-LINUX_VERSION ?= "5.4.42"
+LINUX_VERSION ?= "5.4.43"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine_qemuarm ?= "80606f0432a35225e7bff188a890b836018bae61"
-SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_meta ?= "d62979d9e2d30640c777438bebb40d98e03c331a"
+SRCREV_machine_qemuarm ?= "c3864bf2906c5075305bf675c27788505ea93047"
+SRCREV_machine ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_meta ?= "aafb8f095e97013d6e55b09ed150369cbe0c6476"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 6c991558ce..01795e6166 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86 ?= "v5.4/standard/base"
KBRANCH_qemux86-64 ?= "v5.4/standard/base"
KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "a076e375d8ad4e5fdfa2de876e760868bfb56362"
-SRCREV_machine_qemuarm64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_machine_qemumips ?= "fd673ca3d8d41867ffc9869cba2fa407e7be1b2a"
-SRCREV_machine_qemuppc ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_machine_qemuriscv64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_machine_qemux86 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_machine_qemux86-64 ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_machine_qemumips64 ?= "2da40cf3f065512eea3729172f8e3f0cf1857160"
-SRCREV_machine ?= "1ef0d05b4662a4e5a075db47e7e368e9a12c4877"
-SRCREV_meta ?= "d62979d9e2d30640c777438bebb40d98e03c331a"
+SRCREV_machine_qemuarm ?= "6c628db39bf48f7dd6cd95ae826bcaa18a56df1d"
+SRCREV_machine_qemuarm64 ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_machine_qemumips ?= "c0cd2937ae195344ece04663b30b2049427b3c57"
+SRCREV_machine_qemuppc ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_machine_qemuriscv64 ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_machine_qemux86 ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_machine_qemux86-64 ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_machine_qemumips64 ?= "6254ff1d776b75bc3d9c2c66c083fbc622091cd4"
+SRCREV_machine ?= "9e1b13d7f9d84f691fb9988c5f53c5ab62b8a5e9"
+SRCREV_meta ?= "aafb8f095e97013d6e55b09ed150369cbe0c6476"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.42"
+LINUX_VERSION ?= "5.4.43"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
DEPENDS += "openssl-native util-linux-native"
--
2.19.1
^ permalink raw reply related [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2023-02-01 16:28 bruce.ashfield
0 siblings, 0 replies; 59+ messages in thread
From: bruce.ashfield @ 2023-02-01 16:28 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the latest round of configuration and -stable udpates that
I've collected.
Nothing major, but hopefully the virtio patches will help some of
the AB issues.
Bruce
The following changes since commit da95831d91b1265ecaee5bbfaeb1caaa2c290838:
scons: Pass MAXLINELENGTH to scons invocation (2023-01-31 17:11:07 +0000)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/6.1: update to v6.1.7
linux-yocto/5.15: update to v5.15.89
linux-yocto/6.1: cfg: remove depreciated configs
linux-yocto/6.1: update to v6.1.9
linux-yocto/5.15: update to v5.15.91
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-rt_6.1.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_6.1.bb | 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 26 +++++++++----------
6 files changed, 38 insertions(+), 38 deletions(-)
--
2.34.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-11-19 19:17 Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-11-19 19:17 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's my next set of collected changes for linux-yocto. I built and booted the
5.4 -stable bump .. and obviously it looks good.
I've also grabbed a pending devsrc change, that looks good to me.
Finally, I have a fix Khem sent for perf builds. I kept 5.4 and 5.8 separate
for that fix, so Steve can pick them up for Dunfell as appropriate.
Bruce
The following changes since commit d8f47a68a92802fc47f297de05a0f2817963a7ee:
kernel: relocate copy of module.lds to module compilation task (2020-11-18 13:59:27 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (4):
linux-yocto/5.4: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
arches with 64bit time_t
linux-yocto/5.8: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
arches with 64bit time_t
linux-yocto/5.8: ext4/tipc warning fixups
linux-yocto/5.4: update to v5.4.78
INC@Cisco) (1):
kernel-devsrc: improve reproducibility for arm64
meta/recipes-kernel/linux/kernel-devsrc.bb | 4 ++++
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-rt_5.8.bb | 2 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
.../linux/linux-yocto-tiny_5.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.8.bb | 18 +++++++--------
7 files changed, 34 insertions(+), 30 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-04 8:30 ` Richard Purdie
@ 2020-05-04 12:56 ` Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-04 12:56 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer, steve
On Mon, May 4, 2020 at 4:31 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > Here are the -stable updates I've collected since m3 of dunfell. I
> > ran things through the autobuilder, and no new kernel issues were
> > picked up.
> >
> > The -dev bump is good for master, while all of the 5.4-stable bumps
> > are good for both master and dunfell.
>
> I pulled these into master-next and saw reproducibility issues. I
> wondered why your test build didn't show it, turns out it also did:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
>
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
>
> AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
>
I don't see any changes in the kernels that would have triggered it,
but they never are obvious.
I unfortunately have no idea how to run reproducibility tests on the
kernels locally and my build server at home is brutally underpowered
for more than one core-image build per arch a day (hence the
autobuilder runs).
Is there a cut and paste se of instructions about the tests that I
could follow ?
Bruce
> master-next was:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
>
> and friends.
>
> Cheers,
>
> Richard
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-03 15:44 Bruce Ashfield
@ 2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Richard Purdie @ 2020-05-04 8:30 UTC (permalink / raw)
To: bruce.ashfield; +Cc: openembedded-core, steve
Hi Bruce,
On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Hi all,
>
> Here are the -stable updates I've collected since m3 of dunfell. I
> ran things through the autobuilder, and no new kernel issues were
> picked up.
>
> The -dev bump is good for master, while all of the 5.4-stable bumps
> are good for both master and dunfell.
I pulled these into master-next and saw reproducibility issues. I
wondered why your test build didn't show it, turns out it also did:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
master-next was:
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
and friends.
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-05-03 15:44 Bruce Ashfield
2020-05-04 8:30 ` Richard Purdie
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here are the -stable updates I've collected since m3 of dunfell. I ran
things through the autobuilder, and no new kernel issues were picked up.
The -dev bump is good for master, while all of the 5.4-stable bumps are
good for both master and dunfell.
Cheers,
Bruce
The following changes since commit 2e11d97b6c95e89aa1f9d3603a966c94c442469e:
oeqa/qemurunner: Clean up failure handling (2020-04-26 14:00:51 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.28
linux-yocto/5.4: update to v5.4.32
linux-yocto/5.4: update to v5.4.34
linux-yocto/5.4: update to v5.4.38
linux-yocto-dev: bump to v5.7-rc
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
4 files changed, 19 insertions(+), 19 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-03-24 23:04 Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2020-03-24 23:04 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here's the queued bug fixes for linux-yocto. It has khem's identified fixes
for the kernel selftest issues with the latest -stable udpates, as well as
some BSP fixes and config changes.
I ran this through the AB and everything came back green.
I've done this in multiple commits, so we'll have granularity to look
into individual fixes if we have trouble.
Cheers,
Bruce
The following changes since commit d5db9d12642e03a1d5cca5f1520dad5fcc9524c3:
archiver.py: fix typo of "ARCHIVER_MIRROR_EXCLUDE" in comment (2020-03-24 16:39:40 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: Revert "platform/x86: wmi: Destroy on cleanup rather
than unregister"
linux-yocto/5.4: fix kernel selftests
linux-yocto/5.4: KVM: LAPIC: Mark hrtimer for period or oneshot mode
to expire in hard interrupt context
linux-yocto/5.4: ARM: 8918/2: only build return_address() if needed
linux-yocto/5.4: configuration tweaks
.../linux/linux-yocto-rt_5.4.bb | 4 ++--
.../linux/linux-yocto-tiny_5.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 20 +++++++++----------
3 files changed, 15 insertions(+), 15 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-07-27 16:57 Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2016-07-27 16:57 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here's the latest batch of linux-yocto (4.1 and 4.4) changes. They are
-stable updates, a memory leak fix and configuration tweaks (in particular
the removal of debug kernel from the printk fragment).
This is a slight overlap with another series that I sent before, since I
noticed some mistakes in the 4.1 and 4.4-stable update commits .. so I
rephrased them.
Cheers,
Bruce
The following changes since commit 039f47ad197a9a53109c9f3deadd9c35e62c056d:
uclibc: remove meta-yocto-bsp append (2016-07-26 08:56:32 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.4: bump to v4.4.15
linux-yocto/4.1: bump to v4.1.28
linux-yocto/4.1: bug fixes and configuration changes
linux-yocto/4.4: lx-dialog and mei bug fixes
linux-yocto/4.4: mousedev and printk configuation streamlining
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 20 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++++++++++----------
6 files changed, 31 insertions(+), 31 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-06-21 15:20 Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2016-06-21 15:20 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here's the latest set of changes to the 4.1 and 4.4 linux-yocto
kernel's. Nothing particularly exciting, mainline backports and
minor fixups.
Cheers,
Bruce
The following changes since commit 84cce1d49ddb75025ec454d758fbc8d369920122:
e2fsprogs: remove the extra dot from the recipe filename (2016-06-21 13:00:17 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.1: tpm2, pinctrl, powercap and watchdog backports
linux-yocto/4.1: SPI, MFD, alsa and perf backports
linux-yocto/4.1: driver, mmc and power backports
linux-yocto/4.1: pstate backports
linux-yocto/4.4: sensor driver backports
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 16 ++++++++--------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 16 ++++++++--------
5 files changed, 19 insertions(+), 19 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-04-13 16:12 Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2016-04-13 16:12 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
This series contains some changes that I've been gathering over the past
week. Nothing serious, just BSP mainline backports, configuration tweaks
to tiny (for usability) and a change to make aufs4 opt-in (versus always
on).
I've built and booted this for qemu* (standard and -rt).
Cheers,
Bruce
The following changes since commit e912c468875ffea7e8070cb7813bca262d1cbb0b:
kbd: remove uclibc-stdarg.patch (2016-04-13 10:12:53 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.4: gpio-pca953x: fix the "drive" property cannot
read/write
linux-yocto/4.1: mainline SPI backports
linux-yocto/4.4: BXT enablement
linux-yocto: tiny and pin ctrl config updates
linux-yocto: make aufs4 optional
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 18 +++++++++---------
6 files changed, 26 insertions(+), 26 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 22:49 ` Martin Jansa
@ 2015-05-07 15:33 ` Bruce Ashfield
0 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-07 15:33 UTC (permalink / raw)
To: Martin Jansa, Richard Purdie
Cc: Patches and discussions about the oe-core layer
On 2015-05-06 06:49 PM, Martin Jansa wrote:
> I use tmpfs in most of my builds, so in most cases when I see the error
> from the build, tmpfs is already gone (purged by next build executed on
> the same sever).
ross just found something like this in one of his local builds .. I'm
pretty sure I see the race.
Fix coming shortly, and then the bigger changes I was mentioning before
as well.
Cheers,
Bruce
>
> On Wed, May 6, 2015 at 11:32 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org
> <mailto:richard.purdie@linuxfoundation.org>> wrote:
>
> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
@ 2015-05-07 6:33 ` Khem Raj
1 sibling, 0 replies; 59+ messages in thread
From: Khem Raj @ 2015-05-07 6:33 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
> On May 6, 2015, at 8:33 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
just for build sake to avoid full kernel builds, having a dummy kernel recipe should be another alternative
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 21:32 ` Richard Purdie
@ 2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Martin Jansa @ 2015-05-06 22:49 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
I use tmpfs in most of my builds, so in most cases when I see the error
from the build, tmpfs is already gone (purged by next build executed on the
same sever).
On Wed, May 6, 2015 at 11:32 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and
> python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>
[-- Attachment #2: Type: text/html, Size: 2142 bytes --]
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 17:46 ` Bruce Ashfield
@ 2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
0 siblings, 1 reply; 59+ messages in thread
From: Richard Purdie @ 2015-05-06 21:32 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > I've used master-next week or two ago (mostly to test bluez4 and python3
> > changes) and soon after that dropped all linux-yocto related changes
> > from it assuming that it's indeed cause for the issues I'm seeing, but
> > it's not and it's still failing with master as well (and my
> > jenkins/world builds are just small portion of my builds executed
> > elsewhere where I see similar issues).
>
> Richard: How can we sort out the differences between the build
> environment that Martin uses versus what the autobuilder is showing?
>
> There's nothing particularly complex happening during that build,
> it's a checkout and generation of a config.
>
> I'm unable to reproduce any of the failures, and neither is the
> autobuilder.
This is a tough one and I'm struggling a little. We could try looking at
the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
particular) as well as
tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
Martin, would you be able to share the above somewhere? I'm hoping this
would give us a clue as to what the difference is between the builds and
allow us to reproduce the problem.
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 16:07 ` Martin Jansa
@ 2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-06 17:46 UTC (permalink / raw)
To: Martin Jansa, Richard Purdie; +Cc: openembedded-core
On 2015-05-06 12:07 PM, Martin Jansa wrote:
> On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
>> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
>>> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-06 10:42 AM, Martin Jansa wrote:
>>>> At this point, all I can say is file a bug. My builds of the same
>>>> board work, and the autobuilder show up green.
>>>>
>>>> That screams race condition, so I'll look into it from that angle.
>>>
>>> I'm considering providing simple old-style recipes for vanilla kernels
>>> and using them in my jenkins builds instead linux-yocto, because kernel
>>> shouldn't block testing other recipes from meta-oe and other layers as
>>> often as linux-yocto does.
>>
>> I wasn't aware of linux-yocto breaking that often?
>
> Someone can query http://errors.yoctoproject.org/ database to see how
> often (or if it's just me and my builds), unfortunately the full-text
> search for "linux-yocto" doesn't provide good overview of issues,
> because it shows 350 errors and not all are from linux-yocto recipe.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
> on e-mail also aren't very accurate because I submit only reports from
> relatively success full builds (so I usually skip the builds with failed
> kernel, unless it's failing like that for long time).
>
>> I am aware that:
>>
>> * we have a race issue with shared_work which we're trying to resolve
>> and its proving tricky to find a patch which doesn't break builds
>>
>> * we have the newly reported issue in this thread. FWIW the builders
>> I've seen are all green
>>
>> * there are some warnings in the build which need addressing
>>
>> but on the most part I thought we'd caught the serious kernel failures
>> in advance of changes hitting master. Are you using master-next or
>> master?
>
> I've used master-next week or two ago (mostly to test bluez4 and python3
> changes) and soon after that dropped all linux-yocto related changes
> from it assuming that it's indeed cause for the issues I'm seeing, but
> it's not and it's still failing with master as well (and my
> jenkins/world builds are just small portion of my builds executed
> elsewhere where I see similar issues).
Richard: How can we sort out the differences between the build
environment that Martin uses versus what the autobuilder is showing?
There's nothing particularly complex happening during that build,
it's a checkout and generation of a config.
I'm unable to reproduce any of the failures, and neither is the
autobuilder.
I've stared at the code and can't see what could cause any of this.
That being said, I think I have a solution to what Martin is reporting
here, where I've changed the way the meta data is maintained and
build.
It will be ready in a week or so, so I'd be interested in us holding
on anything drastic until we can try that out.
Bruce
>
>> Its its -next, I can understand the problems more as that has been
>> unstable recently but then by its nature, it can be. We are rooting out
>> problems before master afaict though?
>>
>> Cheers,
>>
>> Richard
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:44 ` Richard Purdie
@ 2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Martin Jansa @ 2015-05-06 16:07 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> > On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > > At this point, all I can say is file a bug. My builds of the same
> > > board work, and the autobuilder show up green.
> > >
> > > That screams race condition, so I'll look into it from that angle.
> >
> > I'm considering providing simple old-style recipes for vanilla kernels
> > and using them in my jenkins builds instead linux-yocto, because kernel
> > shouldn't block testing other recipes from meta-oe and other layers as
> > often as linux-yocto does.
>
> I wasn't aware of linux-yocto breaking that often?
Someone can query http://errors.yoctoproject.org/ database to see how
often (or if it's just me and my builds), unfortunately the full-text
search for "linux-yocto" doesn't provide good overview of issues,
because it shows 350 errors and not all are from linux-yocto recipe.
http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
on e-mail also aren't very accurate because I submit only reports from
relatively success full builds (so I usually skip the builds with failed
kernel, unless it's failing like that for long time).
> I am aware that:
>
> * we have a race issue with shared_work which we're trying to resolve
> and its proving tricky to find a patch which doesn't break builds
>
> * we have the newly reported issue in this thread. FWIW the builders
> I've seen are all green
>
> * there are some warnings in the build which need addressing
>
> but on the most part I thought we'd caught the serious kernel failures
> in advance of changes hitting master. Are you using master-next or
> master?
I've used master-next week or two ago (mostly to test bluez4 and python3
changes) and soon after that dropped all linux-yocto related changes
from it assuming that it's indeed cause for the issues I'm seeing, but
it's not and it's still failing with master as well (and my
jenkins/world builds are just small portion of my builds executed
elsewhere where I see similar issues).
> Its its -next, I can understand the problems more as that has been
> unstable recently but then by its nature, it can be. We are rooting out
> problems before master afaict though?
>
> Cheers,
>
> Richard
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:33 ` Martin Jansa
@ 2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-07 6:33 ` Khem Raj
1 sibling, 1 reply; 59+ messages in thread
From: Richard Purdie @ 2015-05-06 15:44 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > At this point, all I can say is file a bug. My builds of the same
> > board work, and the autobuilder show up green.
> >
> > That screams race condition, so I'll look into it from that angle.
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
I wasn't aware of linux-yocto breaking that often?
I am aware that:
* we have a race issue with shared_work which we're trying to resolve
and its proving tricky to find a patch which doesn't break builds
* we have the newly reported issue in this thread. FWIW the builders
I've seen are all green
* there are some warnings in the build which need addressing
but on the most part I thought we'd caught the serious kernel failures
in advance of changes hitting master. Are you using master-next or
master?
Its its -next, I can understand the problems more as that has been
unstable recently but then by its nature, it can be. We are rooting out
problems before master afaict though?
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 14:58 ` Bruce Ashfield
@ 2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-07 6:33 ` Khem Raj
0 siblings, 2 replies; 59+ messages in thread
From: Martin Jansa @ 2015-05-06 15:33 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> >>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>>>> kernels.
> >>>>>>
> >>>>>> - We have a refresh of the 3.14-rt support
> >>>>>> - bluetooh configuration changes for common-pc/qemux86
> >>>>>> - braswell BSP features and fixes
> >>>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>>> I've built and booted these on my local machines and qemu, and
> >>>>>> everything was sane.
> >>>
> >>> Does it fix the issue I've reported few days ago?
> >>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >>
> >> Nope. But one config warning is far down on the list when I'm
> >> trying to introduce new -stable's and an entire -dev kernel.
> >>
> >> I didn't forget about it, it'll just get done in priority order.
> >
> > OK, now it fails completely in default qemux86 builds:
> >
>
> At this point, all I can say is file a bug. My builds of the same
> board work, and the autobuilder show up green.
>
> That screams race condition, so I'll look into it from that angle.
I'm considering providing simple old-style recipes for vanilla kernels
and using them in my jenkins builds instead linux-yocto, because kernel
shouldn't block testing other recipes from meta-oe and other layers as
often as linux-yocto does.
> > ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_configme
> > | NOTE: kernel configme
> > | [INFO] Configuring target/machine combo: "standard/qemux86"
> > | [INFO] collecting configs in .meta/meta-series
> > | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> > | Error running the meta series for collecting config data
> > | config of "standard/qemux86" failed
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> > ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
> >
> > http://errors.yoctoproject.org/Errors/Details/10481/
> >
> >>>>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>>>> it builds, and forms the base for follow up config changes, features
> >>>>>> and development work. I built and booted core-image-kernel dev with
> >>>>>> the 4.1 changes in place.
> >>>>>
> >>>>> The autobuilder showed up this for an x32 build :/.
> >>>>
> >>>> Can one of the intel folks have a look at this ? I won't be able to get
> >>>> to it until Tuesday at the earliest.
> >>>>
> >>>> Bruce
> >>>>
> >>>>>
> >>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Richard
> >>>>>
> >>>>
> >>>> --
> >>>> _______________________________________________
> >>>> Openembedded-core mailing list
> >>>> Openembedded-core@lists.openembedded.org
> >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >>>
> >>
> >
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 14:42 ` Martin Jansa
@ 2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-06 14:58 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On 2015-05-06 10:42 AM, Martin Jansa wrote:
> On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
>> On 2015-05-02 4:13 AM, Martin Jansa wrote:
>>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>>>> kernels.
>>>>>>
>>>>>> - We have a refresh of the 3.14-rt support
>>>>>> - bluetooh configuration changes for common-pc/qemux86
>>>>>> - braswell BSP features and fixes
>>>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>>> I've built and booted these on my local machines and qemu, and
>>>>>> everything was sane.
>>>
>>> Does it fix the issue I've reported few days ago?
>>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>>
>> Nope. But one config warning is far down on the list when I'm
>> trying to introduce new -stable's and an entire -dev kernel.
>>
>> I didn't forget about it, it'll just get done in priority order.
>
> OK, now it fails completely in default qemux86 builds:
>
At this point, all I can say is file a bug. My builds of the same
board work, and the autobuilder show up green.
That screams race condition, so I'll look into it from that angle.
Bruce
> ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> Log data follows:
> | DEBUG: Executing shell function do_kernel_configme
> | NOTE: kernel configme
> | [INFO] Configuring target/machine combo: "standard/qemux86"
> | [INFO] collecting configs in .meta/meta-series
> | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> | Error running the meta series for collecting config data
> | config of "standard/qemux86" failed
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
>
> http://errors.yoctoproject.org/Errors/Details/10481/
>
>>>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>>>> it builds, and forms the base for follow up config changes, features
>>>>>> and development work. I built and booted core-image-kernel dev with
>>>>>> the 4.1 changes in place.
>>>>>
>>>>> The autobuilder showed up this for an x32 build :/.
>>>>
>>>> Can one of the intel folks have a look at this ? I won't be able to get
>>>> to it until Tuesday at the earliest.
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 2:50 ` Bruce Ashfield
@ 2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Martin Jansa @ 2015-05-06 14:42 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> > On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>> - We have a refresh of the 3.14-rt support
> >>>> - bluetooh configuration changes for common-pc/qemux86
> >>>> - braswell BSP features and fixes
> >>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >
> > Does it fix the issue I've reported few days ago?
> > http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>
> Nope. But one config warning is far down on the list when I'm
> trying to introduce new -stable's and an entire -dev kernel.
>
> I didn't forget about it, it'll just get done in priority order.
OK, now it fails completely in default qemux86 builds:
ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| NOTE: kernel configme
| [INFO] Configuring target/machine combo: "standard/qemux86"
| [INFO] collecting configs in .meta/meta-series
| [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
| Error running the meta series for collecting config data
| config of "standard/qemux86" failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
http://errors.yoctoproject.org/Errors/Details/10481/
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >>
> >> Bruce
> >>
> >>>
> >>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>
> >>> Cheers,
> >>>
> >>> Richard
> >>>
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
@ 2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-04 15:01 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-03 05:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
> I've mixed the versions up, let me know which one poky-lsb should be
FYI: I've fixed the mips build. Looking at x86 now. SRCREV updates
to follow ASAP.
Bruce
> using.
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 21:30 ` Richard Purdie
@ 2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-04 4:36 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-03 5:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
Correct on all counts. We did want it to use LTSI, and that is 3.14
at the moment.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
Doesn't look to bad. I'll address this one along with the x32 build
failure on Monday (assuming I get it fixed in the day).
Bruce
> I've mixed the versions up, let me know which one poky-lsb should be
> using.
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
@ 2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 2 replies; 59+ messages in thread
From: Richard Purdie @ 2015-05-03 21:30 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
>
> - We have a refresh of the 3.14-rt support
> - bluetooh configuration changes for common-pc/qemux86
> - braswell BSP features and fixes
> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>
> I've built and booted these on my local machines and qemu, and
> everything was sane.
>
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.
There was also a problem with poky-lsb. The idea (as far as I remember)
is that it should be using LTSI rather than the default main kernel so
we could split the testing. Unfortunately it was pointing at 3.10 which
doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
updated the PREFERRED_VERSION to that.
This resulted in this failure on the autobuilder:
https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
I've mixed the versions up, let me know which one poky-lsb should be
using.
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 3:52 ` Bruce Ashfield
@ 2015-05-03 10:48 ` Richard Purdie
0 siblings, 0 replies; 59+ messages in thread
From: Richard Purdie @ 2015-05-03 10:48 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Sat, 2015-05-02 at 23:52 -0400, Bruce Ashfield wrote:
> On 2015-05-02 5:00 AM, Richard Purdie wrote:
> > On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>> - We have a refresh of the 3.14-rt support
> >>>> - bluetooh configuration changes for common-pc/qemux86
> >>>> - braswell BSP features and fixes
> >>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >>>>
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >
> > I had a look into this. The issue is that this has been applied:
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
> >
> > but it needs:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
> >
> > and the ioapic driver also appears to need:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
> >
> >
> > which meant I also had to add:
> >
> > struct resource_win {
> > struct resource res; /* In master (CPU) address space */
> > resource_size_t offset; /* Translation offset for bridge */
> > };
> >
> > to drivers/acpi/ioapic.c to make it compile which appears to be related to:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
> >
> > which depends on a number of patches from around that time which change acpi/resource.c:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
> >
> > (from 2015/2/3)
> >
> > At this point I'm out my depth on how you want to fix this but it does
> > appear related to the Braswell changes.
> >
> > To be clear qemux86 and qemux86-64 don't build at all with this series.
> > I'll see if I can just drop the Braswell parts.
>
> I did reproduce the issue here as well, so with any luck, I can sneak
> enough time to have this fixed for Monday after all.
From my perspective there isn't a rush at this point. I've merged the
config changes which unblocked the bluez patches and things are
therefore "flowing" from my perspective, the stable update can wait
until later in the week.
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
@ 2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
1 sibling, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-03 3:52 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> struct resource res; /* In master (CPU) address space */
> resource_size_t offset; /* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.
I did reproduce the issue here as well, so with any luck, I can sneak
enough time to have this fixed for Monday after all.
Bruce
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 9:00 ` Richard Purdie
@ 2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
1 sibling, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-03 2:53 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> struct resource res; /* In master (CPU) address space */
> resource_size_t offset; /* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.
Gah. It figures. That's of course the issue with any set of BSP ports ..
they get tangled up with Greg's series from time to time.
The changes are all additive, so we can't really drop the braswell parts
unless I revert the whole block of changes.
Drop those -stable updates for now, and I'll see if I can carve out some
time tomorrow to get that config building.
Bruce
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 8:13 ` Martin Jansa
@ 2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-03 2:50 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On 2015-05-02 4:13 AM, Martin Jansa wrote:
> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>
> Does it fix the issue I've reported few days ago?
> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
Nope. But one config warning is far down on the list when I'm
trying to introduce new -stable's and an entire -dev kernel.
I didn't forget about it, it'll just get done in priority order.
Bruce
>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>>
>> Bruce
>>
>>>
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>
>>> Cheers,
>>>
>>> Richard
>>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
@ 2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
1 sibling, 2 replies; 59+ messages in thread
From: Richard Purdie @ 2015-05-02 9:00 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >> - We have a refresh of the 3.14-rt support
> >> - bluetooh configuration changes for common-pc/qemux86
> >> - braswell BSP features and fixes
> >> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
> >>
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
>
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
I had a look into this. The issue is that this has been applied:
http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
but it needs:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
and the ioapic driver also appears to need:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
which meant I also had to add:
struct resource_win {
struct resource res; /* In master (CPU) address space */
resource_size_t offset; /* Translation offset for bridge */
};
to drivers/acpi/ioapic.c to make it compile which appears to be related to:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
which depends on a number of patches from around that time which change acpi/resource.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
(from 2015/2/3)
At this point I'm out my depth on how you want to fix this but it does
appear related to the Braswell changes.
To be clear qemux86 and qemux86-64 don't build at all with this series.
I'll see if I can just drop the Braswell parts.
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 23:30 ` Bruce Ashfield
@ 2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-02 9:00 ` Richard Purdie
1 sibling, 1 reply; 59+ messages in thread
From: Martin Jansa @ 2015-05-02 8:13 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >> - We have a refresh of the 3.14-rt support
> >> - bluetooh configuration changes for common-pc/qemux86
> >> - braswell BSP features and fixes
> >> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
Does it fix the issue I've reported few days ago?
http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
>
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
>
> Bruce
>
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >
> > Cheers,
> >
> > Richard
> >
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 22:59 ` Richard Purdie
@ 2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-02 9:00 ` Richard Purdie
0 siblings, 2 replies; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-01 23:30 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-01 6:59 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> The autobuilder showed up this for an x32 build :/.
Can one of the intel folks have a look at this ? I won't be able to get
to it until Tuesday at the earliest.
Bruce
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 1:34 Bruce Ashfield
@ 2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-03 21:30 ` Richard Purdie
1 sibling, 1 reply; 59+ messages in thread
From: Richard Purdie @ 2015-05-01 22:59 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
>
> - We have a refresh of the 3.14-rt support
> - bluetooh configuration changes for common-pc/qemux86
> - braswell BSP features and fixes
> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>
> I've built and booted these on my local machines and qemu, and
> everything was sane.
>
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.
The autobuilder showed up this for an x32 build :/.
https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
0 siblings, 2 replies; 59+ messages in thread
From: Bruce Ashfield @ 2015-05-01 1:34 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Here is the latest consolidated pull request for the supported linux-yocto
kernels.
- We have a refresh of the 3.14-rt support
- bluetooh configuration changes for common-pc/qemux86
- braswell BSP features and fixes
- Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
I've built and booted these on my local machines and qemu, and
everything was sane.
The -dev kernel obviously isn't something for deployment yet, but
it builds, and forms the base for follow up config changes, features
and development work. I built and booted core-image-kernel dev with
the 4.1 changes in place.
Cheers,
Bruce
The following changes since commit db409697db2ea0931cdcd2015d089b6b0ea39bbb:
bitbake: bitbake: reset build mtime cache before the build (2015-04-29 10:59:54 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/3.14: refresh -rt support
linux-yocto: add core bluetooth support to qemux86* and common-pc*
linux-yocto/3.19: Braswell support and bug fixes
perf: fix build (and feature tests) for 4.1-rcX
linux-yocto-dev: introduce 4.1-rc development kernel
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 18 +++++++++---------
meta/recipes-kernel/perf/perf.bb | 3 +++
7 files changed, 29 insertions(+), 26 deletions(-)
--
2.1.0
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 13:26 ` Bruce Ashfield
@ 2015-03-25 13:52 ` Richard Purdie
0 siblings, 0 replies; 59+ messages in thread
From: Richard Purdie @ 2015-03-25 13:52 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: Patches and discussions about the oe-core layer
On Wed, 2015-03-25 at 09:26 -0400, Bruce Ashfield wrote:
> On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> > On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> >>> Hi all,
> >>>
> >>> Here is the latest linux-yocto consolidated pull request. It is a mix of
> >>> kernel version -stable imports (CVEs and fixes), kernel configuration
> >>> changes, a documentation update and kernel configuration enhancement.
> >>>
> >>> The -stable updates are routine, and I build/boot tested them here
> >>> (with my fixup commits being evidence). These are ready for a round of
> >>> autobuilder/soak testing.
> >>
> >> Something in here broke lttng-modules causing cascades of failures on
> >> the autobuilder so I've updated it to the latest code on the 2.6 stable
> >> branch and am retesting.
> >
> > Gah. I built and booted here, but can't think of any reason why that didn't
> > trigger and fail here.
> >
> > I've started my own build as well, with a completely clean starting point.
>
> and sure enough, it blows up on my clean build.
>
> If your update doesn't resolve this, ping me and I'll take care of the fix.
It seemed to work, we've merged everything to master and branched for
the release. Release build now in progress so we'll see... :)
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 12:13 ` Bruce Ashfield
@ 2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-03-25 13:26 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>>> Hi all,
>>>
>>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>>> kernel version -stable imports (CVEs and fixes), kernel configuration
>>> changes, a documentation update and kernel configuration enhancement.
>>>
>>> The -stable updates are routine, and I build/boot tested them here
>>> (with my fixup commits being evidence). These are ready for a round of
>>> autobuilder/soak testing.
>>
>> Something in here broke lttng-modules causing cascades of failures on
>> the autobuilder so I've updated it to the latest code on the 2.6 stable
>> branch and am retesting.
>
> Gah. I built and booted here, but can't think of any reason why that didn't
> trigger and fail here.
>
> I've started my own build as well, with a completely clean starting point.
and sure enough, it blows up on my clean build.
If your update doesn't resolve this, ping me and I'll take care of the fix.
Bruce
>
> Bruce
>
>>
>> Cheers,
>>
>> Richard
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 9:26 ` Richard Purdie
@ 2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-03-25 12:13 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>> Hi all,
>>
>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>> kernel version -stable imports (CVEs and fixes), kernel configuration
>> changes, a documentation update and kernel configuration enhancement.
>>
>> The -stable updates are routine, and I build/boot tested them here
>> (with my fixup commits being evidence). These are ready for a round of
>> autobuilder/soak testing.
>
> Something in here broke lttng-modules causing cascades of failures on
> the autobuilder so I've updated it to the latest code on the 2.6 stable
> branch and am retesting.
Gah. I built and booted here, but can't think of any reason why that didn't
trigger and fail here.
I've started my own build as well, with a completely clean starting point.
Bruce
>
> Cheers,
>
> Richard
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-24 18:57 Bruce Ashfield
@ 2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Richard Purdie @ 2015-03-25 9:26 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> Hi all,
>
> Here is the latest linux-yocto consolidated pull request. It is a mix of
> kernel version -stable imports (CVEs and fixes), kernel configuration
> changes, a documentation update and kernel configuration enhancement.
>
> The -stable updates are routine, and I build/boot tested them here
> (with my fixup commits being evidence). These are ready for a round of
> autobuilder/soak testing.
Something in here broke lttng-modules causing cascades of failures on
the autobuilder so I've updated it to the latest code on the 2.6 stable
branch and am retesting.
Cheers,
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2015-03-24 18:57 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here is the latest linux-yocto consolidated pull request. It is a mix of
kernel version -stable imports (CVEs and fixes), kernel configuration
changes, a documentation update and kernel configuration enhancement.
The -stable updates are routine, and I build/boot tested them here
(with my fixup commits being evidence). These are ready for a round of
autobuilder/soak testing.
The only other change is the addition of the ability to use a defconfig
that is maintained within a kernel tree. This enhacement request came
from the raspberrypi2 maintainers. We went through a few revisions and
test cycles on this (see YOCTO: 7474 for the details).
The final result has no impact on existing configuration workflows, but
does allow an in-tree config to be copied out into WORKDIR and then
incorporated with other fragments as part of kconfig processing. A new
variable is introduced for specifying the defconfig KBUILD_DEFCONFIG,
and I'll work with Scott to make sure this is documented in the
appropriate locations.
Cheers,
Bruce
The following changes since commit 369932178fe9e7aa4a6d0e2ef1e2e539be701d02:
yocto-bsp: Update templates to 3.19 kernel (2015-03-24 10:06:03 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
kernel-yocto: allow in-tree defconfigs
linux-yocto/3.19: configuration updates and stable import
linux-yocto/3.14: integrate korg stable and meta data changes
linux-yocto/3.19: fixes for Intel core warnings
skeleton: clarify linux-yocto-custom workflow
.../recipes-kernel/linux/linux-yocto-custom.bb | 6 ++--
meta/classes/kernel-yocto.bbclass | 39 ++++++++++++++++++++--
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 20 +++++------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 20 +++++------
7 files changed, 69 insertions(+), 36 deletions(-)
--
2.1.0
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
` (2 preceding siblings ...)
2013-08-24 14:59 ` Bruce Ashfield
@ 2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-24 16:05 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
FYI: I've fixed the ARM 3.8 build issue here, it'll be in my series
tonight .. regardless if I'm removing 3.8, it was worth fixing.
Cheers,
Bruce
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
@ 2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-24 14:59 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
ok .. this time I'm REALLY going to step away for a few hours.
The mismatch is between the eglibc 2.18 sys/ptrace.h and the kernel's
definition of the structure. I wouldn't really call it a mismatch,
since they are both the same size and field types .. both simply
define it now.
I'm adding Khem: What's the right thing to do here?
I can obviously hack the kernel to remove the definition, but that make
the linux-yocto 3.10 the only kernel that will work against yocto 1.5's
eglibc for building any applications that use ptrace.h.
Falling back to the 3.8 headers will work, but again, we are avoiding
the problem and any end user that does bump to a newer set of libc-headers
will see the problem.
I'll wait for consensus on the approach and add a change if required
into my linux-yocto 3.8 removal patch tonight.
Bruce
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
@ 2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-24 14:47 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
I reproduced the failure here via adding ptrace to my image install.
The kernel change happened in april, and the good news is that the
structure is still exactly the same size, with the same fields. So the
userspace ABI is unchanged.
I'll hunt down the conflict and adjust the packages, since that kernel
header change will be there to stay.
Has anyone checked to see if the upstream version of those packages have
already adapted to the change ? I'll do that tonight when I'm back, if
no one else has.
Cheers,
Bruce
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
@ 2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
` (2 subsequent siblings)
3 siblings, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:53 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
Ah ok. I'll explicitly add dependencies on them here and restart
my sato build.
I'm a bit surprised that it failed, since user apis are a huge no-no
to change.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
probably because I didn't look at 3.8 ... since my plan was to delete
it!
I'll follow up with a fix for that tonight, if I can see the failure
here. Always fun!! :)
Leave that one with me. Do you have a link to the failure ?
Bruce
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:45 ` Bruce Ashfield
@ 2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
` (3 more replies)
0 siblings, 4 replies; 59+ messages in thread
From: Saul Wold @ 2013-08-24 13:50 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>> Richard/Saul,
>>>>
>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>> qemu machines.
>>>>
>>>> 3.10 also the latest LTSI and will be updated with that content when it
>>>> becomes available.
>>>>
>>>> Other features of the 3.10 kernel include:
>>>>
>>>> - refreshed -rt support
>>>> - refreshed yaffs2, aufs3
>>>> - cryptodev
>>>> - bfs, edf, and OCF staged features
>>>> - scrubbed and updated meta data for v3.10
>>>> - improved tools support for meta data updates and queue maintenance
>>>> - patch carry forward from all previous linux-yocto kernels and
>>>> configuration.
>>>>
>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>> shiny tree.
>>>>
>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>> gst-plugins-good
>>>> to adapt to a changed #define in the exported headers.
>>>>
>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>> manipulated and maintained via a smaller, more contained script. This
>>>> was necessary for both usability reasons and the fact that all of
>>>> guilts
>>>> protections were being removed for the kernel's use .. which makes you
>>>> ask the quesetion "why use it". It was time for a change.
>>>>
>>>> The patches are pretty self explanitory and all contain detailed long
>>>> logs .. but the summary is:
>>>>
>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>> [PATCH 2/5] guilt: update to latest git version
>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>> One of the changes in 3.10 seems to have introduced a conflicting
>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>
>>>> In file included from ptrace.h:22:0,
>>>> | from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>
>>>>
>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>> | struct ptrace_peeksiginfo_args {
>>>> | ^
>>>> | In file included from ptrace.h:9:0,
>>>> | from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>
>>>>
>>>> note: originally defined here
>>>> | struct ptrace_peeksiginfo_args
>>>> | ^
>>>
>>> This affects ltp, valgrind and strace.
>>>
>>> Please check the autobuilder as I am building with this change set and
>>> expect these failures.
>>
>> I'm unfortunately off for the weekend and won't have cycles to look into
>> any failures until Monday.
>
> As it turns out, I may have some time to work on this tonight, since I
> have to delete the 3.8 yocto recipe and get that patch out.
>
> So I've launched a LSB build in the background and will check on it
> later.
>
Just FYI, it might not show up in an LSB build, since those tools
valgrind, ltp and strace are more Dev tools, so a world build would be
better.
Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
AB. (lots of red).
I just restarted AB with out the 3.10 headers.
Sau!
> If anyone else does get a fix for this, make sure to cc' me on any
> changes, so I won't spend time trying to fix it a second time! :)
>
> Bruce
>
>>
>> So if you want to leave the old headers in place, that's an option.
>>
>> I fixed the one issue that I saw with Sato .. but I am after all one
>> person and can't possibly build and boot all the qemu boards with
>> all image combinations! This is after all, where I'd expect other
>> people to help out and fix build issues.
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> Sau!
>>>
>>> Sau!
>>>
>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>
>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>> want
>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>> a one man show on this update, and I wasn't able to get the 100+
>>>> patches
>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>
>>>> ** I'm still attempting to udpate all the reference boards, and
>>>> once done, I'll send a follow up patch.
>>>>
>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>> work issues in the stabilization period.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>>
>>>> The following changes since commit
>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>
>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>> +0100)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>
>>>> Bruce Ashfield (5):
>>>> kern-tools: usability, bug fixes and no guilt
>>>> guilt: update to latest git version
>>>> linux-libc-headers: update to v3.10
>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>> linux-yocto: introduce v3.10
>>>>
>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>> --------------------
>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>
>>>>
>>>>
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>> guilt-native_git.bb} (45%)
>>>> create mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>> delete mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>> create mode 100644
>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>
>>>>
>>>>
>>>>
>>
>
>
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:34 ` Bruce Ashfield
@ 2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:45 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
> On 13-08-24 2:33 AM, Saul Wold wrote:
>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>> Richard/Saul,
>>>
>>> Here's my consolidated set of changes that represent the biggest chunk
>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>> mark on). I've built and booted core-image-sato for all the oe-core
>>> qemu machines.
>>>
>>> 3.10 also the latest LTSI and will be updated with that content when it
>>> becomes available.
>>>
>>> Other features of the 3.10 kernel include:
>>>
>>> - refreshed -rt support
>>> - refreshed yaffs2, aufs3
>>> - cryptodev
>>> - bfs, edf, and OCF staged features
>>> - scrubbed and updated meta data for v3.10
>>> - improved tools support for meta data updates and queue maintenance
>>> - patch carry forward from all previous linux-yocto kernels and
>>> configuration.
>>>
>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>> shiny tree.
>>>
>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>> gst-plugins-good
>>> to adapt to a changed #define in the exported headers.
>>>
>>> Other parts of this update include an uprev of guilt, and in fact, a
>>> restoration of "normal" guil operations, since the kernel tree is now
>>> manipulated and maintained via a smaller, more contained script. This
>>> was necessary for both usability reasons and the fact that all of guilts
>>> protections were being removed for the kernel's use .. which makes you
>>> ask the quesetion "why use it". It was time for a change.
>>>
>>> The patches are pretty self explanitory and all contain detailed long
>>> logs .. but the summary is:
>>>
>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>> [PATCH 2/5] guilt: update to latest git version
>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>> One of the changes in 3.10 seems to have introduced a conflicting
>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>
>>> In file included from ptrace.h:22:0,
>>> | from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>
>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>> | struct ptrace_peeksiginfo_args {
>>> | ^
>>> | In file included from ptrace.h:9:0,
>>> | from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>
>>> note: originally defined here
>>> | struct ptrace_peeksiginfo_args
>>> | ^
>>
>> This affects ltp, valgrind and strace.
>>
>> Please check the autobuilder as I am building with this change set and
>> expect these failures.
>
> I'm unfortunately off for the weekend and won't have cycles to look into
> any failures until Monday.
As it turns out, I may have some time to work on this tonight, since I
have to delete the 3.8 yocto recipe and get that patch out.
So I've launched a LSB build in the background and will check on it
later.
If anyone else does get a fix for this, make sure to cc' me on any
changes, so I won't spend time trying to fix it a second time! :)
Bruce
>
> So if you want to leave the old headers in place, that's an option.
>
> I fixed the one issue that I saw with Sato .. but I am after all one
> person and can't possibly build and boot all the qemu boards with
> all image combinations! This is after all, where I'd expect other
> people to help out and fix build issues.
>
> Cheers,
>
> Bruce
>
>>
>> Sau!
>>
>> Sau!
>>
>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>
>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>> want
>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>> routerstationpro BSP is still using it as its preferred version. I'm
>>> a one man show on this update, and I wasn't able to get the 100+ patches
>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>
>>> ** I'm still attempting to udpate all the reference boards, and
>>> once done, I'll send a follow up patch.
>>>
>>> ** Please test, I've done my best, but things can slip through. We'll
>>> work issues in the stabilization period.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>
>>> The following changes since commit
>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>
>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>> +0100)
>>>
>>> are available in the git repository at:
>>>
>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>
>>> Bruce Ashfield (5):
>>> kern-tools: usability, bug fixes and no guilt
>>> guilt: update to latest git version
>>> linux-libc-headers: update to v3.10
>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>> linux-yocto: introduce v3.10
>>>
>>> meta/classes/kernel-yocto.bbclass | 2 +
>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>> --------------------
>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>> .../files/make_git_commands_conditional.patch | 48 ---
>>> .../guilt/files/optional_head_check.patch | 60 ----
>>> .../guilt/files/uninstall_force.patch | 14 -
>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>
>>>
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>> guilt-native_git.bb} (45%)
>>> create mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>> delete mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>> create mode 100644
>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>
>>>
>>>
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 6:33 ` Saul Wold
@ 2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:34 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 2:33 AM, Saul Wold wrote:
> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>> Richard/Saul,
>>
>> Here's my consolidated set of changes that represent the biggest chunk
>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>> mark on). I've built and booted core-image-sato for all the oe-core
>> qemu machines.
>>
>> 3.10 also the latest LTSI and will be updated with that content when it
>> becomes available.
>>
>> Other features of the 3.10 kernel include:
>>
>> - refreshed -rt support
>> - refreshed yaffs2, aufs3
>> - cryptodev
>> - bfs, edf, and OCF staged features
>> - scrubbed and updated meta data for v3.10
>> - improved tools support for meta data updates and queue maintenance
>> - patch carry forward from all previous linux-yocto kernels and
>> configuration.
>>
>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>> shiny tree.
>>
>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>> gst-plugins-good
>> to adapt to a changed #define in the exported headers.
>>
>> Other parts of this update include an uprev of guilt, and in fact, a
>> restoration of "normal" guil operations, since the kernel tree is now
>> manipulated and maintained via a smaller, more contained script. This
>> was necessary for both usability reasons and the fact that all of guilts
>> protections were being removed for the kernel's use .. which makes you
>> ask the quesetion "why use it". It was time for a change.
>>
>> The patches are pretty self explanitory and all contain detailed long
>> logs .. but the summary is:
>>
>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>> [PATCH 2/5] guilt: update to latest git version
>> [PATCH 3/5] linux-libc-headers: update to v3.10
> One of the changes in 3.10 seems to have introduced a conflicting
> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>
>> In file included from ptrace.h:22:0,
>> | from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>> | struct ptrace_peeksiginfo_args {
>> | ^
>> | In file included from ptrace.h:9:0,
>> | from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>> note: originally defined here
>> | struct ptrace_peeksiginfo_args
>> | ^
>
> This affects ltp, valgrind and strace.
>
> Please check the autobuilder as I am building with this change set and
> expect these failures.
I'm unfortunately off for the weekend and won't have cycles to look into
any failures until Monday.
So if you want to leave the old headers in place, that's an option.
I fixed the one issue that I saw with Sato .. but I am after all one
person and can't possibly build and boot all the qemu boards with
all image combinations! This is after all, where I'd expect other
people to help out and fix build issues.
Cheers,
Bruce
>
> Sau!
>
> Sau!
>
>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>> [PATCH 5/5] linux-yocto: introduce v3.10
>>
>> ** There is one pending activity. As part of thsi update to 3.10, we want
>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>> routerstationpro BSP is still using it as its preferred version. I'm
>> a one man show on this update, and I wasn't able to get the 100+ patches
>> ported to 3.10 AND get this update out before the M4 cutoff.
>>
>> ** I'm still attempting to udpate all the reference boards, and
>> once done, I'll send a follow up patch.
>>
>> ** Please test, I've done my best, but things can slip through. We'll
>> work issues in the stabilization period.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> The following changes since commit
>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>
>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.pokylinux.org/poky-contrib zedd/kernel
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>
>> Bruce Ashfield (5):
>> kern-tools: usability, bug fixes and no guilt
>> guilt: update to latest git version
>> linux-libc-headers: update to v3.10
>> gst-plugins-good: fix 3.10 libc-headers build failure
>> linux-yocto: introduce v3.10
>>
>> meta/classes/kernel-yocto.bbclass | 2 +
>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>> .../guilt/files/guilt-import-commit.patch | 96 ------
>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>> .../guilt/files/guilt-push-no-series.patch | 29 --
>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>> --------------------
>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>> .../files/make_git_commands_conditional.patch | 48 ---
>> .../guilt/files/optional_head_check.patch | 60 ----
>> .../guilt/files/uninstall_force.patch | 14 -
>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>> 23 files changed, 150 insertions(+), 861 deletions(-)
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>> guilt-native_git.bb} (45%)
>> create mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>> delete mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> create mode 100644
>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>
>>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
@ 2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
1 sibling, 1 reply; 59+ messages in thread
From: Saul Wold @ 2013-08-24 6:33 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
> [PATCH 2/5] guilt: update to latest git version
> [PATCH 3/5] linux-libc-headers: update to v3.10
One of the changes in 3.10 seems to have introduced a conflicting
definition of ptrace_peeksiginfo_args in linux/ptrace.h
> In file included from ptrace.h:22:0,
> | from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args'
> | struct ptrace_peeksiginfo_args {
> | ^
> | In file included from ptrace.h:9:0,
> | from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8: note: originally defined here
> | struct ptrace_peeksiginfo_args
> | ^
This affects ltp, valgrind and strace.
Please check the autobuilder as I am building with this change set and
expect these failures.
Sau!
Sau!
> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
> [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> kern-tools: usability, bug fixes and no guilt
> guilt: update to latest git version
> linux-libc-headers: update to v3.10
> gst-plugins-good: fix 3.10 libc-headers build failure
> linux-yocto: introduce v3.10
>
> meta/classes/kernel-yocto.bbclass | 2 +
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../guilt/files/guilt-import-commit.patch | 96 ------
> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
> .../guilt/files/guilt-push-no-series.patch | 29 --
> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
> meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
> .../guilt/files/improve_auto_header_gen.patch | 71 -----
> .../files/make_git_commands_conditional.patch | 48 ---
> .../guilt/files/optional_head_check.patch | 60 ----
> .../guilt/files/uninstall_force.patch | 14 -
> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
> .../kern-tools/kern-tools-native_git.bb | 6 +-
> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
> 23 files changed, 150 insertions(+), 861 deletions(-)
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
> delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
> create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-23 18:08 Bruce Ashfield
@ 2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
1 sibling, 0 replies; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-23 21:30 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Fri, Aug 23, 2013 at 2:08 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
> [PATCH 2/5] guilt: update to latest git version
> [PATCH 3/5] linux-libc-headers: update to v3.10
> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
> [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
Good news on this front. The routerstation pro (and it's replacement after
1.5) are working on 3.10 with the patches rebased. I'll follow up later with
the update of the rsp and the removal of the 3.8 recipe.
The beagleboard and fsl board will follow after that as well, pending some
boot testing.
Cheers,
Bruce
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> kern-tools: usability, bug fixes and no guilt
> guilt: update to latest git version
> linux-libc-headers: update to v3.10
> gst-plugins-good: fix 3.10 libc-headers build failure
> linux-yocto: introduce v3.10
>
> meta/classes/kernel-yocto.bbclass | 2 +
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../guilt/files/guilt-import-commit.patch | 96 ------
> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
> .../guilt/files/guilt-push-no-series.patch | 29 --
> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
> meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
> .../guilt/files/improve_auto_header_gen.patch | 71 -----
> .../files/make_git_commands_conditional.patch | 48 ---
> .../guilt/files/optional_head_check.patch | 60 ----
> .../guilt/files/uninstall_force.patch | 14 -
> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
> .../kern-tools/kern-tools-native_git.bb | 6 +-
> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
> 23 files changed, 150 insertions(+), 861 deletions(-)
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
> delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
> create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
0 siblings, 2 replies; 59+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
mark on). I've built and booted core-image-sato for all the oe-core
qemu machines.
3.10 also the latest LTSI and will be updated with that content when it
becomes available.
Other features of the 3.10 kernel include:
- refreshed -rt support
- refreshed yaffs2, aufs3
- cryptodev
- bfs, edf, and OCF staged features
- scrubbed and updated meta data for v3.10
- improved tools support for meta data updates and queue maintenance
- patch carry forward from all previous linux-yocto kernels and
configuration.
I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
to adapt to a changed #define in the exported headers.
Other parts of this update include an uprev of guilt, and in fact, a
restoration of "normal" guil operations, since the kernel tree is now
manipulated and maintained via a smaller, more contained script. This
was necessary for both usability reasons and the fact that all of guilts
protections were being removed for the kernel's use .. which makes you
ask the quesetion "why use it". It was time for a change.
The patches are pretty self explanitory and all contain detailed long
logs .. but the summary is:
[PATCH 1/5] kern-tools: usability, bug fixes and no guilt
[PATCH 2/5] guilt: update to latest git version
[PATCH 3/5] linux-libc-headers: update to v3.10
[PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
[PATCH 5/5] linux-yocto: introduce v3.10
** There is one pending activity. As part of thsi update to 3.10, we want
to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
routerstationpro BSP is still using it as its preferred version. I'm
a one man show on this update, and I wasn't able to get the 100+ patches
ported to 3.10 AND get this update out before the M4 cutoff.
** I'm still attempting to udpate all the reference boards, and
once done, I'll send a follow up patch.
** Please test, I've done my best, but things can slip through. We'll
work issues in the stabilization period.
Cheers,
Bruce
The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
kern-tools: usability, bug fixes and no guilt
guilt: update to latest git version
linux-libc-headers: update to v3.10
gst-plugins-good: fix 3.10 libc-headers build failure
linux-yocto: introduce v3.10
meta/classes/kernel-yocto.bbclass | 2 +
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../guilt/files/guilt-import-commit.patch | 96 ------
meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
.../guilt/files/guilt-push-no-series.patch | 29 --
meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
.../guilt/files/guilt-set-git_exec_path.patch | 29 --
...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
.../guilt/files/improve_auto_header_gen.patch | 71 -----
.../files/make_git_commands_conditional.patch | 48 ---
.../guilt/files/optional_head_check.patch | 60 ----
.../guilt/files/uninstall_force.patch | 14 -
.../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
.../kern-tools/kern-tools-native_git.bb | 6 +-
.../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
.../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
.../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
23 files changed, 150 insertions(+), 861 deletions(-)
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
--
1.7.10.4
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2012-02-05 6:31 Bruce Ashfield
@ 2012-02-08 4:09 ` Saul Wold
0 siblings, 0 replies; 59+ messages in thread
From: Saul Wold @ 2012-02-08 4:09 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: dvhart
On 02/04/2012 10:31 PM, Bruce Ashfield wrote:
> Richard/Saul,
>
> This is a follow on to the 3.2 tree and src_patches changes that I sent
> last week.
>
> The ability to specify out of tree BSPs via single .scc files is not
> possible, as well as any automatic BSPs following the naming conventions
> of the 3.2 tree.
>
> The meta branch changes are routine, with the exception being that I got
> a report that 3.0 -rt wasn't patching. That report turned out to be true,
> and I've fixed it here.
>
> Cheers,
>
> Bruce
>
> The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
>
> libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> linux-yocto: locate and use out of tree features specified on the
> SRC_URI
> linux-yocto: meta updates for sys940x and cleanup
> linux-yocto: rt compiliation fix
> kern-tools: remove explicit 'yocto' references from auto-bsp handling
> linux-yocto: fri2: use emgd-1.10
>
> meta/classes/kernel-yocto.bbclass | 21 ++++++++++++++++++++
> .../kern-tools/kern-tools-native_git.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 +-
> 5 files changed, 25 insertions(+), 4 deletions(-)
>
Merged into OE-core with updated patch set
Thanks
Sau!
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2012-02-05 6:31 UTC (permalink / raw)
To: richard.purdie; +Cc: dvhart, openembedded-core, saul.wold
Richard/Saul,
This is a follow on to the 3.2 tree and src_patches changes that I sent
last week.
The ability to specify out of tree BSPs via single .scc files is not
possible, as well as any automatic BSPs following the naming conventions
of the 3.2 tree.
The meta branch changes are routine, with the exception being that I got
a report that 3.0 -rt wasn't patching. That report turned out to be true,
and I've fixed it here.
Cheers,
Bruce
The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto: locate and use out of tree features specified on the
SRC_URI
linux-yocto: meta updates for sys940x and cleanup
linux-yocto: rt compiliation fix
kern-tools: remove explicit 'yocto' references from auto-bsp handling
linux-yocto: fri2: use emgd-1.10
meta/classes/kernel-yocto.bbclass | 21 ++++++++++++++++++++
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 +-
5 files changed, 25 insertions(+), 4 deletions(-)
--
1.7.4.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2012-01-11 18:52 Bruce Ashfield
@ 2012-01-17 19:28 ` Saul Wold
0 siblings, 0 replies; 59+ messages in thread
From: Saul Wold @ 2012-01-17 19:28 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On 01/11/2012 10:52 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Since this is a stabilization week, this probably can't be merged
> immediately, but I've been working with this enough to call it
> good enough, and me sitting on them longer doesn't help.
>
> The first change in this series is the switch of qemuppc from prep to
> mac99. With this, we'll close a whole set of issues (slow bootup) and
> close a feature gap that has existed for a while.
>
> I'm seeing a bit of strangeness with the mouse in my sato testing,
> but that's about it. Liming hasn't seen the same issues, so getting
> this into the tree will allow us to incrementally improve and debug
> this.
>
> The second change is a SRCREV update pulls in the forward looking
> fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
> that was found on the routerstationpro.
>
> Cheers,
>
> Bruce
>
> cc: Khem Raj<raj.khem@gmail.com>
> cc: Zumeng Chen<zumeng.chen@windriver.com>
> cc: Liming Wang<liming.wang@windriver.com>
>
> The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
>
> package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
> linux-yocto: consolidated fix SRCREV updates
>
> Liming Wang (4):
> qemuppc: replace emulation of qemuppc from prep to mac99
> qemuppc: add pointercal file
> qemuppc: add machconfig
> tslib: enable big endian support for qemuppc
>
> meta/conf/machine/qemuppc.conf | 2 +-
> .../formfactor/files/qemuppc/machconfig | 10 ++++++++++
> .../pointercal/files/qemuppc/pointercal | Bin 0 -> 36 bytes
> meta/recipes-graphics/tslib/tslib_1.0.bb | 1 +
> meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 6 +++---
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 15 ++++++++-------
> scripts/runqemu | 7 +------
> scripts/runqemu-internal | 16 ++++++++--------
> 8 files changed, 32 insertions(+), 25 deletions(-)
> create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
> create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
>
Merged into OE-Core
Thanks
Sau!
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
0 siblings, 1 reply; 59+ messages in thread
From: Bruce Ashfield @ 2012-01-11 18:52 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, saul.wold
Richard/Saul,
Since this is a stabilization week, this probably can't be merged
immediately, but I've been working with this enough to call it
good enough, and me sitting on them longer doesn't help.
The first change in this series is the switch of qemuppc from prep to
mac99. With this, we'll close a whole set of issues (slow bootup) and
close a feature gap that has existed for a while.
I'm seeing a bit of strangeness with the mouse in my sato testing,
but that's about it. Liming hasn't seen the same issues, so getting
this into the tree will allow us to incrementally improve and debug
this.
The second change is a SRCREV update pulls in the forward looking
fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
that was found on the routerstationpro.
Cheers,
Bruce
cc: Khem Raj <raj.khem@gmail.com>
cc: Zumeng Chen <zumeng.chen@windriver.com>
cc: Liming Wang <liming.wang@windriver.com>
The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto: consolidated fix SRCREV updates
Liming Wang (4):
qemuppc: replace emulation of qemuppc from prep to mac99
qemuppc: add pointercal file
qemuppc: add machconfig
tslib: enable big endian support for qemuppc
meta/conf/machine/qemuppc.conf | 2 +-
.../formfactor/files/qemuppc/machconfig | 10 ++++++++++
.../pointercal/files/qemuppc/pointercal | Bin 0 -> 36 bytes
meta/recipes-graphics/tslib/tslib_1.0.bb | 1 +
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 15 ++++++++-------
scripts/runqemu | 7 +------
scripts/runqemu-internal | 16 ++++++++--------
8 files changed, 32 insertions(+), 25 deletions(-)
create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
--
1.7.4.1
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
@ 2011-01-13 6:01 ` Saul Wold
1 sibling, 0 replies; 59+ messages in thread
From: Saul Wold @ 2011-01-13 6:01 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto, poky
On 01/10/2011 09:30 AM, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
>
> The remaining three changes are new and are:
>
> - A merge from Darren to update the default 2.6.37 configs
> to enable the debug/ftrace configs we need.
>
> - A change to make board descriptions generic. These are
> transparent to nearly everyone, but any new BSPs will be
> described with: KARCH, KMACHINE and KTYPE which are more
> generic variables and used internally during kernel
> configuration. They are differnet from yocto/poky variables
> on purpose, since the kernel tree can be cloned and used
> distinctly from any build system.
>
> - And finally an update to 2.6.37 with a port of the alternate
> RPC ports patch which reinstates usermode NFS support to
> 2.6.37.
>
> Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
> have all been booted against 2.6.37 and will follow shortly.
> Next up are feature merges (lttng, etc) to match the -stable
> kernel functionality.
>
> Cheers,
>
> Bruce
>
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: zedd/kernel
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
> Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (5):
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
> linux-yocto: update SRCREV to pickup debug/ftrace config changes
> kern-tools: create generic variables for platform/board/kernel
> linux-yocto: update to 2.6.37
>
> meta/classes/kernel-yocto.bbclass | 2 +-
> .../conf/distro/include/poky-default-revisions.inc | 28 ++++++++++----------
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Everything got pulled this time
In Master now
Thanks
Sau!
^ permalink raw reply [flat|nested] 59+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2011-01-10 17:30 Bruce Ashfield
@ 2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
1 sibling, 0 replies; 59+ messages in thread
From: Richard Purdie @ 2011-01-10 21:05 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto, poky, saul.wold
On Mon, 2011-01-10 at 12:30 -0500, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
>
> The remaining three changes are new and are:
>
> - A merge from Darren to update the default 2.6.37 configs
> to enable the debug/ftrace configs we need.
>
> - A change to make board descriptions generic. These are
> transparent to nearly everyone, but any new BSPs will be
> described with: KARCH, KMACHINE and KTYPE which are more
> generic variables and used internally during kernel
> configuration. They are differnet from yocto/poky variables
> on purpose, since the kernel tree can be cloned and used
> distinctly from any build system.
>
> - And finally an update to 2.6.37 with a port of the alternate
> RPC ports patch which reinstates usermode NFS support to
> 2.6.37.
>
> Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
> have all been booted against 2.6.37 and will follow shortly.
> Next up are feature merges (lttng, etc) to match the -stable
> kernel functionality.
Merged into master, thanks!
Richard
^ permalink raw reply [flat|nested] 59+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
0 siblings, 2 replies; 59+ messages in thread
From: Bruce Ashfield @ 2011-01-10 17:30 UTC (permalink / raw)
To: rpurdie; +Cc: yocto, poky, saul.wold
It looks like some of my last pull request didn't make it
to master, so I've repeated it here. Patches 4/5 have already
been sent:
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
The remaining three changes are new and are:
- A merge from Darren to update the default 2.6.37 configs
to enable the debug/ftrace configs we need.
- A change to make board descriptions generic. These are
transparent to nearly everyone, but any new BSPs will be
described with: KARCH, KMACHINE and KTYPE which are more
generic variables and used internally during kernel
configuration. They are differnet from yocto/poky variables
on purpose, since the kernel tree can be cloned and used
distinctly from any build system.
- And finally an update to 2.6.37 with a port of the alternate
RPC ports patch which reinstates usermode NFS support to
2.6.37.
Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
have all been booted against 2.6.37 and will follow shortly.
Next up are feature merges (lttng, etc) to match the -stable
kernel functionality.
Cheers,
Bruce
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---
Bruce Ashfield (5):
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
linux-yocto: update SRCREV to pickup debug/ftrace config changes
kern-tools: create generic variables for platform/board/kernel
linux-yocto: update to 2.6.37
meta/classes/kernel-yocto.bbclass | 2 +-
.../conf/distro/include/poky-default-revisions.inc | 28 ++++++++++----------
2 files changed, 15 insertions(+), 15 deletions(-)
^ permalink raw reply [flat|nested] 59+ messages in thread
end of thread, other threads:[~2023-02-01 16:28 UTC | newest]
Thread overview: 59+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-29 1:29 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-29 1:29 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.42 Bruce Ashfield
2020-05-29 1:29 ` [PATCH 2/5] linux-yocto-rt/5.4: update to rt24 Bruce Ashfield
2020-05-29 1:29 ` [PATCH 3/5] linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels Bruce Ashfield
2020-05-29 1:29 ` [PATCH 4/5] linux-yocto: gather reproducibility configs into a fragment Bruce Ashfield
2020-05-29 1:29 ` [PATCH 5/5] linux-yocto/5.4: update to v5.4.43 Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 16:28 [PATCH 0/5] linux-yocto: consolidated pull request bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
2015-05-07 6:33 ` Khem Raj
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.