<hurricos>
tmn505: Oh! OK. So IMAGE_SIZE represents the maximum size the image can occupy, yes?
<hurricos>
Is there any good documentation for the definition variables for each build target?
<hurricos>
I also want to make sure I am using the right variables to make sure builds fail if the initramfs is greater than 16MiB, too, not just the rootfs-less kernel
<hurricos>
since the kernel cannot run any code above 16MiB in physical memory until the right init has occurred
<hurricos>
either that or it refuses to copy it thta high :^)
<hurricos>
slh: I will dig it open and tell you :)
<svlobanov>
Hi. I have observed strange behaviour on armvirt-64 target (today's snapshot). ping shows very large time (~1580945ms). can someone please check ping output on real aarch64 devices? https://pastebin.com/LB9bzXmR
<hurricos>
svlobanov: your virtualization host is qemu?
<hurricos>
I would worry about slirp
<hurricos>
if it is qemu, throw me your 'qemu-system-aarch64' command please :D
svlobanov has quit [Remote host closed the connection]
<tmn505>
hurricos: yes, the IMAGE_SIZE is max that can be occupied by the kernel+rootfs on the flash
paper_ has quit [Read error: Connection reset by peer]
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
hurricos1 has joined #openwrt-devel
hurricos has quit [Read error: Connection reset by peer]
Tapper has quit [Ping timeout: 480 seconds]
<neggles>
hurricos1: KERNEL_SIZE = size of kernel+initramfs, so would need to be 16384k - 256k for the prepended DTB = 16128k
<neggles>
also I believe it doesn’t need the “check-size” if IMAGE_SIZE and KERNEL_SIZE are set
<neggles>
and for some reason on the build I downloaded from your site, the LED controller doesn’t work
<neggles>
no lp5521 module
<neggles>
which is a kernel config / kernel builtin thing, it seems
<hurricos1>
lp5521?
<hurricos1>
wait, did I somehow drop that?
<hurricos1>
oh no
<hurricos1>
it might have just gotten dropped.
hurricos1 is now known as hurricos
<hurricos>
... in the -> 5.10 migration :^)
<hurricos>
now I'm confused, though.
<Grommish>
My rust-lang Host/ stuff is fine, Build/ is borked (for generating rustc/cargo for on-device).. Can I mark it as BROKEN for the Package and still have Host/ called as normal?
<Grommish>
Or does it hide the entire thing
<hurricos>
neggles: CONFIG_LEDS_LP5521 is enabled, and yet ...
<hurricos>
there's something wrong with the config-default under p1020, perhaps
<neggles>
hurricos: it works on my builds 🤷♂️
<hurricos>
oh no
<neggles>
did they change something in .88
<hurricos>
my builds are fucked
<hurricos>
that would explain why my gpio isn't working
<hurricos>
on ap3825i
<neggles>
I’m on .87 still
<hurricos>
potentially
<hurricos>
err
<neggles>
but, maybe?
<hurricos>
how exactly are yo ubuilding?
<hurricos>
Could you pastebin your diffconfig?
<neggles>
build system, I just haven’t rebased since kernel patch ver was bumped