ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log | Community GH | Rockchip GH | ML
vagrantc has quit [Quit: leaving]
<micken> another stupid RK3288 question:
<micken> Is it possible to slow down timers? Setting something in CRU to make it like 1Mhz
vstehle has quit [Ping timeout: 263 seconds]
<micken> never mind
anarsoul|2 has quit [Ping timeout: 260 seconds]
cnxsoft has joined #linux-rockchip
tlwoerner has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-rockchip
lurchi_ is now known as lurchi__
tlwoerner has joined #linux-rockchip
tlwoerner has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
Aussie_matt has joined #linux-rockchip
vstehle has joined #linux-rockchip
VargaD has quit [Ping timeout: 250 seconds]
tlwoerner has quit [Ping timeout: 260 seconds]
libv has quit [Ping timeout: 260 seconds]
libv has joined #linux-rockchip
tlwoerner has joined #linux-rockchip
tlwoerner has joined #linux-rockchip
tlwoerner has quit [Changing host]
VargaD has joined #linux-rockchip
VargaD has quit [Ping timeout: 265 seconds]
VargaD has joined #linux-rockchip
Easyfab has joined #linux-rockchip
xerpi has joined #linux-rockchip
lkcl has joined #linux-rockchip
stephw4DVGC1 has joined #linux-rockchip
stephw4DVGC1 has quit [Client Quit]
xerpi has quit [Quit: Leaving]
lkcl has quit [Ping timeout: 240 seconds]
afaerber has joined #linux-rockchip
lkcl has joined #linux-rockchip
Aussie_matt has quit [Remote host closed the connection]
<mmind00> micken: looks like you solved your issue already ... normally Rockchip timers are sourced directly from the 24MHz oscillator without any dividers between them
zzarr has quit [Ping timeout: 246 seconds]
zzarr has joined #linux-rockchip
<lvrp16> is rockchip working on rk3229?
<lvrp16> for their mainline efforts
<mmind00> lvrp16: you'll need to ask Rockchip what their plans are ... in general I see patches for all socs from them and they did the rk3229 mainline uboot port, so this soc seems definitly to be on their agenda
<lvrp16> mmind00: thanks, that puts the shelf life in perspective
lkcl has quit [Ping timeout: 260 seconds]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
JohnDoe2 has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
JohnDoe_71Rus has quit [Ping timeout: 256 seconds]
BenG83_ has quit [Quit: Leaving]
BenG83_ has joined #linux-rockchip
grw has joined #linux-rockchip
<grw> no serial output from my rk339 sapphire and nothing on usb-c when holding maskrom button
<grw> is it dead?
<micken> mmind00: yes I just used a multiplier in my delay
<micken> 1 tick / microsecond
xerpi has joined #linux-rockchip
LargePrime has joined #linux-rockchip
xerpi has quit [Quit: Leaving]
Omegamoon has joined #linux-rockchip
lkcl has joined #linux-rockchip
LargePrime has quit [Ping timeout: 260 seconds]
LargePrime has joined #linux-rockchip
alyssa has joined #linux-rockchip
<alyssa> General open-ended question for the community: What remains to be done to get Rockchip hardware, particularly based on the RK3288 and RK3399, in a state where it can be used by the non-technical general public with a mainline, blobless stack?
gnufan1 has quit [Ping timeout: 260 seconds]
<alyssa> My personal experience with a RK3288 chromebook has been that it is generally usable, but outstanding pain points include: convoluted booting procedure (with depthcharge), low distribution support, buggy eMMC and USB drivers, blobby internal wifi, non-mainlined VPU, and blobby GPUs
<alyssa> I'm curious what other people's perspectives are, since I do believe these devices will be able to play a major role in free software... if they didn't have the "blobs or nerds" dichotomy.
<alyssa> Admittedly even x86 devices aren't really there, but there's -significantly- more inertia. A person of modest technical skills can figure out how to download an ISO and go through the graphical installer, and once initial setup is done, most people can get the hang of GNOME and such no problem. The same can't be said for the RK devices quite yet, but... I can certainly help code the dream :)
gnufan has joined #linux-rockchip
<mmind00> alyssa: speaking of rk3399 chromeos-devices, booting is the same ... I think you may be able to use uboot in some form [there is uboot support for rk3288-chromeos devices at least], but I try not to touch bootloaders if I don't have to
<alyssa> "I try not to touch bootloaders if I don't have to" I think most people would agree there :)
<mmind00> alyssa: emmc is a shiny new arasan sdhci controller, we lost dwc2 and got (hopefully slightly) less buggy dwc3 ... rest is the same I think ... with the wifi attached to pcie
<alyssa> "less buggy dwc3" Do you know if it plays nice with ath9k_htc devices?
<mmind00> alyssa: what is nice is that suspend/resume is done via the ATF now [sources available], so we actually get working suspend with mainline
<alyssa> Ooo, I forgot about suspend being broken on RK3288 since boot up / shutdown is so fast :p
<alyssa> From what you're saying, RK3399 is a 'healthier' target, I suppose.
lurchi_ is now known as lurchi__
<mmind00> I don't really know about specific device compatiblities on usb though ... my kevin is permanently sitting in my boardfarm
<mmind00> alyssa: slightly but yes ... i.e. I'm not sure if somebody will spend the energie to get working (deep) suspend on rk3288 (ddr-stuff being in the way) and dwc2 is unfixeable ... so one can only try to lower the pain
<mmind00> rk3288 does have a light suspend mode, without putting the ddr in self-refresh - so that doesn't save to much
<alyssa> I don't think suspend is critical, given boot is so fast.
<alyssa> Hmm, is there work to have a normal free sw distribution (i.e. not CrOS :p) package for depthcharge systems, alleviating the need for cgpt magic and manual kernel installation?
<mmind00> alyssa: I don't really track who works on what and I replaced my stock coreboot with a netboot-only variant for my uses
<mmind00> alyssa: but in general, something like might be easiest
<mmind00> or best
<mmind00> i.e. make coreboot start into some sort of uefi environment and then the general distribution-installers should work out of the box
<hanetzer> heh. there's work being done to add grub2 as a payload supported for 'veyron' targets; works, enough to get to a grub shell, but drivers are lacking
<hanetzer> so, no typing on the chromebook keyboard, and it seems it cannot yet see emmc devices or usb
aalm has quit [Ping timeout: 260 seconds]
lkcl has quit [Ping timeout: 240 seconds]
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
lurchi__ is now known as lurchi_
<adj_> alyssa, for me, booting with the chromebook with developer mode is painful: a very noisy beep, Ctrl+D or Ctrl+U for booting from internal or USB, and specially the high risk of pressing space+enter and wiping the full internal storage
<adj_> installing a custom coreboot+payload is not for general public
<alyssa> adj_: yes, I was alluding to that re boot insanity. Despite being a butterfingers, I have not yet had the space+enter issue :p
<adj_> I installed Linux in my wife's chromebook (she doesn't like chromeos), but she didn't pay attention to the booting message and pressed space
<adj_> I needed to reinstall everything again
* alyssa notes the issue
<adj_> a friend of mine had the same experience with his chromebook and his little nephew
<alyssa> adj_: I'm partial to libreboot, of course. If I assume the target will need the boot firmware flashed anyway, we might as well just disable this "feature" in the libreboot builds to begin with.
<adj_> someone opens the lid, presses the autodestruction button and everythings wipes
<alyssa> that's concerning, yes
<adj_> opening the device for flashing the firmware is for technical people, not regular one
<adj_> other than that, the situation is maybe better than on x86-64
<alyssa> adj_: sure, but it's something generally done once in the lifetime of the machine, as opposed to the distro installation. i.e. libreboot vendors would be able to take care of that with minimum cost premium
<adj_> yes
<adj_> I'm thinking about buying an ASUS C101PA
<adj_> probably a blob is needed for wifi :(
<alyssa> I believe so. The FSF takes issue with this -- an issue I plan to discuss with them further -- but a USB wi-fi adaptor is usable instead... provided the USB drivers work ;V
<micken> I will try to get my hand on a RK3288 chromebook , when I am done with the tinker-board port.
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
JohnDoe2 has quit [Quit: KVIrc 4.9.3 Aria]
LargePrime has quit [Ping timeout: 256 seconds]
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
xerpi has joined #linux-rockchip
aalm has joined #linux-rockchip
Easyfab has quit [Quit: Leaving]
vagrantc has joined #linux-rockchip
Omegamoon has left #linux-rockchip [#linux-rockchip]
xerpi has quit [Quit: Leaving]
alyssa has left #linux-rockchip [#linux-rockchip]