Tags give the ability to mark specific points in history as being important
-
orange-pi-5.9-20201019-1553
034fb475 · ·Release: orange-pi-5.9-20201019-1553 NEWS ==== See also: - https://xnux.eu/log/ - https://xnux.eu/devices/pine64-pinephone.html - https://xff.cz/kernels/ 2020-10-19: - fix orange pi 3 ethernet 2020-10-12: - fix issue with dsi clock described here: https://xnux.eu/log/#021 - rebase on v5.9 final - integrate pinetab panel patches from (untested) https://gitlab.com/pine64-org/linux/-/commits/pine64-kernel-5.7.y-pinetabpanel/ 2020-09-29: - add a few more codec API fixes from Samuel 2020-09-28: - rebase on top of 5.9-rc7 - integrated the newest audio patches from Samuel 2020-09-23: - port battery thermal regulation fix from p-boot (completely untested, see https://xnux.eu/log/#018) 2020-09-18: - cedrus panic fix - rebase on linus/master 2020-09-17: - further modem driver improvements (fix urc setting on old modem firmwares) 2020-09-13: - rebase on top of 5.9-rc5 2020-09-12: - rebase on top of 5.9-rc4+ 2020-09-10: - rebase on top of 5.9-rc4+ - further fixes for the modem driver poweron, support for fast poweroff feature present on new modem firmware - added flash DT changes - add mounting matrix and a kernel command line option to override it (ignore_mount_matrix) - https://xff.cz/kernels also contains special kernel builds for my multi-dist image (see https://xnux.eu/log/) - enabled opportunistic sleep - enabled btrfs support 2020-09-01: - rebase on top of 5.9-rc3 2020-08-19: - rebase and port to 5.9-rc1 - fix various issues with 5.9-rc1 - fix sleeps in atomic context in anx7688 driver - dropped panfrost dvfs patches for now (conflicts, stability issues) - fix modem UART issues on powerup (sometimes not receiving RDY, etc.) - root cause was host UART locking up due to noise on RX, and the fix is to only open UART port when the modem is powered 2020-08-11: - fix sun50i-codec-analog probe failure when built-in 2020-08-09: - pull in codec changes from Samuel - don't wait for RDY but poll with empty AT command for the modem's status 2020-08-06: - added Samuel's patch for making recording from the codec work again 2020-08-05: - modem driver fixes for BH 2020-08-03: - fixed AC100 driver to make it work without mod clock 2020-08-02: - integrated latest Samuel's audio patches + rebased my AC100 support on top - finished the modem-power driver into a hopefully useable state 2020-07-25: - rebased on top of 5.8-rc7+ - fixed modem driver issue with not shutting down the modem on poweroff/reset on PinePhone (introduced during modem driver rewrite around 5.8-rc5) - worked around AXP reseting input current limit to 500mA regardless of BC detection being disabled (happened on boot with USB-C cable connected to USB-C PD charger) (and reverted again) - improved modem driver - initialize the modem configuration for proper sleep - setup QDAI automatically from DTS - show modem firmware version in dmesg - added rfkill interface - handle URC caching during suspend 2020-07-16: - added HP jack detection patches from A-wai 2020-07-14: - added support for Pinebook Pro - fix issue in my bl_pwm PinePhone patch that broke Pinebook Pro's backlight 2020-07-13: - rebased on top of 5.8-rc5 - improved HW led trigger API - more modem-power work (change to serdev, recv messages from the modem) - support HDMI audio on PinePhone - bump PD power requirement to 15W on PinePhone 2020-07-08: - refactoring of the modem driver, moved to modem-5.8 branch (not finished yet, see TODO in the driver) - update pinephone 1.0-1.2 dts to reflect the differences in modem setup - enable orange pi 3 hdmi audio 2020-07-06: - rebased on top of 5.8-rc4 2020-07-05: - Added fixes for PinePhone panel initialization after resume from sleep 2020-07-04: - Integrated Clément's HDMI audio series (20200704113902.336911-1-peron.clem@gmail.com) - Integrated Clément's panfrost DVFS series (20200704102535.189647-1-peron.clem@gmail.com) My kernel's main integration branch is 'orange-pi-$VER' (this one). No other branch is supposed to work alone. My defconfigs are tested and work on the boards I support. Read the README.md for more info. Only my branches based on the current mainline kernel branch are maintained (those are usually the -rc# kernels!). You can find the current mainline version here https://www.kernel.org/ (mainline: ...) My prebuilt kernels can be found at https://xff.cz/kernels/ You can use them to test that your board works, or just run them without bothering with building everything yourself. I run them on all my boards. My website is https://xnux.eu and may contain useful advice. Good luck! ~megi -
xfs-5.10-merge-5
89464554 · ·Recalling the first round of new code for 5.10, in which we added: - New feature: Widen inode timestamps and quota grace expiration timestamps to support dates through the year 2486. - New feature: storing inode btree counts in the AGI to speed up certain mount time per-AG block reservation operatoins and add a little more metadata redundancy. For the second round of new code for 5.10: - Deprecate the V4 filesystem format, some disused mount options, and some legacy sysctl knobs now that we can support dates into the 25th century. Note that removal of V4 support will not happen until the early 2030s. - Fix some probles with inode realtime flag propagation. - Fix some buffer handling issues when growing a rt filesystem. - Fix a problem where a BMAP_REMAP unmap call would free rt extents even though the purpose of BMAP_REMAP is to avoid freeing the blocks. - Strengthen the dabtree online scrubber to check hash values on child dabtree blocks. - Actually log new intent items created as part of recovering log intent items. - Fix a bug where quotas weren't attached to an inode undergoing bmap intent item recovery. - Fix a buffer overrun problem with specially crafted log buffer headers. - Various cleanups to type usage and slightly inaccurate comments. - More cleanups to the xattr, log, and quota code. - Don't run the (slower) shared-rmap operations on attr fork mappings. - Fix a bug where we failed to check the LSN of finobt blocks during replay and could therefore overwrite newer data with older data. - Clean up the ugly nested transaction mess that log recovery uses to stage intent item recovery in the correct order by creating a proper data structure to capture recovered chains. - Use the capture structure to resume intent item chains with the same log space and block reservations as when they were captured. - Fix a UAF bug in bmap intent item recovery where we failed to maintain our reference to the incore inode if the bmap operation needed to relog itself to continue. - Rearrange the defer ops mechanism to finish newly created subtasks of a parent task before moving on to the next parent task. - Automatically relog intent items in deferred ops chains if doing so would help us avoid pinning the log tail. This will help fix some log scaling problems now and will facilitate atomic file updates later. - Fix a deadlock in the GETFSMAP implementation by using an internal memory buffer to reduce indirect calls and copies to userspace, thereby improving its performance by ~20%. - Fix various problems when calling growfs on a realtime volume would not fully update the filesystem metadata. - Fix broken Kconfig asking about deprecated XFS when XFS is disabled.
-
-
vfs-rearrange-remap-helpers_2020-10-15
407e9c63 · ·vfs: move the clone/dedupe/remap helpers to a single file I would like to move the generic helper functions that support the file remap range operations (aka clone and dedupe) to a separate file under fs/. For the moment, I have a few goals here: one is to declutter fs/read_write.c and mm/filemap.c. The second goal is to be able to deselect all the remap code if no filesystems require it. The third (and much more long term) goal is to have a place to land the generic code for the atomic file extent swap functionality, since it will reuse some of the functionality. Someday. Whenever I get around to submitting that again. AFAICT, nobody is attempting to land any major changes in any of the vfs remap functions during the 5.10 window -- for-next showed conflicts only in the Makefile, so it seems like a quiet enough time to do this. There are no functional changes here, it's just moving code blocks around. v2: move a few more things
-
-