ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
<vagrantc> well, before coreboot support for veyron_speedy was in mainline, libreboot included patches for it, so it was easier to get running
<amstan> it might not have been in mainline, but https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/firmware-veyron-6588.B/src/mainboard/google/veyron_speedy always had the running version, the same version shipping on the device
<vagrantc> alyssa: it might be dwc2 actually... i haven't been able to figure it out ... but it seems to cooincide with eMMC errors more excessive than usual
gnufan has joined #linux-rockchip
<vagrantc> at any rate, i've been thinking i should try flashing the newest coreboot+depthcharge to see if it works any better, since i've been struggling with this poor thing for years
<alyssa> vagrantc: in my limited experience, eMMC usually causes issues on boot itself but then after successfully booting to userspace is nice and quiet. dwc2 on the other hand is the usual culprit for post-boot system instability. but what do I know? I couldn't manage to boot a debian kernel the other today ;)
<vagrantc> i also seem to remember libreboot also exposing a very minimal user-interface ... e.g. displaying a short text description for each of the keybindings that do various things
<alyssa> (this is on a 4.14 rc with some patches. I'm hopefuly 4.15 brought fixes? Alternatively, time to fork over some money since mmind00 is hopeful RK3399 is immune from these issues :p)
<vagrantc> is there an rk3399 laptop?
<alyssa> all the new ARM chromebooks are rk3399 iirc
<vagrantc> ah
<alyssa> and apparently there's a CrOS rk3399 tablet coming out in the next month, which might be fun to play with ;P
* vagrantc will give the veyron_speedy a few more tries sometime soon
<sphalerite> vagrantc: asus c101pa, samsung chromebook 2, iirc
<sphalerite> I think the marketing name for rk3399 is OP1
<alyssa> which I find hilarious since OP1 -also- follows the technical chip naming scheme of "capital letters followed by number" :p
* vagrantc waves
<sphalerite> Hardware names and version numbers are just generally confusing
vagrantc has quit [Quit: leaving]
<amstan> warning: "samsung chromebook 2" is a very overloaded name, it might mean the intel machine
<amstan> sphalerite: yeah, i suggest you just stick with rk3399
<alyssa> "Rockchip RK3399 (OP1) integrates Mali... supporting... DirectX11.1." Besides my own on a technicality, I somehow don't think there's a DX11 driver for the Chromebook :^)
<amstan> alyssa: yeah, don't read those feature lists
<amstan> sometimes they label it as "Intel Rockchip RK3399"
<sphalerite> o.o
<amstan> sometimes they bundle it with an antivirus and microsoft office
<amstan> i've lost all faith in them
<alyssa> were we supposed to have faith in them to begin with? :D
<amstan> "Crtex" "OPI"
<sphalerite> D:
<amstan> oh! we don't need mali drivers everyone!
<amstan> "GPU/VPUIntel HD Graphics"
<sphalerite> I previously attributed this to malice, in the sense that the marketers just want to sell the stuff even if they stray from the exact truth a bit
<sphalerite> but this is just incompetence, isn't it...
<sphalerite> why did they come up with this OP1 name anyway
<sphalerite> rk3399 is so much clearer and distinguishable
<sphalerite> none of this OPI crap
* sphalerite needs to sleep
<sphalerite> gnight all
<amstan> good night
gnufan has quit [Ping timeout: 260 seconds]
<alyssa> is Crtex a faster version of Cortex?
<amstan> alyssa: yes, but don't quote me on it
<alyssa> :p
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 264 seconds]
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 265 seconds]
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 264 seconds]
gnufan has joined #linux-rockchip
anarsoul|2 has quit [Ping timeout: 264 seconds]
gnufan has quit [Ping timeout: 264 seconds]
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 265 seconds]
cnxsoft has quit [Ping timeout: 260 seconds]
gnufan has joined #linux-rockchip
alyssa has left #linux-rockchip [#linux-rockchip]
cnxsoft has joined #linux-rockchip
gnufan has quit [Ping timeout: 240 seconds]
gnufan has joined #linux-rockchip
ezequielg has quit [Ping timeout: 276 seconds]
tl_lim has quit [Read error: Connection reset by peer]
tl_lim has joined #linux-rockchip
tl_lim has quit [Ping timeout: 276 seconds]
tl_lim has joined #linux-rockchip
cyteen has quit [Quit: Leaving]
cyteen has joined #linux-rockchip
gnufan has quit [Ping timeout: 264 seconds]
lurchi__ has joined #linux-rockchip
gnufan has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 264 seconds]
vstehle has joined #linux-rockchip
gnufan has quit [Ping timeout: 240 seconds]
Easyfab has joined #linux-rockchip
gnufan has joined #linux-rockchip
xerpi has joined #linux-rockchip
tl_lim has quit [Ping timeout: 245 seconds]
tl_lim has joined #linux-rockchip
tl_lim has quit [Ping timeout: 245 seconds]
tl_lim has joined #linux-rockchip
chewitt has quit [Ping timeout: 265 seconds]
chewitt has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
tl_lim has quit [Ping timeout: 245 seconds]
tl_lim has joined #linux-rockchip
BenG83 has quit [Ping timeout: 260 seconds]
aalm has quit [Ping timeout: 256 seconds]
tl_lim has quit [Read error: Connection reset by peer]
cyteen has quit [Ping timeout: 240 seconds]
ayaka has joined #linux-rockchip
<ayaka> finally overcome the damn emperor Xi's poisoned network
nighty-- has joined #linux-rockchip
cyteen has joined #linux-rockchip
ayaka has quit [Ping timeout: 245 seconds]
ayaka has joined #linux-rockchip
xerpi has quit [Quit: Leaving]
ayaka has quit [Ping timeout: 260 seconds]
ayaka has joined #linux-rockchip
ayaka has quit [Ping timeout: 255 seconds]
gnufan has quit [Ping timeout: 260 seconds]
gnufan has joined #linux-rockchip
ayaka has joined #linux-rockchip
aalm has joined #linux-rockchip
nighty-- has quit [Quit: Disappears in a puff of smoke]
wzyy2 has joined #linux-rockchip
gnufan has quit [Ping timeout: 260 seconds]
gnufan has joined #linux-rockchip
chewitt has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
chewitt has joined #linux-rockchip
chen has joined #linux-rockchip
chen is now known as Guest95500
wzyy2 has quit [Ping timeout: 264 seconds]
Guest95500 has quit [Quit: Konversation terminated!]
gnufan has quit [Ping timeout: 240 seconds]
gnufan has joined #linux-rockchip
<sphalerite> what's needed in order to get output from the kernel to the screen during early boot? I don't seem to get a graphical console until after initrd, which makes debugging that stage of boot quite difficult :)
gnufan has quit [Ping timeout: 260 seconds]
gnufan has joined #linux-rockchip
<hanetzer> earlyprintk as part of the kernel parameters, and a properly setup debug_ll :)
<sphalerite> That doesn't sound like the answer to my question. I'd prefer something that doesn't imply "get some more hardware"
<hanetzer> oh... didn't quite grok what you asked. But idk about that, and for the most part if you're doing embedded/arm you should have at least a few uart adapters on hand ;)
<sphalerite> I don't
<sphalerite> oh and this is a chromebook, should have mentioned that bit
<sphalerite> C201
xerpi has quit [Quit: Leaving]
<hanetzer> ah, I got one of those. What bootloader are you using?
<hanetzer> 2gb variant?
<sphalerite> yep 2gb and depthcharge
<hanetzer> libreboot?
<sphalerite> yeah
<hanetzer> I never had luck with that.
<hanetzer> I got grub2 to 'work' as a coreboot payload on my c201/4gb, though its far from being usable
<sphalerite> I mean, booting works fine in general. I'm just trying to get the stock kernel for my distro to work on it more reliably (it does work, just not reliably currently)
<sphalerite> and I'm wondering what userspace fiddling is necessary to get a graphical console before switching to the real root filesystem
<sphalerite> and a manually-built kernel works just fine
<hanetzer> prolly early kms at least
gnufan has quit [Ping timeout: 240 seconds]
<sphalerite> that just requires the modules to be included in the initrd right?
<sphalerite> I've just gone and included all the drivers loaded in a successful boot in the initrd, but the screen still stays white until after the initrd
<hanetzer> hrm. firmware in the initrd as well?
tllim has joined #linux-rockchip
gnufan has joined #linux-rockchip
<sphalerite> yeah although I don't think it needs any firmware?
<hanetzer> no clue, not that far into using them
LargePrime has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
tl_lim has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
tllim has quit [Ping timeout: 265 seconds]
tl_lim has quit [Ping timeout: 276 seconds]
tl_lim has joined #linux-rockchip
BenG83 has joined #linux-rockchip
gnufan has quit [Ping timeout: 260 seconds]
unics has joined #linux-rockchip
gnufan has joined #linux-rockchip
cyteen has quit [Ping timeout: 265 seconds]
tl_lim has quit [Ping timeout: 245 seconds]
tl_lim has joined #linux-rockchip
gnufan has quit [Ping timeout: 260 seconds]
gnufan has joined #linux-rockchip
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-rockchip
gnufan has quit [Read error: Connection reset by peer]
aalm has quit [Ping timeout: 240 seconds]
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 255 seconds]
gnufan has joined #linux-rockchip
leah2 has quit [Ping timeout: 276 seconds]
leah2 has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
unics has quit [Quit: Leaving]
Easyfab has quit [Quit: Leaving]
gnufan has quit [Ping timeout: 260 seconds]
aalm has joined #linux-rockchip
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 240 seconds]
gnufan has joined #linux-rockchip
cyteen has joined #linux-rockchip
gnufan has quit [Ping timeout: 260 seconds]
gnufan has joined #linux-rockchip
gnufan has quit [Ping timeout: 260 seconds]
BenG83 has quit [Quit: Leaving]
gnufan has joined #linux-rockchip
rj1_ is now known as rj1
rj1 has quit [Changing host]
rj1 has joined #linux-rockchip
rj1 has joined #linux-rockchip
tl_lim has quit [Ping timeout: 245 seconds]