schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sorinello>
nitro
cbeznea1 has quit [Quit: Leaving.]
cbeznea has joined #openwrt-devel
<Harm_>
MaxSoniX: Re: similar device. Nice find!
<MaxSoniX>
It’s a pity that providers don’t have firmware on the site or, for example, a person with such a device would be good among us)
<Harm_>
yeah, the WG420223-TC is exactly the same case as I have (except for the Wi-Fi text on the front)
<Harm_>
MaxSoniX: how should I name my device in OpenWRT? WG420223-99 or just WG420223?
<Harm_>
I also see a distinction between model and version
<MaxSoniX>
Harm_: I don't know for sure, with my devices I'm also in doubt. It would be nice if someone more experienced could enlighten us on this issue. The only good thing would be the mention of both the names of the OEM manufacturer and the trade name, which would make it easier to look for similar devices later.
<MaxSoniX>
Or vice versa, swap the names of trade and OEM
<Harm_>
Nice, I'll ask that in my forum post
<aiyion>
in OpenWrts Makefiles there are "SUPPORTED_DEVICES" and there are "BOARD_NAME"s. At some points either of them is used, default to boardname if it exists, and use the devicename otherwise.
<aiyion>
Is there some rule that allows the translation of a device descriptor with a comma to a boardname with the underscore??
<aiyion>
(Can I assume the BOARD_NAME of a device with a comma between vendor and model is the same string but with an underscore instead?
torv_ is now known as torv
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
Borromini has joined #openwrt-devel
<Borromini>
Hey guys. What's Ansuel's IRC handle? I forgot.
<hurricos>
mrnuke_ I *meant* a scope at the time. A friend of our hackerspace has a very high-end one
<hurricos>
a scope is more sensitive than a logic analyzer ;)
<mrnuke_>
hurricos: You could use a beat-up DS1054G, and it would tell you all you need to know :)
<hurricos>
Right.
<mrnuke_>
I am curious if the MCU sends a break condition (0x00 packet with framing error) whenever it craps out. I think we should see that as a 0x00 input byte, but I haven't checked
<hauke>
jow: making wolfssl nonshared cuaes problems with image builder.
<hauke>
wolfssl was upgraded after the 22.03.0-rc5 and libustream-ssl depends on the new version, but imagebuilder still uses the non shared version
<hauke>
and this fails
Gaspare has quit [Quit: Gaspare]
Gaspare has joined #openwrt-devel
Borromini has joined #openwrt-devel
Borromini has quit []
indy_ has quit [Remote host closed the connection]
Grommish has joined #openwrt-devel
indy has joined #openwrt-devel
Grommish has quit [Read error: Connection reset by peer]
<hurricos>
stintel: The registers are TCR and TSR, they're machine-specific registers. I don't see any memory mapping for these registers either, unfortunately
<hurricos>
I forgot to bring my BSAP3040 with me to the Lab -- lots of people to see today -- but I'll bring it in to try out the BDI against it next time around.
<hurricos>
I'll also go check whether the BDI can even be configured to interact with the T-series QorIQ stuff without different firmware.
<hurricos>
the bdiGDB configuration is definitely different between mpc85xx and P3/P4/P5/T1/T2/T4
Grommish has joined #openwrt-devel
cmonroe has joined #openwrt-devel
Grommish has quit [Read error: Connection reset by peer]
<hurricos>
I have the BDI firmware for P3/P4/P5, but none for T-series :\
<hurricos>
Might work still. P3/P4/P5 and T-series are basically the same, it just won't be able to identify the CPU
<hurricos>
Comes down to finding a copy of b20qp4gd.xxx (I have xxx=103) that's new enough to read the registers to understand the CPU. I think this should work :P
MaxSoniX has quit [Quit: Konversation terminated!]