Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v17.01.1
  • v17.01.0
  • v17.01.0-rc2
  • v17.01.0-rc1
  • reboot
6 results
Search by author
  • Any Author
  • Johannes Rudolph Johannes Rudolph PowerPan
1 author
  1. May 23, 2015
  3. May 22, 2015
  5. May 21, 2015
  7. May 20, 2015
    • Steven Barth's avatar
      generic/4.0: fix error during kernel patch application · 53098a8a
      Steven Barth authored 
      
Commit 5168c9a5702648eb690d32ec821647aca80aeba9 introduced a regression
during patch application on the 4.0 kernel. Some of the patched content
doesn't match the actual code, therefore leading to the following error:
  Applying patch generic/667-ipv6-Fixed-source-specific-default-route-handling.patch
  patching file net/ipv6/ip6_output.c
  Hunk #1 FAILED at 886.
  1 out of 1 hunk FAILED -- rejects in file net/ipv6/ip6_output.c
  patching file net/ipv6/route.c
  Hunk #1 succeeded at 2247 (offset 2 lines).
  Patch generic/667-ipv6-Fixed-source-specific-default-route-handling.patch does not apply (enforce with -f)

This change just adapts the actual patch to fix what is in kernel 4.0
and make it apply cleanly.

Signed-off-by: default avatarMathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45705
      53098a8a
  9. May 19, 2015
  11. May 17, 2015
  13. May 16, 2015
  15. May 13, 2015
  17. May 12, 2015
  19. May 11, 2015
  21. May 10, 2015
    • Felix Fietkau's avatar
      mtd: remove the warning about read-only caused by size vs. block boundary mismatch · ac0e2479
      Felix Fietkau authored 
      Since the kernel/rootfs split handling was modified 2 years ago by r37283 (
https://dev.openwrt.org/changeset/37283

 ) and by the subsequent checkins,
users have seen rather scary mtd errors in the log at every boot. The message
ends "-- forcing read-only", which looks a bit error-like. That error has
been mentioned in some forum threads, when users have noticed this message
instead of some actual error.

[    2.940000] 0x000000070000-0x000000ff0000 : "firmware"
[    2.970000] 2 netgear-fw partitions found on MTD device firmware
[    2.970000] 0x000000070000-0x000000188440 : "kernel"
[    2.980000] mtd: partition "kernel" must either start or end on erase
block boundary or be smaller than an erase block -- forcing read-only
[    2.990000] 0x000000188440-0x000000ff0000 : "rootfs"

The patch removes the rather useless warning message.

signed-off-by: default avatarHannu Nyman <hannu.nyman@iki.fi>

SVN-Revision: 45669
      ac0e2479
    • Felix Fietkau's avatar
      ar71xx: add platform_pre_upgrade for sysupgrade · b3375205
      Felix Fietkau authored 
      
Signed-off-by: default avatarRafał Miłecki <zajec5@gmail.com>

SVN-Revision: 45667
      b3375205
    • Felix Fietkau's avatar
      kernel: fix regression in backtrace module info change (#19631) · 9ebb99cb
      Felix Fietkau authored 
      
Signed-off-by: default avatarFelix Fietkau <nbd@openwrt.org>

SVN-Revision: 45665
      9ebb99cb
    • Felix Fietkau's avatar
      ipq806x: add pcie support to ipq806x based platforms · cfb56b48
      Felix Fietkau authored 
      This change adds PCIe support to IPQ806x based platforms. The driver is
actually cherry-picked from the following LKML thread:
*https://lwn.net/Articles/643086/

 (patches 110-111)

We also add here an additional fix to support multiple PCI controllers
on the same platform (patch 112), and to patch the ap148 & dbs149 DTS
files (patch 113).

Signed-off-by: default avatarMathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45663
      cfb56b48
    • Felix Fietkau's avatar
      ipq806x: add support for zImage kernel · 3c4bc0cd
      Felix Fietkau authored 
      
This change enable zImage+appended dtb support in ipq806x kernel
options. The zImage will now be generated as part of the kernel
binaries. Platforms which do not have DT support enabled in U-boot
can now make use of it by generating zImage files and appending dtb
to it.

It is not used yet but it is done as a stepping stone for early IPQ806x
platforms, which did not include DT support in U-boot.

Signed-off-by: default avatarMathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45662
      3c4bc0cd
    • Felix Fietkau's avatar
      ipq806x: fix boot freeze on zImage kernel · bdcba364
      Felix Fietkau authored 
      
ARCH_QCOM is using the ARCH_MULTIPLATFORM option, as now recommended
on most ARM architectures. This automatically calculate ZRELADDR by
masking PHYS_OFFSET with 0xf8000000.

On IPQ806x though, the first ~20MB of RAM is reserved for the hardware.
In newer bootloader, when DT is used, this is not a problem, we just
reserve this memory in the device tree. But if the bootloader doesn't
have DT support, then ATAGS have to be used. In this case, the ARM
decompressor will position the kernel in this low mem, which will not be
in the RAM section mapped by the bootloader, which means the kernel will
freeze in the middle of the boot process trying to map the memory.

As a work around, this patch allows disabling AUTO_ZRELADDR when
ARCH_QCOM is selected. It makes the zImage usage possible on bootloaders
which don't support device-tree, which is the case on certain early
IPQ806x based designs.

Signed-off-by: default avatarMathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45661
      bdcba364
    • Felix Fietkau's avatar
      generic: add CRYPTO_DEV_QCE option to default config · 9913b6a9
      Felix Fietkau authored 
      
This option has been added in kernel 3.17. It shows-up only when both
ARCH_QCOM and CRYPTO are enabled. So we'll disable these two by default
to avoid stalling the build when these conditions are met.

Signed-off-by: default avatarMathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45658
      9913b6a9