Skip to content
Snippets Groups Projects
Select Git revision
  • add-tplink-eap225-outdoor-v3-support protected
  • master default
  • v21.02.2
3 results
Search by author
  • Any Author
  • Linus Lüssing Linus Lüssing tux
  • Paul Paul paul
  • Philipp Rothmann Philipp Rothmann yksflip
  • Till Till eex
4 authors
  1. Aug 31, 2019
  3. Aug 30, 2019
    • Christian Lamparter's avatar
      build: remove harmful -nopad option from mksquashfs · 1c0290c5
      Christian Lamparter authored 
      
While the -nopad option prevents mksquashfs from padding the
image to an arbitrary 4k. It does not take into consideration
that squashfs is programmed to have this 4k padding when it's
being used on on a block device... which is its main "use-case".

Now, after a week long discussion on the ML that included a
back-and-forth between some of the possible options.
But this is likely the best KISS patch to deal with the issue
right away given the limited resources.

From squashfs code point of view, be warned. The 4k padding is
not enough when dealing with devices that have a PAGE_SIZE
bigger than 4k.

if it turns out to be affecting you, then please look-up either:
"FS#2460 - kernel panic reading squashfs from ubi volume" bug
Or the discussion on the OpenWrt-Devel ML in
"amp821xx: use newly added pad-squashfs for Meraki MR24" and
"Squashfs breakage lottery with UBI..."
before making an educated guess.

Note: This will not affect the "tiny"/small flash devices as
much as it seems at first. This is because the the rootfs_data
partition that follows uses jffs2. And it requires to be aligned
to the flash block-size in order to work at all.

So either the involved FSes will meet in the middle as before,
or not at all. But in that latter case the image was already
hoping for the "undefined behaviour" gamble to turn out in its
favour and this is probably why this was unnoticed for so long.

Fixes: FS#2460
Reported-by: default avatarRussell Senior <russell@personaltelco.net>
Signed-off-by: default avatarChristian Lamparter <chunkeey@gmail.com>
      1c0290c5
    • Koen Vandeputte's avatar
      kernel: bump 4.19 to 4.19.69 · db97cb81
      Koen Vandeputte authored 
      
Refreshed all patches.

Compile-tested on: cns3xxx
Runtime-tested on: cns3xxx

Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      db97cb81
    • Koen Vandeputte's avatar
      kernel: bump 4.14 to 4.14.141 · 071209ed
      Koen Vandeputte authored 
      
Refreshed all patches.

Compile-tested on: cns3xxx
Runtime-tested on: cns3xxx

Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      071209ed
    • Rafał Miłecki's avatar
      base-files: use JSON for storing firmware validation info · f5220479
      Rafał Miłecki authored 
      
So far firmware validation result was binary limited: it was either
successful or not. That meant various limitations, e.g.:
1) Lack of proper feedback on validation problems
2) No way of marking firmware as totally broken (impossible to install)

This change introduces JSON for storing detailed validation info. It
provides a list of performed validation tests and their results. It
allows marking firmware as non-forceable (broken image that can't be
even forced to install).
Example:
{
        "tests": {
                "fwtool_signature": true,
                "fwtool_device_match": true
        },
        "valid": true,
        "forceable": true
}

Implementation is based on *internal* check_image bash script that:
1) Uses existing validation functions
2) Provides helpers for setting extra validation info

This allows e.g. platform_check_image() to call notify_check_broken()
when needed & prevent user from bricking a device.

Right now the new JSON info is used by /sbin/sysupgrade only. It still
doesn't make use of "forceable" as that is planned for later
development.

Further plans for this feature are:
1) Expose firmware validation using some new ubus method
2) Move validation step from /sbin/sysupgrade into "sysupgrade" ubus
   method so:
   a) It's possible to safely sysupgrade using ubus only
   b) /sbin/sysupgrade can be more like just a CLI

Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      f5220479
    • John Crispin's avatar
      mediatek: backport a pcie fix · 7f9edadf
      John Crispin authored 
      
PCI/e probe was failing under certain situations.

Signed-off-by: default avatarJohn Crispin <john@phrozen.org>
      7f9edadf
    • John Crispin's avatar
      linux-firmware: add mediatek BT firmware · 63c722c0
      John Crispin authored 
      
Signed-off-by: default avatarJohn Crispin <john@phrozen.org>
      63c722c0
  5. Aug 29, 2019
  7. Aug 28, 2019
  9. Aug 27, 2019

Hosted with love by Chaotikum e.V. Support us if you can