#
✕ nick:tmlind
#asahi · 2021-11-16 08:33
tmlindi heard apple uses linux internally for new hardware bring up or something like that
#asahi · 2021-11-16 08:32
tmlindyeah what a pity if they cannot really participate, oh well
#asahi · 2021-11-16 08:22
tmlindheh wondering why no upstream patches from corellium.. maybe because of strange directory paths in strings corellium.macho | grep home
#asahi · 2021-11-16 08:01
tmlindfun for years to come!
#asahi · 2021-11-16 07:59
tmlindlet's see what felipe suggests, has he commented on the related patches?
#asahi · 2021-11-16 07:58
tmlindyeah
#asahi · 2021-11-16 07:57
tmlindthat's probably because some read/write to the phy already was done at that point..
#asahi · 2021-11-16 07:56
tmlindi'm allergic to usb nowadays :p
#asahi · 2021-11-16 07:56
tmlindthe right person to comment on this is really felipe on the mailing lists, he might have some better ideas
#asahi · 2021-11-16 07:55
tmlindanyways, this all can be dealt with later too, just smells bad
#asahi · 2021-11-16 07:54
tmlindyeah sounds hacky
#asahi · 2021-11-16 07:54
tmlindwell the whole dwc3 probably hangs trying to read/write from the phy :)
#asahi · 2021-11-16 07:53
tmlindyeah to me it sounds that also a phy driver is needed, and after the phy reset, dwc3 needs to reinit the ulpi/utmi whatever data connection to the phy
#asahi · 2021-11-16 07:50
tmlindit should be likely be handled by drivers/phy, then the phy driver notifies dwc3 in a standard way
#asahi · 2021-11-16 07:49
tmlindas long as there's some interrupt..
#asahi · 2021-11-16 07:49
tmlindit should be possible to deal with the repeater and the phy with a custom phy driver
#asahi · 2021-11-16 07:48
tmlindis the repeater interrupt wired somewhere to a gpio line on the soc?
#asahi · 2021-11-16 07:48
tmlindno, not dwc2 for sure
#asahi · 2021-11-16 07:47
tmlindout of the usb hardware out there, dwc3 is quite sane actually
#asahi · 2021-11-16 07:47
tmlindi'm still stuck dealing with crappy usb hardware too :)
#asahi · 2021-11-16 07:46
tmlindi had my share of usb already 15 years ago
#asahi · 2021-11-16 07:46
tmlindyeah probably read/write to the phy hangs dwc3
#asahi · 2021-11-16 07:45
tmlindyeah sounds buggy :)
#asahi · 2021-11-16 07:45
tmlindto me it sounds that dwc3 can hang if the link to phy is misconfigured after repeater reset
#asahi · 2021-11-16 07:44
tmlindprobably the issue is re-establishing the communication from dwc3 to the phy after the repeater reset
#asahi · 2021-11-16 07:43
tmlindi doubt that's the right fix though
#asahi · 2021-11-16 07:43
tmlindi doubt that's the right fix though
#asahi · 2021-11-16 07:39
tmlindjannau: thanks for the m1-keyboard link
#asahi · 2021-11-16 07:38
tmlindjannau: sounds like dwc3 should just need to reinit the phy connection over ulpi/utmi whatever it might be after the repeater reset, i doubt dwc3 needs a reset
#asahi · 2021-11-16 06:03
tmlindhmm so is the macbook spi keyboard already working then? maybe i can attempt to upgrade then with some usb wlan dongle..
#asahi · 2021-11-16 05:40
tmlindthis still with the old corellium hacked kernel, can't quite yet upgrade :)
#asahi · 2021-11-16 05:37
tmlindfyi looks like hotplug of devices works with usb-c to usb-a adapter cable kept plugged in, this sounds like some unhandled interrupt for some usb-c related pin in the phy driver maybe?
#asahi · 2021-05-19 07:22
tmlindok so not going to be very usable as a chroot build box :)
#asahi · 2021-05-19 07:21
tmlindyeah so it seems comparing ldr for example that lists 64-bit and 32-bit on the page above, which seems to translate to the width as listed for ldr at https://developer.arm.com/documentation/102374/0101/Loads-and-stores---size
#asahi · 2021-05-19 07:18
tmlindmaybe the 32-bit instructions on the page above just mean the load size with a32 missing, not sure
#asahi · 2021-05-19 07:15
tmlindbut maybe i'm missing something and those are not a32 instructions..
#asahi · 2021-05-19 07:10
tmlindhmm there sure are tons of 32-bit instructions listed.. seems like kvm should be able to use them? see https://dougallj.github.io/applecpu/firestorm-int.html
#asahi · 2021-05-19 07:00
tmlindbut aren't the arm 32-bit instructions still there, no?
#asahi · 2021-05-19 06:19
tmlindor some kind of kvm setup?
#asahi · 2021-05-19 06:12
tmlindjust wondering.. so is CONFIG_COMPAT supposed to work on m1 for 32-bit chroot environment?
#asahi · 2021-05-05 07:22
tmlindfyi, there's also kexecboot that is a much simpler solution for folks needing a kexec gui
#asahi · 2021-04-21 15:36
tmlindsounds good to me
#asahi · 2021-04-21 13:12
tmlindyeah a proper driver for using some generic framework would be always better, in any case syscon is documented at Documentation/devicetree/bindings/mfd/syscon.yaml
#asahi · 2021-04-21 13:08
tmlinddepending on what all the nvram is used for and assuming it's on some separate controller, syscon might be usable in the simple cases for handling the nvram. but only if no other real framework is around to deal with it i'd say :)
#asahi · 2021-04-21 13:06
tmlindprobably the wlan nvram mac address should be handled by a separate driver and the wlan driver could then ask for it?
#asahi · 2021-04-12 13:03
tmlindthanks for the link
#asahi · 2021-04-12 12:30
tmlindmarcan: yeah the "raw data" view in the m1.json link above is handy though :)
#asahi · 2021-04-12 11:48
tmlindok
#asahi · 2021-04-12 11:46
tmlindhmm maybe that was actually u-boot limitation, not sure
#asahi · 2021-04-12 11:45
tmlindfyi, i recall local-mac-address also depends on having ethernet aliases to work properly, might be worht checking if that still is the case

plus ›