<rsalvaterra>
If anyone's using lzo, what they really want is lzo-rle, as it provides better compression for the typical use case (zram).
eigma has quit [Server closed connection]
eigma has joined #openwrt-devel
johnf has quit [Server closed connection]
johnf has joined #openwrt-devel
hurricos has quit [Server closed connection]
hurricos has joined #openwrt-devel
ptudor_ has joined #openwrt-devel
ptudor__ has joined #openwrt-devel
ptudor has quit [Ping timeout: 480 seconds]
ptudor_ has quit [Ping timeout: 480 seconds]
kopijahe has joined #openwrt-devel
<jow>
rsalvaterra: looks sane to me
<jow>
rsalvaterra: in general I favor grouping kmods where itm akes sense
<jow>
not packaging every tiny helper .ko just for the sake of it
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<rsalvaterra>
jow: This situation is even more insidious. The lzo-rle module appears to be separate from lzo, but it effectively isn't. If you only load the lzo module, lzo-rle is also advertised as present, when it isn't. It's arguably a kernel problem, but it's there.
danitool has joined #openwrt-devel
<jow>
rsalvaterra: so lzo-rle clearly isn't standalone and it makes no sense to pacakge it separately
<jow>
and the overhead of the extra packaging might match the overhead of just sticking the extra .ko into the excisting zlo module
<jow>
*existing lzo kmod package
<rsalvaterra>
That was my reasoning. A 5 kiB difference isn't worth the hassle.
robimarko has joined #openwrt-devel
<rsalvaterra>
Alright, I'll shepherd this in, thanks.
tizbac has quit [Remote host closed the connection]
kopijahe has quit [Read error: Connection reset by peer]
kopijahe has joined #openwrt-devel
kopijahe has quit [Remote host closed the connection]
ptudor__ has quit [Ping timeout: 480 seconds]
kopijahe has joined #openwrt-devel
ptudor has joined #openwrt-devel
sauce has quit [Server closed connection]
sauce has joined #openwrt-devel
ptudor_ has joined #openwrt-devel
ptudor has quit [Ping timeout: 480 seconds]
kopijaheaseli has joined #openwrt-devel
agb has quit [Server closed connection]
agb has joined #openwrt-devel
kopijahe has quit [Ping timeout: 480 seconds]
ecloud has quit [Ping timeout: 480 seconds]
Misanthropos has quit [Ping timeout: 480 seconds]
kopijaheaseli has quit [Read error: Connection reset by peer]
ecloud has joined #openwrt-devel
eduardo010174 has joined #openwrt-devel
sorinello has quit [Quit: Leaving]
sorinello has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
<aiyion>
the wiki page does say the soc of the unifi ap pro is a ar9344 rev2. Mine says it contains a rev3. Can someone tell, whether thats wrong in the wiki or if there are more revisions out there, than the one in the wiki?
Darkmatter66 has left #openwrt-devel [#openwrt-devel]
Tapper has quit [Quit: Tapper]
rsalvaterra has quit [Server closed connection]
rsalvaterra has joined #openwrt-devel
ecloud has quit [Server closed connection]
ecloud has joined #openwrt-devel
eduardo010174 has quit [Server closed connection]
eduardo010174 has joined #openwrt-devel
Slimey has joined #openwrt-devel
Slimey_ has joined #openwrt-devel
Slimey has quit [Ping timeout: 480 seconds]
Slimey_ is now known as Slimey
Slimey has quit [Read error: Connection reset by peer]
goliath has quit [Quit: SIGSEGV]
Pepes has joined #openwrt-devel
ekathva_ has quit [Remote host closed the connection]
Guest2811 is now known as Rayyan
ekathva has joined #openwrt-devel
minimal has quit [Quit: Leaving]
eduardo010174 has quit [Quit: Leaving]
noltari has quit [Remote host closed the connection]
noltari has joined #openwrt-devel
Misanthropos has quit [Ping timeout: 480 seconds]
Misanthropos has joined #openwrt-devel
csharper2005_ has joined #openwrt-devel
<aiyion>
I just realized the device I want to mess with next has nand-flash. While I theoretically understand how these things wear down and have some bad-block paging, I'd appreciate not to need too deep into it to dump it.
<aiyion>
I really hope the serial console of this thing is open...
<aiyion>
I was looking for a nand pendant to spi dumping
<aiyion>
I watched through two DefCon talks on the matter an figured it has been done, but is likely not the next reasonable step looking at how the er10ßx has a serial console which could expose all sorts of easier ways.
robimarko_ has quit [Remote host closed the connection]
robimarko_ has joined #openwrt-devel
<robimarko_>
Well, the most viable way would be to use nanddump
<robimarko_>
Any other way pretty much requires a NAND programmer and a clamp or desoldering
<mangix>
anyone else get packet loss with flow offload enabled?
<aiyion>
I was just so used to dumping flash with a clamp before I touch anything else. I'll look at naddump tomorrow, thx robimarko_
<robimarko_>
aiyion: Me as well, but its only easy if we are talking about SPI-NOR
<robimarko_>
NAND is a whole new beast
<robimarko_>
Especially if its 1.8 or even 1.2V IO level
Grommish has joined #openwrt-devel
Grommish has quit [Read error: Connection reset by peer]
Grommish has joined #openwrt-devel
<xdarklight>
hauke: if you got some time in the next days, could you please boot https://github.com/xdarklight/openwrt/commits/lantiq-5.15 on one of your boards? I see messages like this: gswip 1e108000.switch: port 4 failed to add <LAN MAC address> vid 1 to fdb: -22
guidosarducci has quit [Remote host closed the connection]