<hurricos>
specifically they mentioned backporting two patches, didn't quite understand what they meant
<hurricos>
Not sure who else to ping here, it's a must-have for 22.03, without which current WiFi config breaks for all mpc85xx users :p
dangole has quit [Ping timeout: 480 seconds]
<Spiwocoal>
it seems the source url for xxd is down, while running 'make download' it gets stuck trying to download the files for xxd, and I checked the url on my browser and it seems to be down, anyone else report this to be the case? or is it just me?
<dwfreed>
though changing cba to eecs would probably work better
<Spiwocoal>
nope, still not working here, but thankfully the wayback machine had the tarball archived
<dwfreed>
it's also going to be on distro mirrors
<dwfreed>
eg gentoo
mrkiko has quit [Remote host closed the connection]
schwicht has joined #openwrt-devel
mrkiko has joined #openwrt-devel
dlg has quit [Ping timeout: 480 seconds]
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
danitool has quit [Ping timeout: 480 seconds]
<mangix>
hurricos: he's pepes here
Spiwocoal has quit [Remote host closed the connection]
rsalvaterra has joined #openwrt-devel
ptudor_ has joined #openwrt-devel
ptudor has quit [Ping timeout: 480 seconds]
rsalvaterra_ has quit [Ping timeout: 480 seconds]
cmonroe_ has joined #openwrt-devel
rsalvaterra_ has joined #openwrt-devel
rsalvaterra_ is now known as rsalvaterra
dlg has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
<ynezz>
that problematic download of xxd is reported in #10555, perhaps we should consider reverting back to 2b94aac7a128 ? although downloading complete Vim tarball just for xxd seems like overkill
<ynezz>
maybe we should consider moving that little utility as a project to git.openwrt.org ?
<ynezz>
or bite the bullet and add the small source to the tools, but it's probably going to influence the CVE handling/scaning etc.
<ynezz>
another question is, if that xxd package needs to be always built, as it seems that only 2 targets bcm4908 and mediatek needs that for u-boot
<ynezz>
https://github.com/gregkh/xxdi "Perl script that implements vim's 'xxd -i' mode so that packages do not have to use all of vim just to get this functionality. "
<mangix>
ynezz: sounds better
<ynezz>
./xxdi.pl -> Can't locate File/Slurp.pm in @INC (you may need to install the File::Slurp module)
<ynezz>
:)
<mangix>
just add to include/prereq-build.mk
<pepes>
Mangix: Yeah, I should find some better nickname. :-D Pepe is too common and it was occupied here on oftc already
<pepes>
hurricos: I don't have any device, which you mentioned, but I do have CZ.NIC Turris 1.0 and Turris 1.1, which are using Freescale P2020. Not yet supported within OpenWrt. :-( Pali is working on improving mpc85xx support in U-boot and Linux kernel.
<f00b4r0>
i don't know if the plan is for another rc or a .0, but if the former, maybe we should include https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f1c9afd801380a05a91d979b475c76cc0a67caae - it's a big performance benefit for the affected devices
goliath has joined #openwrt-devel
<f00b4r0>
nbd: got it I'll check it out. re build deps on regular linux: shouldn't the build use the system libraries instead of embedding its own? (from a maintenance/security pov)
Tapper1 has joined #openwrt-devel
Tapper has quit [Read error: Connection reset by peer]
Piraty has quit [Remote host closed the connection]
<ynezz>
probably just need to add some underscores here and there to make it `xxd -i` compat
<nbd>
f00b4r0: this is mostly for testing anyway. at some point there should be a properly packaged version of unetd for linux distros
<nbd>
f00b4r0: and that one should use the system libraries
srslypascal is now known as Guest1573
srslypascal has joined #openwrt-devel
robimarko has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
MaxS0niX has joined #openwrt-devel
Guest1573 has quit [Ping timeout: 480 seconds]
MaxSoniX has quit [Ping timeout: 480 seconds]
<stintel>
does uhttpd support HTTP PUT?
<jow>
stintel: nope
<jow>
stintel: or rater not natively. It understands the PUT HTTP verb and passes it through to a cgi, ucode or Lua handler
<stintel>
k, just looking for potential alternative for adding all my OpenWrt devices in .ssh/config with scp instead of sftp
<dwfreed>
install the sftp server package?
<stintel>
running out of space
<jow>
dwfreed: openssh-sft-server used to be a tiny, few KB executable
<oliv3r[m][m]>
Hey guys, I'm trying to get the cable-test (VCT) to work on an ar8327; however I'm only getting junk. According to the datasheet, the VCT registers are in the 'custom vendor' space of the standard MII registers (0x16 and 0x1c). Reading/writing/using those just produces junk that doesn't make sense. Reading the standard registers seems to be okay however (MII_PHYSID[12] for example). Anybody have any idea what I could be looking at? I
robimarko_ has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
rua has joined #openwrt-devel
schwicht has joined #openwrt-devel
robimarko has quit [Ping timeout: 480 seconds]
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<f00b4r0>
stintel: now there's one extra feature that I wish the M300 had to make it absolutely perfect: an SFP cage. Then I could use it as a solo FTTH router without the need for an external ONT :)
<stintel>
but it would be incompatible with my HA setup ;)
<f00b4r0>
I'm not saying the SFP cage should replace one of the ports ;)
<stintel>
I'd rather plug the fiber into my switch with redundant PSU then at least
<f00b4r0>
ah, you have fancy toys ;)
<stintel>
I do, blame covid :P
<stintel>
I went a bit nuts during lockdowns
<f00b4r0>
lol, a serious case of GAS maybe? ;)
<stintel>
GAS?
<f00b4r0>
Gear Acquisition Syndrome
<stintel>
:D
<stintel>
probably
<f00b4r0>
;)
<stintel>
meanwhile I have 6 nRF5480 to play with thread
<f00b4r0>
oh right since you mentioned that I wanted to take a look.
<stintel>
and considering ordering another RAK5146 LoRa GW :P
<f00b4r0>
the nRF modules are very low power right, much lower than the typical ESP ones?
<stintel>
haven't measured tbh
<stintel>
actually don't have USB power measurement equipment
<stintel>
I should sort that
<stintel>
oops, another case of GAS? :p
<f00b4r0>
lol
<f00b4r0>
I need to find a device that can communicate wirelessly over relatively long distances in a 125mW enveloppe, which is... very low. For $technical_reasons related to French energy meters specs :)
<stintel>
yeah thread won't be of help there, unless you can plug in one of those things every so many meters in the path
<f00b4r0>
ah ok
<stintel>
thread is mesh
<stintel>
and LoRa ... I didn't manage to receive the LHT52 in the basement with the RAK5146 on the 6th floor
<f00b4r0>
oh, similar to Zigbee then
<stintel>
but that's many walls / ceilings
<stintel>
yes, like zigbee and z-wave, on top of 802.15.4
<stintel>
iiuc
<f00b4r0>
ok
<stintel>
so now I'm considering getting a high gain antenna for the gateway, and/or a sensor with external antenna
rua has quit [Ping timeout: 480 seconds]
<f00b4r0>
definitely GAS ;)
<stintel>
most likely
<stintel>
> Generally, it can penetrate about 7 or 8 walls, but the ability to penetrate walls is also affected by external factors, such as wall thickness, cement steel material, weather environment, etc.