<gamiee>
Kreyren: the WOL needs to be supported by RGMII PHY, and the PHY needs to send an interrupt (for eg. GPIO) to wake up A64
<Jookia>
how long should i wait to make sure my activation email has bounced?
<KREYREN_oftc>
gamiee, i know thus why am i askin for something alike WOL as the A64 doesn't seem to have it
<KREYREN_oftc>
gamiee, or like can you recommend something i can add on my PCB that will do the thing?
<gamiee>
It is not A64 dependent
<gamiee>
A64 have GPIO interrupts, the thing is, if the PHY supports it, and if according pin from PHY is connected to GPIO on A64, which have interrupt to wake SoC
<Jookia>
i've finished reverse engineering the lichee panel 86's BSP so you can rebuild the allwinner bootloader+kernel from source and run it :)
<Jookia>
so i want to add it to the page
<gamiee>
Jookia: oh nice!
<gamiee>
About emails, we should ping one person I forgot name
<gamiee>
by sending WOL packet to the PHY. Or maybe it is needed to enabled in device tree (if it is implemented in PHY at all). But take my responses with reserve, as I don't have full insight and I can be wrong.
<KREYREN_oftc>
github.com/OLIMEX/DIY-laptop well take a look :p
* KREYREN_oftc
also has no idea how to send the WOL packet
<gamiee>
It's not about datasheet right now, but how the WL_HOST_WAKE works in PHY side.... what I don't know.
<KREYREN_oftc>
@_@
<gamiee>
Also, why are you asking about how make Wake on LAN working on Teres, when you don't know how to send it at all? TL;DR, find application for that on net, put mac address, IP (if it is not withing your network, don't forget about port forwarding) and send WOL magic packet via that app.
<gamiee>
in busybox, there is handy ether-wake
<gamiee>
command
<KREYREN_oftc>
gamiee, bcs i have no idea how does this thing work on teres
<KREYREN_oftc>
end goal is avoiding getting up to wake up the system
<gamiee>
The process of wake on lan is the same as on classical PC, it is magic packet sent to the PHY.
evgeny_boger has joined #linux-sunxi
<KREYREN_oftc>
installed `wol` and doing `wol MAC_ADDRESS` which doesn't work and the device doesn't show as connected in the router
<gamiee>
are you sending it within same LAN network as your Teres is?
<KREYREN_oftc>
ye
<KREYREN_oftc>
i am SSH-ing over LAN
<gamiee>
Hmm, another question is, if teres is powering PHY chip when it's on sleep. I really don't know, so as I said upper, please wait for other folks which knows more.
<Jookia>
that doesn't necessarily mean it will wake the host on lan, just that it will wake the host
<Jookia>
linux and the firmware would have to agree to only wake it on lan
<KREYREN_oftc>
what's the difference
<Jookia>
it might wake the system on every packet or something like that
<KREYREN_oftc>
so it is possible to make it wake up somehow? i can change the OS if needs be
<KREYREN_oftc>
*is it
<Jookia>
i don't know. the firmware controls that
<KREYREN_oftc>
like i can change the PCB too if needs be
<Jookia>
you could try doing 'iw wlan0 wowlan enable' in linux and see what happens but that's about it i think
<Jookia>
looking at the driver it seems wowlan isn't supported for rtl8723b in mainline linux
<KREYREN_oftc>
Jookia, that's syntax err
<KREYREN_oftc>
`iw phy wlan0 wowlan enable` ?
<KREYREN_oftc>
You can omit the 'phy' or 'dev' if the identification is unique,
<KREYREN_oftc>
e.g. "iw wlan0 info" or "iw phy0 info". (Don't when scripting.)
<KREYREN_oftc>
though
<Jookia>
i dunno
<Jookia>
your best bet would probably to use a wireless card that does support wake on lan or something else to wake the device
<KREYREN_oftc>
the PCB is designed for some atheron chip it has this one on a daugher board with pinning to match the atheron chip bcs the chip is short on supply
<Jookia>
you want to look for a driver+chip that supports wake on lan
<Jookia>
alternatively you could probably hack something up yourself if you want to add a microcontroller or something
<KREYREN_oftc>
what controller would you recommend? i can jumper wire it
<Jookia>
not sure, i haven't done a project like that. i would imagine you could set up an esp wifi chip and make its entire job be to ping your computer when it gets a packet or something. it would require writing firmware and stuff though. did you mean atheros chip?
<KREYREN_oftc>
ye atheros chip
<KREYREN_oftc>
didn't figure out which one is compatible yet though
* karlp
can't think of an atheros part that's pin compatible with rtl8723xs.
<karlp>
I suspect that part was EOL before the A64 laptop design was even started though unfortunately.
<karlp>
it does suck, there's _very_ few options for available, functional, wifi4 level modules.
<KREYREN_oftc>
like the kernel driver is getting updates
<KREYREN_oftc>
O.o
<KREYREN_oftc>
ye thus why teres has that annoying daugher board there
<karlp>
ath9k was loved and adored, but yeah, good luck finding parts for it these days.
<karlp>
we're meant to cross our fingers and have faith that wifi6 iot class hardware will save the day.
<karlp>
I'm not entirely convinced of that yet :|
<gamiee>
karlp: wifi6 iot class will never not help us. NDAs are NDAs
<gamiee>
Even if there is some RE effort, until it will be done, more other chips will be released, and focus will be split.
<karlp>
gamiee: that's my expectation as well, but wifi6 iot is what I'm being _sold_ is going to be the answer :|
<gamiee>
the worst thing is, that it is split to two parts, host driver, and device driver. If device driver is shit, you can do anything at host. if device driver is good, but host driver sucks, still, you need to rework whole driver to get it to mainlining state.
<gamiee>
and since wifi is quite complex thing, there is not enough people which will know how to do this.
<gamiee>
karlp: yeah. I see more promise in OpenWifi
<KREYREN_oftc>
hmm guess i will take the gerber 3D render screenshot in GIMP put a what each lane does and go ask on some libre mailing list for a compatible wifi chip >_<
<KREYREN_oftc>
or like daughter-boarding some other chip if needs be
<KREYREN_oftc>
or making new PCB
<KREYREN_oftc>
\>_<
jernej has quit [Ping timeout: 480 seconds]
<karlp>
are you prepared to give up bluetooth?
<karlp>
you'll have more options that way at least.