Conversation
john-tho
force-pushed
the
routerboot-v7
branch
3 times, most recently
from
ce6cece to
fd635d8
Compare
|
This is just rebased or there is some modifications compared to the previous one you want us to test? |
|
(Hopefully—rebase fun) nothing changed (yet). |
|
I tested it on ipq4019 (chateau 12) and it still works fine. |
|
Maybe related to openwrt#13166 ? |
include/image-commands.mk
Outdated
| endef | ||
|
|
||
| define Build/kernel-pack-npk | ||
| sh -c 'source $(STAGING_DIR_HOST)/share/npkpy-venv/bin/activate; python $(STAGING_DIR_HOST)/share/npkpy-venv/bin/pack_npk_kernel.py --kernel $@ --output $@.npk' |
There was a problem hiding this comment.
I tried this locally and had an issue with source. I think it should be . (a dot).
tools/npkpy/Makefile
Outdated
|
|
||
| define Host/Compile | ||
| python -m venv $(STAGING_DIR_HOST)/share/npkpy-venv | ||
| sh -c 'source $(STAGING_DIR_HOST)/share/npkpy-venv/bin/activate; pip install --editable $(HOST_BUILD_DIR)' |
|
@john-tho any plans to resume the work on routerboot v7 ? |
|
npkpy seems to only use standard python libs, do we really need venv or could we just use |
|
@john-tho just rebased on top of main, switched to yafut + use |
Use OpenWrt's lzma loader for initramfs image Due to mips kernel self extractor inability to relocate, and RouterBoot on 760igs refusing to netboot an ELF with: Entry point address: 0x80b91000 or greater: 0x80b81000 and below okay. Note that this is only a bootloader ELF entry point limitation, a 50MiB Linux + initramfs vmlinux will boot fine on 760igs. With this lzma loader, netboot will occasionally freeze after decompressing the kernel, but before starting vmlinux. It was considered that an occasional netboot freeze was simpler to workaround than an image that refuses to boot unless minimized. Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
Adjust the YAFFS file path written depending on the sysupgrade filename. Default to kernel (for ELF), switch to bootimage (for NPK) if image name has v7. Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
RouterBOOT v7 for NOR devices does not support the historic yaffs "kernel" ELF boot method. Generate a compatible kernel Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
RouterBOOT v7 for NOR devices does not support the historic yaffs "kernel" ELF boot method. Generate a compatible kernel Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
RouterBOOT v7 for NOR devices does not support the historic yaffs "kernel" ELF boot method. Generate a compatible kernel Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
john-tho
force-pushed
the
routerboot-v7
branch
from
fd635d8 to
ab83ff5
Compare
|
@john-tho how can we help get this into OpenWrt ? Haven't tested with the CI docker container, but using |
|
What's up with this PR? And why does it want to merge into the fork rather than upstream? I don't need this yet, but just noticed the issue with RouterBOOT v7 in the wiki. As there apparently is a solution, I'd like to see this in OpenWRT before it hits my manufacturing with some future delivery of routers. I'm gonna go into testing and wait for a reaction, but would create my own PR at some point if I get none. |
6 participants
Generate a sysupgrade flash image compatible with RouterBOOT v7
Pack kernel into NPK file container, into
bootimage, in a yaffs filesystem.As-is, would require python-venv on the buildbots
Would want to merge the npk-py changes into upstream npk-py for review