<amstan>
why don't you use the usb trick on veyron?
<macc24>
because i don't want to have separate debug and release cadmium builds
<amstan>
uart voltages are 1.8V on gru and 3.3V on gru i think, but you can always check (see ppdut_uart2_vref)
<macc24>
uuh
* macc24
noted]
<amstan>
in theory you're also only supposed to have uart connected there (aka your adaptor emitting voltage toward the chromebook) when ppdut_uart2_vref is high ortherwise you're producing a current leak when the chromebook is off and might kill the pin
<macc24>
yea i only have uart connected
<macc24>
and a 500 ohm resistor on 3v3 in case i fuck :D
<amstan>
except replace atmega328 with rk3399 and io pins with uart_tx from your adaptor to uart_rx on the rk3399
<amstan>
vcc being ppdut_uart2_vref
vagrantc has joined #linux-rockchip
<macc24>
hmm
alpernebbi has quit [Ping timeout: 240 seconds]
alpernebbi has joined #linux-rockchip
chewitt has joined #linux-rockchip
robmur01 has quit [Ping timeout: 256 seconds]
robmur01 has joined #linux-rockchip
robmur01 has quit [Read error: Connection reset by peer]
alpernebbi has quit [Ping timeout: 256 seconds]
robmur01 has joined #linux-rockchip
<Orac>
Any of you running a rockpro64 with a nvme root by chance? I'm going to be getting my unit in a week or two and building a system (I build arm os's from scratch) and wanted to know if there are any gootchas I should watch out for
<Orac>
my plans are to continue with the distro I know (Debian)
<amstan>
i still think you're crazy for attempting this
<amstan>
lol
<macc24>
lol
<macc24>
i've done crazier things
<macc24>
have i told you about that time i with my friend soldered pci express onto a laptop docking port
<macc24>
and the dock now has pci express?
<Orac>
macc24: that just sounds fun
<macc24>
amstan: i'm telling you, at end of this year i'll solder into uart port on a ball of a bga chip xD
<Orac>
macc24: I wish I could hold my hands steady enough to solder anymore
<macc24>
amstan: you know what makes it crazier?
<macc24>
the tip i used xD
<macc24>
it's 1.5mm at thinnest point xD
<macc24>
and it's the stock tip of my iron xD
<vagrantc>
Orac: i have a rockpro64 and i think i had used it with sata root ...
<vagrantc>
Orac: also using debian NVMe root on the pinebook pro, which is fairly similar
<Orac>
that's a good start then
<Orac>
I can make the dtb adjustments very easy I need then
<vagrantc>
i am, in fact, on irc with that very pinebook :)
<Orac>
already doing it for about 7 other socs right noe
<Orac>
er now
<Orac>
I wanted to wait for the rock5 but getting anxious to try a rk out
<Orac>
I have just about every other main vendor out there
<vagrantc>
i really e
<vagrantc>
should boot the rockpro64 again sometime... it's been a while
<Orac>
I also plan on sharing time between it and freebsd
<Orac>
ok so the pbpro is essential the same soc.. good
<vagrantc>
i got both because i think at the time the rockpro64 would arrive sooner and i could get debian ready foro the rk3399 soc ... although i think in the end mostly otther folks already did most of the work
<Orac>
for me I only need headless so the soc is perfect
Orac is now known as Tenkawa
stikonas has joined #linux-rockchip
rektide has quit [Ping timeout: 256 seconds]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
camus1 has joined #linux-rockchip
camus has quit [Ping timeout: 240 seconds]
camus1 is now known as camus
lurchi__ is now known as lurchi_
System_Error has quit [Read error: Connection reset by peer]
<macromorgan>
mmind00: for that clock thingy I'm trying to make sure I have the yaml files right... so the xin32k should be there and I should add it to the yaml file?
s1b1 has quit [Read error: Connection reset by peer]
vagrantc has joined #linux-rockchip
<mmind00>
macromorgan: I'm not sure about there being 2 clocks there ... the clk-rk808 driver does strange things on first glance and I only skimmed the rk817 datasheet
<macromorgan>
yeah, near as I can tell the first clock is assumed always on (the only function is to return 32768 when you attempt to adjust it), the second clock controls the register for actually setting the clock
<mmind00>
macromorgan: though the clock being named xin32k is specific to the rk8xx being used together with the 32k input of the soc
<macromorgan>
the datasheet confirms the rk805, rk809, and rk817 only have 1 clock, whereas the rk808 and rk818 have 2.
<macromorgan>
okay, so ignore/delete that patch and I'll put a note about the implementation in the yaml file I send
<macromorgan>
for now that means (I think) everything is fixed with rewriting the rk808.txt to yaml except the errors for the rk809 (or is it rk808) with the vcc13 and vcc14.
<mmind00>
alternatively declare 1 clock in the yaml for the affected rk8xx and adapt the driver to map clk1 to the real clock if only one output-name declared, fall back to the current state if there are 2 output-names (for backward compatiblity)
<mmind00>
the clk-rk808.c already knows the type of rk8xx, so I'm not really sure why there are two clocks for them at all ;-)
<mmind00>
macromorgan: DT-basic is "a binding should declare the hardware, not implementation hacks" ;-)
<macromorgan>
okay, need to fix the driver :-(
<mmind00>
macromorgan: thankfully it will mainly be jumping through hoops during probe to allow the "sane" case but also stay backward-compatible with existing dts ... hence the check number of elements in clock-output-names
s1b1 has joined #linux-rockchip
<macromorgan>
seems for the moment this is a thing that only affects the odroid go advance and nothing else
<macromorgan>
actually just kidding... quartz64 too
<macromorgan>
I'm afraid I'm lost...
<macromorgan>
you're saying if there is only one name and it's rk805,rk809, or rk817 map it to clock 2 (the real clock), and if there are 2 names do what we already do?
Tenkawa has quit [Quit: Leaving.]
matthias_bgg has quit [Ping timeout: 256 seconds]
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-rockchip
Whistler has quit [Ping timeout: 252 seconds]
dianders has quit [Read error: Connection reset by peer]
arnd has quit [Read error: Connection reset by peer]
tucanae47_ has quit [Read error: Connection reset by peer]