forked from openwrt/openwrt
-
Notifications
You must be signed in to change notification settings - Fork 6
Mfw 963 bpftool patch #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The bpftool patches are from v4.16 of the linux kernel. Bpftool was introduced in v4.15 but the version needed for debugging xlated and jitted programs is in v4.16. These patches add bpftool as well as the libbpf and disasm files needed.
The following patches are modified in order for bpftool to build and be used. We didn't patch kernel/bpf/syscall.c and kernel/bpf/verifier.c for instance as they are not required for bpftool (self-contained in the tools directory) to be used. The patches and the subsequent modifications are as follows: 504-v4.16-bpf-move-instruction-printing-into-a-separate-file.patch: - Do not patch kernel/bpf/verifier.c 530-v4.16-bpf-use-char-in-prog-and-map-name.patch: - Do not patch include/linux/bpf.h - Do not patch include/uapi/linux/bpf.h 532-v4.16-bpf-cgroup-implement-ebpf-based-device-controller.patch: - Do not patch kernel/bpf/cgroup.c - Do not patch kernel/bpf/syscall.c - Do not patch kernel/bpf/verifier.c 536-v4.16-bpf-introduce-new-bpf-cpu-map-type.patch: - Do not patch kernel/bpf/syscall.c 549-v4.16-bpf-introduce-bpf-functions-calls-function-boundaries.patch: - Do not patch include/linux/bpf_verifier.h - Do not patch kernel/bpf/verifier.c 553-v4.16-bpf-allow-for-correlation-of-maps-and-helpers-in-dum.patch: - Do not patch include/linux/filter.h - Do not patch kernel/bpf/syscall.c - Do not patch kernel/bpf/verifier.c 556-v4.16-bpf-offload-report-device-information-for-off.patch: - Do not patch include/linux/bpf.h - Do not patch include/uapi/linux/bpf.h - Do not patch kernel/bpf/offload.c - Do not patch kernel/bpf/syscall.c - Whitespace correction in order for patch to succeed in bpf_prog_info 570-v4.16-bpf-offload-report-device-information-about-offloade.patch: - Do not patch include/linux/bpf.h - Do not patch include/uapi/linux/bpf.h - Do not patch kernel/bpf/offload.c - Do not patch kernel/bpf/syscall.c - Whitespace correction in order for patch to succeed in bpf_prog_info 576-v4.16-libbpf-add-error-reporting-in-XDP.patch: - Do not patch samples/bpf/Makefile
The bpftool patches are from v4.16 of the linux kernel. Bpftool was introduced in v4.15 but the version needed for debugging xlated and jitted programs is in v4.16. These patches add bpftool as well as the libbpf and disasm files needed.
The following patches are modified in order for bpftool to build and be used. We didn't patch kernel/bpf/syscall.c and kernel/bpf/verifier.c for instance as they are not required for bpftool (self-contained in the tools directory) to be used. The patches and the subsequent modifications are as follows: 504-v4.16-bpf-move-instruction-printing-into-a-separate-file.patch: - Do not patch kernel/bpf/verifier.c 530-v4.16-bpf-use-char-in-prog-and-map-name.patch: - Do not patch include/linux/bpf.h - Do not patch include/uapi/linux/bpf.h 532-v4.16-bpf-cgroup-implement-ebpf-based-device-controller.patch: - Do not patch kernel/bpf/cgroup.c - Do not patch kernel/bpf/syscall.c - Do not patch kernel/bpf/verifier.c 536-v4.16-bpf-introduce-new-bpf-cpu-map-type.patch: - Do not patch kernel/bpf/syscall.c 549-v4.16-bpf-introduce-bpf-functions-calls-function-boundaries.patch: - Do not patch include/linux/bpf_verifier.h - Do not patch kernel/bpf/verifier.c 553-v4.16-bpf-allow-for-correlation-of-maps-and-helpers-in-dum.patch: - Do not patch include/linux/filter.h - Do not patch kernel/bpf/syscall.c - Do not patch kernel/bpf/verifier.c 556-v4.16-bpf-offload-report-device-information-for-off.patch: - Do not patch include/linux/bpf.h - Do not patch include/uapi/linux/bpf.h - Do not patch kernel/bpf/offload.c - Do not patch kernel/bpf/syscall.c - Whitespace correction in order for patch to succeed in bpf_prog_info 570-v4.16-bpf-offload-report-device-information-about-offloade.patch: - Do not patch include/linux/bpf.h - Do not patch include/uapi/linux/bpf.h - Do not patch kernel/bpf/offload.c - Do not patch kernel/bpf/syscall.c - Whitespace correction in order for patch to succeed in bpf_prog_info 576-v4.16-libbpf-add-error-reporting-in-XDP.patch: - Do not patch samples/bpf/Makefile
…nto MFW-963-bpftool-patch
bmastbergen
pushed a commit
that referenced
this pull request
Oct 29, 2020
MFW-620 Version and Device parameters
untangle-bot
pushed a commit
that referenced
this pull request
Aug 22, 2021
Rearrange all voltage triplets for "opp_table0" to match the specifications. "opp-microvolt" and "opp-microvolt-<name>" triplets are in order of <target min max>, and NOT <min target max>. Previously, the CPU would *always* spend its time at the "minimum" voltage, ignoring the actual intended target. This is a regression from previous behavior. On an NBG6817 with a Qualcomm CPU of PVS bin #2... (see &opp_table0 -> opp-1725000000 -> opp-microvolt-speed0-pvs2-v0) * Before: /usr/bin/tail -n +1 /sys/kernel/debug/opp/cpu0/opp\:1725000000/supply-0/u_volt_* ==> /sys/kernel/debug/opp/cpu0/opp:1725000000/supply-0/u_volt_max <== 1260000 ==> /sys/kernel/debug/opp/cpu0/opp:1725000000/supply-0/u_volt_min <== 1200000 ==> /sys/kernel/debug/opp/cpu0/opp:1725000000/supply-0/u_volt_target <== 1140000 * After: /usr/bin/tail -n +1 /sys/kernel/debug/opp/cpu0/opp\:1725000000/supply-0/u_volt_* ==> /sys/kernel/debug/opp/cpu0/opp:1725000000/supply-0/u_volt_max <== 1260000 ==> /sys/kernel/debug/opp/cpu0/opp:1725000000/supply-0/u_volt_min <== 1140000 ==> /sys/kernel/debug/opp/cpu0/opp:1725000000/supply-0/u_volt_target <== 1200000 To check voltages and frequencies at run time, use... /bin/cat /sys/kernel/debug/regulator/regulator_summary && /bin/cat /sys/kernel/debug/clk/clk_summary | grep "hfpll" See https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation/devicetree/bindings/opp/opp.txt?h=v5.4.142#n91 Fixes: 1e25423 ("ipq806x: refresh dtsi patches") Signed-off-by: Shane Synan <digitalcircuit36939@gmail.com> Reviewed-by: Ansuel Smith <ansuelsmth@gmail.com> [commit message style cleanup, another kernel refresh] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
untangle-bot
pushed a commit
that referenced
this pull request
Nov 28, 2021
Follow up to commit 565b62c. Managed to hit the very same issue again while playing with the NOR SPL builds. Signed-off-by: Mathias Kresin <dev@kresin.me>
untangle-bot
pushed a commit
that referenced
this pull request
Nov 28, 2021
Follow up to commit 8fb714e. Managed to hit the very same issue again while playing with the NOR SPL builds. Signed-off-by: Mathias Kresin <dev@kresin.me>
sdelafond
pushed a commit
that referenced
this pull request
Jul 6, 2022
Follow up to commit c744798. Managed to hit the very same issue again while playing with the NOR SPL builds. Signed-off-by: Mathias Kresin <dev@kresin.me>
untangle-bot
pushed a commit
that referenced
this pull request
May 21, 2023
Iomega Storcenter ix4-200d is a four-bay SATA NAS powered by a Marvell Kirkwood SoC clocked at 1.2GHz. It has 512MB of RAM and 32MB of flash memory, 3x USB 2.0 and 2x 1Gbit/s NIC Specification: - SoC: Marvell Kirkwood 88F6281 - CPU/Speed: 1200Mhz - Flash size: 32 MiB - RAM: 512MB - LAN: 2x 1Gbit/s - 3x USB 2.0 Notes: - The blue drive LED is triggered by HDD activity, it can not be controlled via GPIO. - The LCD screen requires proprietary code and does not function at this time. - Due to a kernel-related issue with the Marvell 88SE6121 SATA controller, currently only trays numbered #3 and #4 work, #1 and #2 do not. [1] Serial pinout: CN4 -------------- | 10 8 6 4 2 | | 9 7 5 3 1 | -------------- PIN 1 Mark (fat line) 1 = RXD 4 = TXD 6 = GND 9 = 3.3V (not necessary to connect) Installation instructions: 1. download initramfs-uImage and copy into tftp server 2. connect the tftp server to network port #1 3. access uboot environment with serial cable and run setenv mainlineLinux yes setenv arcNumber 1682 setenv console 'console=ttyS0,115200n8' setenv mtdparts 'mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x20000@0xA0000(u-boot environment)ro,0x300000@0x100000(kernel),0x1C00000@0x400000(ubi)' setenv bootargs_root 'root=' setenv bootcmd 'setenv bootargs ${console} ${mtdparts} ${bootargs_root}; nand read.e 0x800000 0x100000 0x300000; bootm 0x00800000' saveenv setenv serverip 192.168.1.1 setenv ipaddr 192.168.1.2 tftpboot 0x00800000 [initramfs-uImage filename] bootm 0x00800000 4. connect to LAN on network port #2, log into openwrt and sysupgrade to install into flash [1] https://bugzilla.kernel.org/show_bug.cgi?id=216094 Signed-off-by: Sander van Deijck <sander@vandeijck.com> (aligned FROM from signed-off. LED+key rename, whitespace removal) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
untangle-bot
pushed a commit
that referenced
this pull request
Jul 17, 2024
Hardware specification: SoC: MediaTek MT7981B 2x A53 Flash: 16MB NOR RAM: 256MB Ethernet: 2x 10/100/1000 Mbps Switch: MediaTek MT7531AE WiFi: MediaTek MT7976C Button: Reset Power: DC 12V 1A, PoE 802.3af 48V Flash instructions: Option #1 - SSH I was able to SSH into the stock firmware of my device. 1. Attach the router to the network 2. Use scp (-O) to copy the sysupgrade image 3. Connect using SSH and run `sysupgrade -n` Option #2 - U-Boot One way to use the bootloader for flashing is using TFTP: 1. Connect to the router using an ethernet cable 2 Spin up a TFTP server serving the sysupgrade file 3. Open the case and attach a UART 4. Attach power to the router and interrupt the countdown by pressing any key 5. Select option #2 (Upgrade firmware) 6. Enter IP address information and image name 7. Wait patiently Co-Authored-By: Enrique Rodríguez Valencia <enrique.rodriguez@galgus.net> Co-Authored-By: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Leon M. Busch-George <leon@georgemail.eu> (cherry picked from commit b4086f4)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.