xback has quit [Remote host closed the connection]
xback has joined #openwrt-devel
<norris>
who can edit the wiki hwdata fields? "Supported Current Rel" / "Current official release" supports the new 23.05.0 release tag, but "Supported Since Rel" does not
<PaulFertser>
hauke: hello. The sha256sums is signed with "OpenWrt 23.05 release signature" key 6D9278A33A9AB3146262DCECF93525A88B699029 but it doesn't seem to be present in https://git.openwrt.org/keyring.git
<dwfreed>
that's the snapshot key
<dwfreed>
it probably shouldn't be using the snapshot key
<f00b4r0>
xback: re rb912 cpu clock, I really doubt it's actually running at 960MHz. In all likelyhood, that's a computation error from the kernel, which has no control of its own over the CPU freq
<f00b4r0>
xback: at 960Mhz I'd expect kittens to die and the device to vaporize, tbh. No way it would be stable.
<hauke>
PaulFertser: thanks for pointing this out
<hauke>
ynezz: could you please have a look at the signing keys for the 23.05 release
<hauke>
I think you wanted to change it sometime in the rc process
<PaulFertser>
hauke: thank you for caring and congratulations on the release :)
Daanct12 has quit [Quit: WeeChat 4.0.5]
raenye has joined #openwrt-devel
<raenye>
rmilecki: I verified that lan1-4 RJ45 ports indeed match the switch ports in Linksys EA9200
<raenye>
rmilecki: about the GPIO patch, I'm wondering whether I should also add frequency limitations on the two 5 GHz bands, similar to Netgear R8000 DT
<raenye>
iwinfo radio0 scan finds mostly networks on channels 36-48, but also 52, 56 (and also sees radio2's AP on channel 149)
<raenye>
iwinfo radio2 scan sees channel 112 (and radio0's AP on channel 48)
<raenye>
AFAICT for R8000 it's the other way around (high channels on phy0, low channels of phy2)
<dermoth>
Hey there... have the developers ever considered a torrent to distribute openwrt? I always mirror all packages for the versions I use so if I encounter any issue while upgrading I can access them while my router is down or broken.... So I though at least I could contribute back some of the bandwidth.
<slh>
what would that really improve? the individual files are on average <10 MB for the images and a few dozen KB for the packages, the computational overhead to cover that (and still sort it back into a sensible directory structure) sound massive
<slh>
also keep in mind that the package(s feeds) are not locked and are getting updates constantly
Borromini has quit [Quit: Lost terminal]
<dermoth>
Humm... I'm definitively downloading more than that.. these include 3 images on 2-3 different architectures:
<dermoth>
17.01.2 1.5G
<dermoth>
18.06.1 2.3G
<slh>
I'm talking about the individual files
<dermoth>
21.02.3 4.2G
<dermoth>
well one torrent would have all files of the mirror of course (you can select what to download within it)
<slh>
again, the packages aren't locked, they change - and if you download all images... why? even if you really have a dozen different devices, downloading only what you actually need makes more sense
<dermoth>
My mirror script download only the required images, but all packages ot be on the safe side
<dermoth>
all package for the arch
kwz has quit [Ping timeout: 480 seconds]
raenye has joined #openwrt-devel
<dermoth>
tbh, if you don't care of the bandwidth, I don't mind either - less work, my script has been working nicely since 17.01.2 :)
<dermoth>
I switched to rsync at one point when it became available, at first it was using wget!
<dermoth>
I agree it would take something to automatically update the torrent file... then probably would have to find a cli torrent tool as I would definitively not hand-pick the files in a gui app :). I added 23.05.0 to it and it's happily mirroring it now: )
<dermoth>
I use a combination of targets, arches and patterns to pick just the images for my HW
raenye has quit [Read error: Connection reset by peer]
swalker_ has quit [Remote host closed the connection]