00:02
<
youmukonpaku1337 >
ok yea i should be able to
00:17
apritzel has quit [Ping timeout: 480 seconds]
00:52
stipa is now known as Guest1823
00:52
stipa has joined #linux-sunxi
00:58
Guest1823 has quit [Ping timeout: 480 seconds]
01:08
ungeskriptet0 has joined #linux-sunxi
01:13
ungeskriptet has quit [Ping timeout: 480 seconds]
01:24
stipa is now known as Guest1828
01:24
Guest1828 has quit [Read error: Connection reset by peer]
01:25
stipa has joined #linux-sunxi
02:09
youmukon1 has joined #linux-sunxi
02:09
youmukonpaku1337 is now known as Guest1834
02:09
youmukon1 is now known as youmukonpaku1337
02:11
Guest1834 has quit [Ping timeout: 480 seconds]
02:47
stipa is now known as Guest1838
02:47
stipa has joined #linux-sunxi
02:48
Guest1838 has quit [Ping timeout: 480 seconds]
03:05
Daanct12 has joined #linux-sunxi
03:55
hexdump01 has joined #linux-sunxi
03:57
hexdump0815 has quit [Ping timeout: 480 seconds]
03:58
junari has joined #linux-sunxi
04:20
junari has quit [Ping timeout: 480 seconds]
04:29
anarsoul has quit [Ping timeout: 480 seconds]
04:44
rubberduck has joined #linux-sunxi
04:57
stipa has quit [Ping timeout: 480 seconds]
05:06
stipa has joined #linux-sunxi
05:09
anarsoul has joined #linux-sunxi
05:14
JohnDoe_71Rus has joined #linux-sunxi
05:23
youmukonpaku1337 has quit [Quit: WeeChat 4.0.4]
05:54
youmukonpaku1337 has joined #linux-sunxi
06:24
apritzel has joined #linux-sunxi
06:27
jelly-hme has quit [Ping timeout: 480 seconds]
06:34
apritzel has quit [Ping timeout: 480 seconds]
07:01
warpme has joined #linux-sunxi
07:10
youmukon1 has joined #linux-sunxi
07:10
youmukonpaku1337 has quit [Read error: Connection reset by peer]
07:23
jelly has joined #linux-sunxi
07:31
jelly has quit [Ping timeout: 480 seconds]
07:38
wasutton- has joined #linux-sunxi
07:41
youmukonpaku1337 has joined #linux-sunxi
07:42
wasutton3 has quit [Ping timeout: 480 seconds]
07:45
youmukon1 has quit [Read error: Connection reset by peer]
07:49
warpme has joined #linux-sunxi
07:52
youmukon1 has joined #linux-sunxi
07:53
Guest1708 has quit [Read error: Connection reset by peer]
07:53
DarkNeutrino has joined #linux-sunxi
07:53
mripard has joined #linux-sunxi
07:56
mripard has quit []
07:57
youmukonpaku1337 has quit [Ping timeout: 480 seconds]
07:57
mripard has joined #linux-sunxi
08:09
DarkNeutrino has quit [Ping timeout: 480 seconds]
08:09
DarkNeutrino has joined #linux-sunxi
08:13
apritzel has joined #linux-sunxi
08:21
youmukon1 has quit [Remote host closed the connection]
08:22
youmukonpaku1337 has joined #linux-sunxi
08:24
warpme has joined #linux-sunxi
08:28
DarkNeutrino is now known as Guest1865
08:28
DarkNeutrino has joined #linux-sunxi
08:30
youmukonpaku1337 has quit [Remote host closed the connection]
08:30
youmukonpaku1337 has joined #linux-sunxi
08:38
jelly has joined #linux-sunxi
08:42
warpme has quit [Read error: Connection reset by peer]
08:43
warpme has joined #linux-sunxi
08:43
youmukonpaku1337 has quit [Remote host closed the connection]
08:44
youmukonpaku1337 has joined #linux-sunxi
08:45
jelly has quit [Read error: Connection reset by peer]
08:49
freemangordon has quit []
08:49
freemangordon has joined #linux-sunxi
09:04
kuba2k2 has joined #linux-sunxi
09:16
jelly has joined #linux-sunxi
10:10
harve-vite has joined #linux-sunxi
10:12
harve-vite has quit []
10:14
bauen1 has quit [Ping timeout: 480 seconds]
10:21
youmukonpaku1337 has quit [Remote host closed the connection]
10:21
youmukonpaku1337 has joined #linux-sunxi
10:50
warpme has joined #linux-sunxi
10:55
youmukonpaku1337 has quit [Remote host closed the connection]
10:55
youmukonpaku1337 has joined #linux-sunxi
11:20
youmukon1 has joined #linux-sunxi
11:23
youmukonpaku1337 has quit [Ping timeout: 480 seconds]
11:33
youmukon1 has quit [Remote host closed the connection]
11:33
youmukonpaku1337 has joined #linux-sunxi
11:47
youmukonpaku1337 has quit [Remote host closed the connection]
11:47
youmukonpaku1337 has joined #linux-sunxi
12:10
gsz has joined #linux-sunxi
12:13
indy_ is now known as indy
12:27
bauen1 has joined #linux-sunxi
12:31
youmukonpaku1337 has quit [Remote host closed the connection]
12:31
youmukonpaku1337 has joined #linux-sunxi
12:33
kuba2k2 has quit [Ping timeout: 480 seconds]
12:41
youmukonpaku1337 has quit [Remote host closed the connection]
12:42
youmukonpaku1337 has joined #linux-sunxi
12:56
kuba2k2 has joined #linux-sunxi
12:58
youmukonpaku1337 has quit [Remote host closed the connection]
12:59
youmukonpaku1337 has joined #linux-sunxi
13:05
Daanct12 has quit [Quit: WeeChat 4.0.4]
13:19
youmukonpaku1337 has quit [Remote host closed the connection]
13:19
youmukonpaku1337 has joined #linux-sunxi
13:23
JohnDoe_71Rus has quit []
13:30
youmukonpaku1337 has quit [Remote host closed the connection]
13:31
youmukonpaku1337 has joined #linux-sunxi
13:37
Danct12 has quit [Read error: Connection reset by peer]
14:20
youmukonpaku1337 has quit [Remote host closed the connection]
14:20
youmukonpaku1337 has joined #linux-sunxi
14:35
mripard has quit [Quit: mripard]
14:36
mripard has joined #linux-sunxi
14:39
JohnDoe_71Rus has joined #linux-sunxi
14:54
mripard has quit [Quit: mripard]
15:24
kuba2k2 has quit [Ping timeout: 480 seconds]
16:07
apritzel has quit [Ping timeout: 480 seconds]
16:52
Danct12 has joined #linux-sunxi
17:18
ftg has joined #linux-sunxi
17:33
anarsoul|2 has joined #linux-sunxi
17:34
anarsoul has quit [Read error: No route to host]
17:39
daschaos has quit [Remote host closed the connection]
17:41
daschaos has joined #linux-sunxi
17:48
warpme has joined #linux-sunxi
17:51
warpme has quit [Remote host closed the connection]
17:51
warpme has joined #linux-sunxi
18:18
warpme has joined #linux-sunxi
18:21
ungeskriptet0 has quit []
18:21
ungeskriptet0 has joined #linux-sunxi
18:27
bauen1 has quit [Ping timeout: 480 seconds]
18:48
gsz has quit [Ping timeout: 480 seconds]
19:08
apritzel has joined #linux-sunxi
19:24
JohnDoe_71Rus has quit []
19:36
warpme has joined #linux-sunxi
19:54
youmukonpaku1337 has quit [Remote host closed the connection]
19:55
youmukonpaku1337 has joined #linux-sunxi
20:03
bauen1 has joined #linux-sunxi
20:08
Guest1865 has quit [Read error: Connection reset by peer]
20:25
hexdump01 has quit []
20:25
hexdump0815 has joined #linux-sunxi
20:35
<
apritzel >
hexdump0815: mmh, interesting, thanks for the heads up, at least it's some extra data point to consider
20:48
youmukon1 has joined #linux-sunxi
20:53
youmukonpaku1337 has quit [Ping timeout: 480 seconds]
21:02
kuba2k2 has joined #linux-sunxi
21:02
<
jernej >
apritzel: do you have any issue with motorcomm PHY power sequence?
21:04
kuba2k2 has quit []
21:06
<
apritzel >
on the OrangePi Zero3? Or in general?
21:08
<
jernej >
However, I'm sure there is SW workaround/fix too
21:11
<
apritzel >
Does the OPi 3 LTS also use an YT8531?
21:11
<
apritzel >
the Motorcom datasheet says: "The YT8531(D) device requires only one external power supply: 3.3 V."
21:11
<
apritzel >
so I don't think there is any particular sequence needed
21:12
<
apritzel >
however the datasheet also says that one should keep RST low for at least 10ms after enabling power
21:13
stipa has quit [Ping timeout: 480 seconds]
21:13
<
apritzel >
I don't know from the top of my head if we take care of that, or if Linux would be, but U-Boot is spoiling this
21:13
<
apritzel >
I tried without U-Boot Ethernet support, though, and there was no difference, IIRC
21:24
youmukon1 has quit [Read error: Connection reset by peer]
21:25
youmukonpaku1337 has joined #linux-sunxi
21:30
Halamix2_ has quit []
21:33
Halamix2 has joined #linux-sunxi
21:37
<
youmukonpaku1337 >
apritzel: so uh i am a complete idiot and the wifi interface was 12mbit
21:37
<
youmukonpaku1337 >
so shit was running horribly
21:37
<
youmukonpaku1337 >
i now need to use the main usb port as host
21:37
<
youmukonpaku1337 >
problem is
21:37
<
youmukonpaku1337 >
it does NOT work
21:38
<
youmukonpaku1337 >
i have dr_mode set to host in DT
21:41
<
jernej >
apritzel: it has YT8531C
21:42
jason123onirc has joined #linux-sunxi
21:43
<
jernej >
apritzel: I added reset delays longer than that, but I get occasional user report that it doesn't work from time to time, so not sure what I can do more
21:47
jason123santaonirc has quit [Ping timeout: 480 seconds]
21:50
<
youmukonpaku1337 >
megi: if possible, can you test forcing dr_mode=host on your device with a powered otg adapter? and see if it works
21:52
<
youmukonpaku1337 >
or is there a way to force usb2 on the wifi interface lol
21:54
<
apritzel >
youmukonpaku1337: I don't know any details, but the MUSB host mode is reported to have problems
21:54
<
youmukonpaku1337 >
oh
21:54
<
apritzel >
that's why Allwinner added a mux and a separate EHCI/OCHI host controller pair to later SoCs
21:55
<
youmukonpaku1337 >
i assume im screwed and stuck with ohci then?
21:55
<
youmukonpaku1337 >
:(
21:56
<
apritzel >
so with "Wifi interface" you mean the pins on the board that connect to the USB1 controller?
21:56
<
youmukonpaku1337 >
well the pins intended for the rtl8188eus
21:56
<
youmukonpaku1337 >
which seem to be connected to the ohci controller, yes
21:57
<
apritzel >
that should work fine with Hi-Speed, since it's the usual EHCI/OHCI pair
21:57
<
youmukonpaku1337 >
oh
21:57
<
youmukonpaku1337 >
can i switch it to ehci then...?
21:57
<
youmukonpaku1337 >
if so how
21:57
<
youmukonpaku1337 >
cause atm the interface in linux is a 1.1 root hub lol
21:58
<
apritzel >
which probably means something's gone wrong with the EHCI setup
21:58
<
apritzel >
the bootlog would be your friend again
21:58
<
youmukonpaku1337 >
and let me guess: this means digging through dmesg
21:58
<
youmukonpaku1337 >
yep
21:58
<
youmukonpaku1337 >
knew it
21:59
<
youmukonpaku1337 >
ugh
21:59
<
apritzel >
there are two separate devices, one OHCI, and EHCI
21:59
<
youmukonpaku1337 >
OH
21:59
<
youmukonpaku1337 >
yeah
21:59
<
youmukonpaku1337 >
that explains it
21:59
<
youmukonpaku1337 >
one ehci for the musb
21:59
<
youmukonpaku1337 >
one ehci for the wifi and the ohci for the wifi also
21:59
<
youmukonpaku1337 >
and i suppose theyre switched somehow
21:59
<
apritzel >
no, MUSB is not EHCI
21:59
<
youmukonpaku1337 >
oh
22:00
<
youmukonpaku1337 >
i mean it is hi speed, no?
22:00
<
apritzel >
MUSB is MUSB, it has a different software interface, but should support host mode
22:00
<
youmukonpaku1337 >
oh i see
22:00
<
apritzel >
need to look up if it's Hi-Speed, but I think so
22:00
<
youmukonpaku1337 >
yes it is
22:00
<
youmukonpaku1337 >
lsusb -t lists it as such at leasy
22:01
<
apritzel >
yeah, the manual explicitly lists Hi-Speed in host mode
22:02
<
apritzel >
by anyway, we have examples for only either EHCI or OHCI enabled, and that working
22:02
<
youmukonpaku1337 >
i see
22:02
<
apritzel >
for instance for keyboards fixed to the port you only need OHCI
22:02
<
youmukonpaku1337 >
digging time
22:02
<
apritzel >
on the other hand a USB hub only talks EHCI to the host, so you just need EHCI
22:03
<
youmukonpaku1337 >
i see
22:03
<
youmukonpaku1337 >
okay so
22:03
<
youmukonpaku1337 >
usb bus 3 is ehci
22:03
<
youmukonpaku1337 >
and it is registered fine
22:04
<
youmukonpaku1337 >
aaaand... thats the only block lol
22:04
<
youmukonpaku1337 >
bus 1 is ohci
22:04
<
apritzel >
yeah, that part looks fine
22:04
<
youmukonpaku1337 >
so question is what is going wrong
22:05
<
youmukonpaku1337 >
the controller should be the same right
22:05
<
apritzel >
maybe your device is only negotiating up to Full speed (12Mbit), because of a shady cable, for instance?
22:05
<
youmukonpaku1337 >
uhhh
22:05
<
youmukonpaku1337 >
i mean
22:05
<
apritzel >
check dmesg when you connect the device, it might say so
22:06
<
youmukonpaku1337 >
quite sketchy i guess
22:07
<
youmukonpaku1337 >
what the hell
22:07
<
youmukonpaku1337 >
stuff is connected to usb bus 2
22:07
<
apritzel >
that image file seems sketchy as well: "the image ... cannot be displayed because it contains errors"
22:07
<
youmukonpaku1337 >
oh yea oops
22:08
<
apritzel >
but I remember that twisting D-/D+, even for short distances, is helpful
22:09
<
youmukonpaku1337 >
and its still 0kb
22:09
<
youmukonpaku1337 >
ugh
22:09
<
youmukonpaku1337 >
one sec
22:10
<
youmukonpaku1337 >
very sketchy
22:10
<
youmukonpaku1337 >
what
22:10
<
youmukonpaku1337 >
meg
22:10
<
youmukonpaku1337 >
meh
22:10
<
youmukonpaku1337 >
ig something is up with monarchupload atm
22:11
<
youmukonpaku1337 >
here
22:11
<
youmukonpaku1337 >
zoom into the wifi pins lol
22:11
<
youmukonpaku1337 >
pretty sketch i guess apritzel
22:11
<
youmukonpaku1337 >
but again for some reason stuff gets connected on bus 2 which is musb???
22:12
<
youmukonpaku1337 >
in dmesg
22:12
<
apritzel >
yeah, I wouldn't offer beyond 12Mbit as well, if I'd be the PHY ;-)
22:12
<
youmukonpaku1337 >
wait whats PHY
22:14
<
apritzel >
the USB PHY, that piece of (integrated) circuitry that manages the electrical part of the connection
22:14
<
youmukonpaku1337 >
oh
22:14
<
youmukonpaku1337 >
okay so is it just my bad wiring or is it wired only to ohci
22:14
<
youmukonpaku1337 >
or what did i fuck up lol
22:14
<
apritzel >
try to twist the data cables tightly, from end to end
22:15
<
youmukonpaku1337 >
should i use better cables instead lol
22:15
<
youmukonpaku1337 >
i have some nice thick cables
22:15
<
apritzel >
both EHCI and OHCI controllers connect to the PHY, which provides the two D-/D+ pins
22:15
<
youmukonpaku1337 >
oh okay
22:15
<
youmukonpaku1337 >
so its just cable quality?
22:16
<
apritzel >
so if you have a connection via one controller, the connection part is fine, and it should work with the other controller as well
22:16
<
apritzel >
but the signal quality needs to be much better for Hi-Speed
22:16
<
youmukonpaku1337 >
i see
22:16
<
youmukonpaku1337 >
the thick cable i mentioned is for hifi systems so uh
22:16
<
apritzel >
the cable "quality" is not so critical, at least not for the data pins, and not over such short distances
22:16
<
youmukonpaku1337 >
should be mostly okay?
22:17
<
youmukonpaku1337 >
oh
22:17
<
apritzel >
no, think won't help, it's not a current issue
22:17
<
youmukonpaku1337 >
so what could help here then
22:17
<
apritzel >
as I said: twist the cables around each other, like in a twisted pair Ethernet cable
22:17
<
youmukonpaku1337 >
oh
22:17
<
youmukonpaku1337 >
are you sure that would help? lol
22:18
<
youmukonpaku1337 >
but alright
22:18
<
apritzel >
I didn't believe that either, but I solved a USB issue with that
22:18
<
youmukonpaku1337 >
holy fuck
22:18
<
youmukonpaku1337 >
lmao
22:18
<
youmukonpaku1337 >
okay
22:19
<
apritzel >
and IIRC it was the very same symptom: 12Mbit was working, but it wasn't negotiating Hi-Speed
22:19
<
youmukonpaku1337 >
hmm
22:19
<
youmukonpaku1337 >
okay
22:19
<
youmukonpaku1337 >
i will test in like 10 min
22:19
<
apritzel >
actually if you use thinner cables, that helps the twisting and thus signal integrity
22:19
<
youmukonpaku1337 >
ooh
22:19
<
youmukonpaku1337 >
i see
22:19
<
youmukonpaku1337 >
are those thin enough? lol
22:20
<
youmukonpaku1337 >
theyre standard arduino 15cm jumper cables
22:21
<
youmukonpaku1337 >
well
22:21
<
youmukonpaku1337 >
not arduino
22:21
<
youmukonpaku1337 >
just dupont
22:22
<
apritzel >
well, they might work, but I wonder if you need to lose the connectors, because they are not twisted
22:23
<
youmukonpaku1337 >
hmm
22:23
<
youmukonpaku1337 >
thats possible
22:23
<
youmukonpaku1337 >
but what about the uh
22:24
ftg has quit [Read error: Connection reset by peer]
22:24
<
apritzel >
I just read that for low speed the data lines might not be twisted, so the plot thickens
22:24
<
youmukonpaku1337 >
hmm
22:24
<
youmukonpaku1337 >
alright so ill test twisting them
22:24
<
youmukonpaku1337 >
btw they should hold the twist fine or do i need to do something else
22:25
<
youmukonpaku1337 >
btw what about the female end of the jumper, how am i gonna twist that lol
22:32
<
apritzel >
well, give it a try, but remember that the data lines work in the VHF frequency range in Hi-Speed mode
22:33
<
apritzel >
the easiest way is typically to sacrifice some old USB cable: that has the right wires and is twisted correctly already
22:35
<
youmukonpaku1337 >
an option
22:35
<
youmukonpaku1337 >
i suppose
22:35
<
youmukonpaku1337 >
but lemme just try twisting these first
22:40
<
apritzel >
any extlinux (on U-Boot) users here? jernej? Who is generating (or just providing) extlinux.conf? Is that the "distro"?
22:40
<
apritzel >
I see that in Debian the extlinux package only exists for x86, so no scripted generation there, I guess?
22:41
<
apritzel >
(with "there" I mean for Debian based distros on armhf/arm64)
22:42
<
gnarface >
apritzel: i just made my extlinux.conf by hand but there's supposedly a tool that comes with u-boot that can generate them
22:47
DarkNeutrino has quit [Ping timeout: 480 seconds]
22:47
DarkNeutrino has joined #linux-sunxi
22:47
<
youmukonpaku1337 >
apritzel: im gonna have to use another wire anyway or cut off the connectors cause uhh
22:48
<
youmukonpaku1337 >
i have the wrong cable type
22:48
<
youmukonpaku1337 >
ill just use a usb cable
23:31
<
youmukonpaku1337 >
okay did some sketchy soldering
23:32
<
youmukonpaku1337 >
gonna test if it works in a bit