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 21, 2021
  3. Aug 20, 2021
  5. Aug 19, 2021
  7. Aug 18, 2021
    • Adrian Schmutzler's avatar
      ath79: convert remaining mtd-mac-address cases to nvmem · e826b642
      Adrian Schmutzler authored 
      
Since the nvmem-based approach for retrieving MAC addresses
appears to depend on the addresses being set up after the
partitions, it is no longer possible to keep the MAC address
setup in shared DTSI files while the partitions itself are
set up in DTS files for the individual devices.

In ath79 the firmware partition is typically located somewhere
"in the middle" of the partition table. Thus, it's not trivial
to share the partitions containing MAC address information in
a common DTSI (like we did in some cases on ramips).

In this commit, MAC address setup is thus moved to the relevant
partitions, and in most cases needs to be duplicated. While
the duplication is not really nice, it eventually provides a
cleaner and more tidy setup, making the DTS(I) file
fragmentation a bit more logical. This should also help
with adding new devices, as information is distributed across
less locations.

For consistency, this commit also moves the mtd-cal-data property
"down" together with the MAC address setup, so it's not based
on a partition before the latter is defined either. (This is
only done for those files touched due to nvmem conversion.)

Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      e826b642
    • Adrian Schmutzler's avatar
      ramips: convert most mtd-mac-address cases in DTSI to nvmem · ba3d92c5
      Adrian Schmutzler authored 
      
Convert most of the cases from mtd-mac-address to nvmem where
MAC addresses are set in the DTSI, but the partitions are only
located in the device DTS. This posed some problems earlier, since
in these cases we are using partitions before they are defined,
and the nvmem system did not seem to like that.

There have been a few different resolution approaches, based on
the different tradeoffs of deduplication vs. maintainability:

 1. In many cases, the partition tables were identical except for
    the firmware partition size, and the firmware partition was
    the last in the table.
    In these cases, the partition table has been moved to the
    DTSI, and only the firmware partition's "reg" property has
    been kept in the DTS files. So, the updated nvmem definition
    could stay in the DTSI files as well.

 2. For all other cases, splitting up the partition table would
    have introduced additional complexity. Thus, the nodes to be
    converted to nvmem have been moved to the DTS files where the
    partitioning was defined.

 3. For Netgear EX2700 and WN3000RP v3, the remaining DTSI file
    was completely dissolved, as it was quite small and the name
    was not really nice either.

 4. The D-Link DIR-853 A3 was converted to nvmem as well, though
    it is just a plain DTS file not taken care of in the first
    wave.

In addition, some minor rearrangements have been made for tidyness.

Not covered (yet) by this patch are:

 * Various unielec devices
 * The D-Link DIR-8xx family

Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      ba3d92c5
    • Michael Heimpold's avatar
      bcm27xx-userland: factor out a -dev package · 9a79fe20
      Michael Heimpold authored 
      
Installing headers and static libraries to the target system seems
to be not required for most use cases, so let's factor them
out into a dedicated -dev package.

This cuts down to disk usage to around 50% of the original
package to ~ 2MB - not that disk space is an issue normally,
but when using inside an initramfs only project, it counts.

Signed-off-by: default avatarMichael Heimpold <mhei@heimpold.de>
      9a79fe20
    • Stijn Tintel's avatar
      toolchain/gcc: switch to version 10 by default · 6d0cefcf
      Stijn Tintel authored 
      
Runtime-tested on:
* ath79
* bcm27xx/bcm2708
* bcm27xx/bcm2709
* bcm27xx/bcm2711
* mvebu/cortexa53
* octeon
* realtek
* x86/64

Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
Acked-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      6d0cefcf
    • Stijn Tintel's avatar
      toolchain/binutils: switch to version 2.36.1 by default · 3f41153b
      Stijn Tintel authored 
      
Runtime-tested on:
* ath79
* bcm27xx/bcm2708
* bcm27xx/bcm2709
* bcm27xx/bcm2711
* mvebu/cortexa53
* octeon
* realtek
* x86/64

Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
Acked-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      3f41153b
    • Stijn Tintel's avatar
      umbim: bump to git HEAD · 959838ed
      Stijn Tintel authored 
      
 de56231 umbim: fix compilation with GCC 10

Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
Acked-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      959838ed
    • Stijn Tintel's avatar
      busybox: fix compilation with GCC 10 · 8ae3d5f9
      Stijn Tintel authored 
      
When compiling busybox with GCC 10 and CONFIG_PKG_ASLR_PIE_ALL=y, there
are hundreds of errors like:

relocation R_MIPS16_26 against `xzalloc' cannot be used when making a
shared object; recompile with -fPIC

Simply solve this by no longer disabling PKG_ASLR_PIE, so that $(FPIC)
is properly added to the CFLAGS and LDFLAGS.

Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
Acked-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      8ae3d5f9
    • Stijn Tintel's avatar
      ipq40xx: fix Edgecore ECW5211 boot · a43da1be
      Stijn Tintel authored 
      
The bootloader will look for a configuration section named ap.dk01.1-c2
in the FIT image. If this doesn't exist, the device won't boot.

Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      a43da1be

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