<alyssa_>
Has anyone played with chainloading u-boot from depthcharge on rk chromebooks, for the purpose of running vanilla mainline, including support for initramfs and so forth?
equaa has joined #linux-rockchip
alyssa_ has quit [Quit: leaving]
akaizen has joined #linux-rockchip
akaizen has quit [Client Quit]
akaizen has joined #linux-rockchip
tllim has joined #linux-rockchip
ssvb has joined #linux-rockchip
lurchi_ is now known as lurchi__
cnxsoft has joined #linux-rockchip
ssvb has quit [Ping timeout: 250 seconds]
tl_lim has joined #linux-rockchip
tllim has quit [Ping timeout: 246 seconds]
nighty- has joined #linux-rockchip
tl_lim has quit [Ping timeout: 246 seconds]
tl_lim has joined #linux-rockchip
akaizen has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
indy has quit [Ping timeout: 268 seconds]
equaa has quit [Ping timeout: 250 seconds]
indy has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
<rompelstompel_>
are there any Rock64 users that managed to get mpph264enc working in gstreamer?
<sphalerite>
Anyone know what is required for the framebuffer and fbconsole to start working? They don't work in the initrd for me, and I'd quite like to see what's going on before the root switch
<mmind00>
sphalerite: hmm, normally this should just work, but of course depends on the soc ... rk3288 I guess?
<sphalerite>
mmind00: yes, sorry, forgot to mention that bit
<mmind00>
sphalerite: in my board-farm I only do arm64 with initrds, but I think it does come up with the display at the initrd stage
<sphalerite>
mmind00: fb and fbcon do work fine, just not ini initrd. I think I just need to put the right modules in the initrd, question being which ones
<mmind00>
sphalerite: lsmod? :-)
<sphalerite>
mmind00: weeeeelll there's the little issue that I haven't actually got a modular kernel booting consistently enough to do that :p
<sphalerite>
and having fbcon working in the initrd might help me work that out
<mmind00>
sphalerite: the proverbial hen+egg problem ;-)
<sphalerite>
I've got a kernel with all the drivers built in working, but yeah
<sphalerite>
and I don't think I have a way to get a serial console on it
<sphalerite>
(c201 chromebook)
<vagrantc>
rock64 is rk3328, no?
<mmind00>
vagrantc: yep ... and rock64pro is rk3399-based
<rompelstompel_>
Interesting, though have you perhaps managed to get the hardware encoding to work on rock64
<sphalerite>
I'm not sure what the problem with booting the modular kernel actually is. It works every once in a blue moon, but I can't tell why it doesn't work the rest of the time because I get no output from it >.> I suspect an eMMC-related hang or me just getting the root device wrong, but I have no way of telling
<vagrantc>
sphalerite: i've gotten eMMC related hangs on c201 pretty regularly ... i just added some modules to my initrd to get it to show up on the screen
<sphalerite>
vagrantc: which ones? :)
<vagrantc>
sphalerite: you could also enable rockchip.uart_usb if you just build in usb
<sphalerite>
I already have pwm-rockchip, rtc-rk808, clk-rk808, rockchipdrm, vgem
<sphalerite>
vagrantc: I need some specific hardware to make use of that, right?
<vagrantc>
yes
<sphalerite>
would a USB-UART thing and a raspberry pi be sufficient for that?
<vagrantc>
my c201 is currently in a partly broken state due to experimenting with u-boot (and it never really worked well)
<vagrantc>
sphalerite: i've only tried with attaching a hacked up USB cable to a serial-ttl adapter
<vagrantc>
sphalerite: but possibly rpi would work
<sphalerite>
I think what I have is a USB-TTL cable (USB on one end, 4 stick thingies on the other iirc)
<vagrantc>
yeah, then you need to hack up a USB cable and wire the appropriate parts to the "4 stick thingies"
<vagrantc>
then enable the feature in the kernel and pass the kernel the rockchip.usb_uart option on the commandline
<vagrantc>
sphalerite: the rockchip.usb_uart effectively rewires one of the USB ports to no longer talk USB, but instead exposes some pints for serial-ttl
<sphalerite>
oh ok so I'm guessing the USB-TTL cable is not what I'll want to plug into the chromebook
<vagrantc>
s,pints,pins,
<vagrantc>
you'll need something like it, but you'll also need a custom cable with a USB end on it and exposed wires on the other end
<sphalerite>
instead cutting up a USB cable and attaching pins to it which I then stick into the USB-TTL cable and the USB end of that into another computer?
<vagrantc>
sounds about right
<sphalerite>
I don't have the USB-TTL cable or any sacrificeable USB cables (or relevant tools) at hand, I probably will tomorrow. In the meantime, any specific kernel modules which might help me get fbcon?
* vagrantc
doesn't have the c201 available to check
matthias_bgg has quit [Ping timeout: 240 seconds]
<vagrantc>
DRM_PANEL_SIMPLE, ROCKCHIP_ANALOGIX_DP
<vagrantc>
those modules i think were needed
<sphalerite>
oooh I haven't got analogix-dp in the module list yet
<sphalerite>
not sure what the module name for DRM_PANEL_SIMPLE is but I'll see if I can work that out, thanks for the pointers!
<vagrantc>
panel-simple or simple-panel would be my guess :)
<vagrantc>
panel-simple
<vagrantc>
BACKLIGHT_PWM ?
<sphalerite>
the screen is plain white (the backlight very much on) during initrd, so I'm not sure I need that additionally
<vagrantc>
pwm_bl
<vagrantc>
sphalerite: using coreboot?
<sphalerite>
yeah, coreboot and depthcharge
<vagrantc>
haven't tried recent mainline coreboot ... had an old libreboot running on it
<sphalerite>
hm, panel_simple and pwm_bl are built-in so those won't be the ones missing
<vagrantc>
now u-boot looks so close i just want to switch to that :)
<sphalerite>
well it's not mainline coreboot, it's libreboot as well
<vagrantc>
ah
<sphalerite>
just the libreboot from libreboot's website
<rompelstompel_>
I am getting the following with mpph264enc on rock64:
<vagrantc>
sphalerite: you might also need rk808-regulator
<sphalerite>
going to see if adding analogix-dp is enough, brb, thanks for the help so far!
<sphalerite>
vagrantc: also built-in
sphalerit has joined #linux-rockchip
<sphalerite>
nope, still plain white screen :(
<sphalerite>
ok since I can't get my hands on hardware flashing tools right now… how often does software flashing go wrong?
<sphalerite>
if it does go wrong my c201 will be inoperable for 4 days or so while I wait for the stuff to arrive, and I want to know how likely that scenario is so I can decide whether to try it before having the kit or not :)
* vagrantc
shrugs
<sphalerite>
how many software flashes have you done, and how many have gone wrong?
afaerber has quit [Remote host closed the connection]
<sphalerite>
(on rk3288s)
afaerber has joined #linux-rockchip
<vagrantc>
i think i've done two software flashes, and one of them went badly, and since i've just used the hardware flashers
<vagrantc>
i don't think it was because the flash process went badly, but i was installing something of unknown status
<sphalerite>
ah ok
<sphalerite>
oh yeah, I also don't know how I'm going to get the actual image I want to flash yet either, heh
<vagrantc>
burn your bridges in the right order :)
<sphalerite>
aye
<sphalerite>
now where are the build instructions for libreboot >.>