<mrnuke_>
svanheule: in your switch_port LED driver, I don't understand the need for "is_secondary" in the reg property. That's something the code should understand based on the port number. Adding that to devicetree is really confusing
<mrnuke_>
svanheule: I've had to go read the code to understand its meaning. If I were going from the documentation, I would put reg = <24 0 1>; for SFP LEDs, which is, of course, nonsensical on rtl838x
<mrnuke_>
svanheule: I would also suggest to make "rtl_hw_trigger" a list of text fields. Having an ad-hoc value deosn't help much, unless the user is an expert navigator of https://svanheule.net/switches/led_control
Tapper has quit [Ping timeout: 480 seconds]
schwicht has joined #openwrt-devel
schwicht_ has quit [Read error: Connection reset by peer]
<mrnuke_>
svanheule: writing to rtl_hw_trigger, also seems to not change anything in "/sys/kernel/debug/rtl838x/led/" on rtl8380. Is this intentional ?
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<mrnuke_>
svanheule: I'm also confused on how to properly set led{0,1,2}_sw_p_en_ctrl, and led_mode_ctrl registers from the sysfs interface.
<mrnuke_>
svanheule: Tested-byL Yours truly, with the caveat that I was not able to get the hardware LED control to work
minimal has quit [Quit: Leaving]
schwicht_ has joined #openwrt-devel
schwicht has quit [Read error: Connection reset by peer]
rua has quit [Quit: Leaving.]
goliath has quit [Quit: SIGSEGV]
floof58 has quit [Quit: floof58]
csrf1 has joined #openwrt-devel
csrf has joined #openwrt-devel
floof58 has joined #openwrt-devel
csrf has quit [Remote host closed the connection]
csrf has joined #openwrt-devel
csrf1 has quit [Read error: Connection reset by peer]
csrf1 has joined #openwrt-devel
<mrnuke_>
svanheule: using 'linux,default-trigger = "realtek-switchport";' does not seem to change the boot-up value of led{0,1,2}_sw_p_en_ctrl
schwicht_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
valku has quit [Quit: valku]
<mrnuke_>
svanheule: the "led_glb_ctrl " also appears to be woefully wrong and confuses the LED controller
<mrnuke_>
For example, driver sets it at "0x2f39000f", whereas the default (that was previously working) is 0x2f396a3f
zatwai has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
zatwai has joined #openwrt-devel
ptudor has quit [Ping timeout: 480 seconds]
ptudor has joined #openwrt-devel
<Mangix>
Wonder if there's a way to configure cookie timeout for luci
<aiyion>
nvmd, will work through their guidelines, how hard can that be. Will come back later with proper questions.
<PaulFertser>
aiyion: is the flash desoldered from target board or are you using ISP? The target SoC might be influencing your operations.
<aiyion>
ISP for now. Will change that tomorrow, when I've got access to my soldering heat gun again :/
<aiyion>
But thanks for the hint.
<PaulFertser>
aiyion: if you have found target hardware reset line probably worth trying to tie it low.
<aiyion>
will do, thanks
<PaulFertser>
aiyion: I think for flashrom it's enough for you to specify correct erase sector size, then you can erase the whole flash, and then just flash the whole image. If your clock isn't too high it should just work.
<Borromini>
aiyion: i compared the datasheet for my chip with the ones already supported (as in: voltage etc) in flashrom and for mine it was just the packaging that seemed to differ. I might of course have gotten *very* lucky.
<Borromini>
PaulFertser: what's ISP?
<PaulFertser>
Borromini: in system programming
<Borromini>
ok so with a SOIC clamp e.g.?
indy has quit [Ping timeout: 480 seconds]
<PaulFertser>
Borromini: yes, and without disconnecting flash Vcc from the board (it's often easy enough to lift just one single pin off)
<Borromini>
ok :)
indy has joined #openwrt-devel
indy has quit [Ping timeout: 480 seconds]
indy has joined #openwrt-devel
<aiyion>
Borromini: If I get it right, evil twins are not that likely to encounter; so not 'very' lucky.
<aiyion>
eraseblocks match the c variant as far as I can tell.
<aiyion>
I'll create a patch for the chip when I'm done comparing the rest of the values to my datasheet.
<Borromini>
:)
<Namidairo>
i'd argue gigadevice are the evil twin, unless they're actually using their own jedec id now
indy has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
dangole_ has quit [Remote host closed the connection]
dangole_ has joined #openwrt-devel
bluew has joined #openwrt-devel
dangole_ has quit [Remote host closed the connection]
dangole_ has joined #openwrt-devel
srslypascal is now known as Guest3231
srslypascal has joined #openwrt-devel
dangole_ is now known as dangole
Tapper has quit [Ping timeout: 480 seconds]
Guest3231 has quit [Ping timeout: 480 seconds]
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Ping timeout: 480 seconds]
jlsalvador2 is now known as jlsalvador
Borromini has quit [Quit: Lost terminal]
robimarko has joined #openwrt-devel
valku has joined #openwrt-devel
<neggles>
Namidairo: they've been using their own jedec id for quite a while
schwicht has joined #openwrt-devel
MaxSoniX has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
indy has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
schwicht has quit [Read error: Connection reset by peer]
dangole_ has joined #openwrt-devel
schwicht has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
dangole_ has quit [Remote host closed the connection]
dangole_ has joined #openwrt-devel
soxrok2212 has quit [Read error: Connection reset by peer]
soxrok2212 has joined #openwrt-devel
<[Pokey]>
is it possible to gentle gentle persuady poke someone into glancing over my PR and maybe merging it
<[Pokey]>
I just want my device running main releases so I don't havr to fight kmods to install packages
dangole_ is now known as dangole
minimal has joined #openwrt-devel
gladiac has joined #openwrt-devel
<yolo>
how to log all packets that are rejected|dropped(i.e. they never got an ack or reply from the remote side), e.g. a device behind openwrt tried to send udp|tcp to a bad or non-existent IP to the cloud, can openwrt catch and log that request?
<yolo>
if it's a domain name, dnsmasq can log all NXDOMAIN for invalid requests, but I need a way to log invalid IP requests be it udp or tcp
robimarko has quit [Quit: Leaving]
swegener has quit [Quit: leaving]
schwicht has quit [Remote host closed the connection]
<jow>
dangole: we should discuss the ujail-by-default eventually
<jow>
define a policy fro script hooks, define a policy for uci managed flesystem paths vs. filesystme paths in native configs the init script setting up the jail might not be aware of etc.
GNUmoon has quit [Quit: Leaving]
bluew has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
bluew has joined #openwrt-devel
bluew has quit [Remote host closed the connection]
bluew has joined #openwrt-devel
bluew has quit [Remote host closed the connection]
bluew has joined #openwrt-devel
bluew has quit [Remote host closed the connection]
bluew has joined #openwrt-devel
csrf1 has quit [Remote host closed the connection]
csrf has quit [Remote host closed the connection]
csrf has joined #openwrt-devel
csrf1 has joined #openwrt-devel
bluew has quit [Remote host closed the connection]