ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
stikonas has quit [Remote host closed the connection]
tlwoerner has quit [Ping timeout: 240 seconds]
norris has quit [*.net *.split]
dvergatal has quit [*.net *.split]
dvergatal has joined #linux-rockchip
norris has joined #linux-rockchip
tlwoerner has joined #linux-rockchip
tlwoerner has quit [Ping timeout: 256 seconds]
tlwoerner has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
dlezcano has quit [Remote host closed the connection]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
shoragan has joined #linux-rockchip
<macc24> mmind00: do you test if sound works?
<mmind00> macc24: not really ... my boardfarm doesn't have any sound-specific setup ... so in terms of multimedia the core display is the one thing I do test regularly
<macc24> mmind00: i hear sound's broken on veyron... need to bisect
<mmind00> macc24: also, the speakers on my veyron test-device gave up their magic smoke years ago [it even smelled aweful], when some sound thingy went haywire
<macc24> mmind00: what if u hook up an led into those speakers
<macc24> and put that alongside screen so u can see if speakers are working
<mmind00> macc24: too complex ... my boardfarm is actually a separate entity, where the display for example goes to a hdmi muxer device which in turn runs to an external monitor and the serial console comes through a web-interface ... I don't physically touch / see devices when doing tests
<macc24> mmind00: huh, interesting
<mmind00> macc24: https://chemnitzer.linux-tage.de/2017/de/programm/beitrag/208 ... ignore the german language and go to 28:40 in the video ;-)
<macc24> ooh servo
<macc24> where did you get those boards from?
<mmind00> macc24: same source I got my Veyron/Gru devices from ... the big "G" ;-)
<macc24> mmind00: i want servos too D:
<mmind00> macc24: hehe
System_Error has quit [Ping timeout: 276 seconds]
System_Error has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
vagrantc has joined #linux-rockchip
<amstan> macc24: i would try building a suzyq again
<macc24> amstan: i just did it the pay2win way and shelled out 70pln for a suzyqable
<macc24> hmm that usb breakout board gives me ideas
<macc24> i wonder if arm chromebook with thunderbolt is ever going to launch...
<amstan> as soon as we get back to SOCs that have real type C ports, like gru used to have
<amstan> not this usb hub abomination (imagine that for pcie)
matthias_bgg has quit [Quit: Leaving]
<macc24> amstan: :o
<macc24> plz gib pci express
<macc24> so i can hook up a desktop gpu to a low power laptop xD
<amstan> i'm not holding my breath, heh
<macc24> :(
stikonas has joined #linux-rockchip
<robmur01> macc24: s/chromebook/laptop/ and there are fruit-flavoured options
<macc24> robmur01: add my budget into consideration and list falls back to 0
<robmur01> at least by the time such a Chromebook comes out a second-hand M1 Air might be cheaper :)
<macc24> still not cheap enough lol
<macc24> 2013 macbook air with average components is 3 times as expensive as the most i spent on a laptop to use as daily driver
<macc24> i'm, what some might call, "unemployed"
lurchi__ is now known as lurchi_
shailangsa has joined #linux-rockchip
lurchi_ is now known as lurchi__
<alpernebbi> I got u-boot working as a chromeos kernel partition :D
<alpernebbi> you might wanna try u-boot.elf in a coreboot build, idk
<macc24> what's your config and how did you assemble spi flash image for kevin?
<alpernebbi> macc24: also please try veyron's .kpart images, but I'm not sure what's their status is with mainline u-boot
<macc24> ok
<alpernebbi> it's the defconfig in the tagged commit
<alpernebbi> some u-boot tool called binman assembles the SPI flash image
<macc24> i love how easy kevins are to take apart
<alpernebbi> see arch/arm/dts/rk3399-u-boot.dtsi for a binman node
<alpernebbi> if you want to build things yourself there's a tool for that as well, buildman
<alpernebbi> I wrote some things in my repo wiki that might help
<ente`> macc24: that sentence sounds weird out of context
<macc24> ente`: i dare you to take it out of context
<ente`> macc24: "?!"
<ente`> unfortunately it's a windows demo :(
<macc24> heh, my clip broke
<macc24> and i can't find dupont cables
<macc24> guess i'll solder new clip onto old cables lol
<macc24> i've got to build a proper programming board for stm32 bluepill...
<macc24> alpernebbi: full rom image booted up \o/
<alpernebbi> it doesn't boot a kernel for me tho
<macc24> what are you trying to boot that kernel with?
<alpernebbi> extlinux.conf from u-boot-menu debian package
<macc24> odd
<alpernebbi> I mean it works from U-Boot in RW_LEGACY and U-Boot in the kernel partition, but not as full rom, it just gets stuck at "Starting kernel..."
<alpernebbi> did it boot into an OS for you
<macc24> i'll experiment around
<alpernebbi> thanks
<macc24> did you compile in support for chromeos kernel partitions?
<alpernebbi> not into u-boot, no
<macc24> ._.
<macc24> uh, i think i left stove on at home
<alpernebbi> But I'm not trying to boot from chromeos kernel partitions anyway?
macc24 has left #linux-rockchip [WeeChat 2.8]
<alpernebbi> It's meant to be an ordinary distro boot
<alpernebbi> I mean it does load kernel/initramfs/dtb just fine, I think I'm getting a early kernel panic
macc24 has joined #linux-rockchip
<macc24> jokes aside i'll try booting something linux on it
<macc24> hmmm early kernel panic
<macc24> alpernebbi: do you know if u-boot adds simplefb node into device tree?
<alpernebbi> I think there's a config for it that I did not enable
<macc24> ...
<macc24> alright i'll compile u-boot for kevin myself
<macc24> what is the least broken-on-kevin branch of https://github.com/alpernebbi/u-boot?
<alpernebbi> rk3399-gru-kevin
<alpernebbi> currently the tagged commit
<macc24> okay
<alpernebbi> I see config VIDEO_DT_SIMPLEFB
<macc24> and /just/ defconfig is good?
<alpernebbi> configs/chromebook_kevin_defconfig to be precise, I do commit whatever I need into it
<macc24> okay
<macc24> alpernebbi: bootefi doesn't work too
<macc24> `bootefi hello`
<alpernebbi> would be easier to debug with a servo :p
<macc24> or at least with uart....
<alpernebbi> yeah
<alpernebbi> macc24: CONFIG_CMD_BOOTEFI_HELLO is not set btw
<alpernebbi> unless you set it yourself
<macc24> alpernebbi: i compiled my own build
<alpernebbi> I had tried `bootefi selftest` and remember it showing only a network error
<alpernebbi> do tell if you see any good options I should have enabled
<macc24> alpernebbi: fyi veyron kpart boots with no display
<alpernebbi> which veyron was it
<macc24> minnie
<alpernebbi> great, thanks for testing :D
<alpernebbi> I'm assuming the display is something with u-boot and not about how I put it into the kpart :P
<macc24> theoretically yes
<macc24> depthcharge might be leaving display controller in weird state
<macc24> with u-boot not kicking it into whatever it expects
<alpernebbi> understandable
lkcl has quit [Quit: BNC by #bnc4you]
lurchi__ is now known as lurchi_
<macc24> alpernebbi: so far i can say "i have no idea"
<alpernebbi> same
<macc24> mmind00: ???
<macc24> any ideas why u-boot can't boot anything on a rk3399 device?
<alpernebbi> macc24: also, not urgent but I'd be glad if you can test minnie.cbfs as RW_LEGACY
<alpernebbi> (I'll go sleep soon)
<macc24> good night
<alpernebbi> thanks again
<mmind00> macc24: that would need more information ... i.e. my rk3399-puma board has an uboot 2021.10 I think ... so uboot works ;-) ... and my Gru-Kevin does use Coreboot reflashed to do only netboot - so no uboot there
<macc24> mmind00: that puma board, what config does it have?
<macc24> hmmmm
<alpernebbi> mmind00: context is my u-boot-on-gru-kevin work here https://github.com/alpernebbi/u-boot/tree/rk3399-gru-kevin
<mmind00> as I said, I never spent much time on bootloaders for ChromeOS devices ... the base coreboot always did what I needed
<macc24> mmind00: can you check u-boot v2022.04-rc1 ?
<macc24> on your rk3399-puma
<alpernebbi> I don't think it's a rk3399 problem either
lkcl has joined #linux-rockchip
<macc24> alpernebbi: what device do you have?
<mmind00> don't really have the time for that ... though I remember u-boot breaking way too often
<macc24> okay
<alpernebbi> only gru-kevin, but from others' comments I remember that pinebook-pro and others worked for the commits where gru-kevin doesn't
<macc24> hmm i wonder if it works on a gru-bob
<macc24> i also wonder why it didn't ask me for bl31 firmware