ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at | Logs at | ML at
mijk has left #linux-rockchip [" - Chat comfortably. Anywhere."]
nighty has quit [Remote host closed the connection]
ganbold has joined #linux-rockchip
nighty has joined #linux-rockchip
<naobsd> is community, not Rockchip
<naobsd> we(community) don't have Android 6 SDK
<naobsd> RK3288 SDK should be able to build easily
<naobsd> fews steps
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
wzyy2 has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
beeno has joined #linux-rockchip
beeno has left #linux-rockchip [#linux-rockchip]
wadim_ has joined #linux-rockchip
lkcl has joined #linux-rockchip
lkcl has quit [Client Quit]
lkcl has joined #linux-rockchip
paulk-collins has joined #linux-rockchip
wzyy2 has quit [Remote host closed the connection]
<mrueg> naobsd: is there a "what's working / missing" for linux mainline on rk3288 anywhere?
<mrueg> not sure if the one at firefly gets updated regularly
mrjay has joined #linux-rockchip
Omegamoon has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<mrjay> anyone know if rk3288 supports hdmi cec?
<phh> mrjay: it does
<phh> though I've never seen it work anywhere
<mrjay> phh: no driver?
<phh> mrjay: there is a driver in rockchip's kernel, and there is a driver in mainline as well, though I don't think anyone has tested mainline's driver on a rockchip soc
<mrjay> i wonder if tinker board has cec support
<phh> mrjay: problem is that it needs the hdmi cec pin to be connected, and a 32k clk input
<phh> well check on the schematics what I just said ;)
<mrjay> phh: thanks
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
<mrjay> on tinker board schematic there is pin hdmicec and it seems to be connected somewhere
<mrjay> so in theory there is hdmi cec support on tinkerboard
<phh> and you checked 32k clk?
cnxsoft has quit [Remote host closed the connection]
<phh> either my pdf viewer or that schematics has real problems..., like where does RTC_CLKOUT1 come from, or where does HDMICEC goes to
<mrjay> no problem on your side ... schematic is very poor/incomplete
<phh> rk808 has a 32k output, so perhaps its 32k output is connected to rk3288's input... or not
<mrjay> well maybe someone with tinker board might test cec capability
<phh> LongChair: ^^^ ?
<paulk-collins> huh, I had never seen a full computer schematics fitting in a single A4 paper
<phh> mmmm, possibly the 4.4 kernel doesn't have cec
<phh> mrjay: one important thing missing on the schematics, is that there are two pins that are capable of hdmicec on the rk3288, we don't know which one from the schematics
<mrjay> there is brand new cec framework in mainline, but no rockchip user driver
<phh> mrjay: there is actually
<phh> mrjay: rockchip's hdmi component is DesignWave Sinopsys
<phh> CEC for this IP has been merged in 4.10
<mrjay> phh: on rk3288?
<phh> yes, but again, afaik, noone tested it
<mrjay> phh: i'll try to find code
<phh> oops, sorry, no it hasn't been merged
<phh> only proposed
<mrjay> phh: could you post link?
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
<phh> actually there is a rfcv2 of that patch
<LongChair> mrjay, phh: i didn't try CEC
<mrjay> awsome that it's baking
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
<mrjay> LongChair: if you'll have time could you test CEC?
<LongChair> I have lots of things to figure out before i come to CEC :)
<mrjay> LongChair: :)
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
mrjay has quit [Quit: Page closed]
alex_ has quit [Quit: *]
alex_ has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
alex_ has quit [Client Quit]
alex_ has joined #linux-rockchip
alex_ has quit [Remote host closed the connection]
alex_ has joined #linux-rockchip
<phh> (to try to enable cec, you can look at rk3288-box.dts, and its cec_enable, set it to 1)
<phh> (if with cec_enable to 1, the device still boots, congrats, we've done further than I ever did!)
<phh> wens: how is 4.10-rc6 on your c201? I have to disable emmc to be able to boot, else it gets stuck in gpt scan, though now boot is reliable
muvlon_ has joined #linux-rockchip
alex_ has quit [Quit: *]
alex_ has joined #linux-rockchip
<wens> phh: didn't bring it home with me, can check next week
<phh> ok np
<phh> i don't know who else has c201 here
nighty has quit [Quit: Disappears in a puff of smoke]
<Omegamoon> I need some help here... I am booting LibreElec on rk3128... it says "Started Kodi Media Center" but I have only the initial logo on screen
<Omegamoon> so I need to debug it
<LongChair> anyone knows if using mesa on rockchip makes any sense ?
<Omegamoon> I had a debug shell working on /dev/ttyFIQ before, but that one is no longer working somehow... any ideas on how to get that shell working again?
<Omegamoon> breaking my head over this :(
<phh> how about ttyS?
<Omegamoon> @phh: not sure how that would work
<Omegamoon> I'll try linking the shell console to /dev/ttyS0 to see what that brings
<phh> console=ttyS0
<wens> phh: np
nighty has joined #linux-rockchip
muvlon_ has quit [Ping timeout: 245 seconds]
LongChair has quit [Read error: Connection reset by peer]
LongChair1 is now known as LongChair
muvlon_ has joined #linux-rockchip
<alex_> @phh I'm using a C201
<phh> and you do you test mainline kernel on it?
cnxsoft has joined #linux-rockchip
<alex_> I tried running 4.10-rc5 which was a bit broken due to the eMMC problems, one of the patches made it better but not fully
<phh> right, mostly same state as me
<alex_> I'm using 4.9 atm from linux-armv7-chromebook packaged from arch arm (i had to create my own image with just one dtb as the one with multiple does not boot correctly)
cnxsoft has quit [Remote host closed the connection]
<alex_> i also had some wifi issues with 4.10-rc5, just didn't have time to debug everything
cnxsoft has joined #linux-rockchip
LongWork has joined #linux-rockchip
<Omegamoon> @phh: do you know if ttyFIQ0 could be conflicting with ttyS0 in any way?
<phh> that's most likely, AFAIK ttyFIQ is just ttyS with irq remapped as FIQ
<Omegamoon> I have serial console output, but still no
<phh> but I could be wrong
<Omegamoon> *still no shell
<Omegamoon> I'll disable FIQ debugger for now
athidhep has joined #linux-rockchip
LongWork has quit [Ping timeout: 255 seconds]
cnxsoft has quit [Quit: cnxsoft]
beeno has joined #linux-rockchip
<beeno> hello everyone
<beeno> can someone perhaps help with getting rockhip linux running on a ugoos UT3S
JohnDoe_71Rus has joined #linux-rockchip
anubis has joined #linux-rockchip
anubis is now known as Guest19870
<Guest19870> Hi, just a random question; does the new Thinker board has a decent CPU to use iperf3 as a client/server? I'm looking at using this board for a bandwidth monitor
Myy has joined #linux-rockchip
wadim_ has quit [Remote host closed the connection]
Guest19870 has quit [Quit: Page closed]
<LongChair> Would anyone have some good doc link about DRM API ?
_whitelogger has joined #linux-rockchip
<LongChair> Myy: yeah last one is teh doc from libdrm
<LongChair> but that's all i have found. Very odd that such an API doesn't have more doc
<Myy> Well, given that everyone uses X11 with DRI drivers, most people do not really care about that API. Maybe looking at projects like "kmscon" might give you an idea on how to use it. :/
<LongChair> yeah
<LongChair> Myy: i have heard though that drm is likely the only way to get a proper 4K playback
<LongChair> Do we know how many overlays RK3288 can handle by the way ?
<Myy> While this might be possible, that would be highly implementation specific. You'll have to look at the Rockchip DRM driver and see which IOCTL it provides, and understand how to use them. That part will be barely documented, however :/
<LongChair> Myy : i think gst uses drm as a sink
<LongChair> it just uses plain drm afaik, nothing driver specific
<LongChair> its just harder to read when there is no doc to understand what drm api is supposed to do :)
<Myy> Well, I got some examples about how to create OpenGL cubes using pure DRM as a backend
<Myy> But that's it
<Myy> However, maybe people on the DRM irc channels might provide you better answers
<Myy> "Mesa developers hang out in"
<beeno> Myy, thanks for that. It's at least something to try. All I could get working this far was that it activates hdmi and just sits there with nothing on screen. Is that something you've seen before?
<Myy> I've seen that when the DRI gets enabled but the programs then borks up for some reason.
<Myy> *DRM
<Myy> Which happened when playing with OpenGL for example. KMS prepare the screen and then some syntax errors in the shaders make OpenGL unable to do anything and you get a nice black screen with nothing...
<Myy> That said, in order to test kmscube, you'll need Wayland/DRM drivers. X11 drivers won't have GBM related symbols.
<Myy> If you can run kmscube, you can also try
<beeno> If I have only the RK3288UbootLoader_V2.30.06.bin on eMMC, should it load up uboot and display something?
<Myy> UBoot won't display anything, it does not have HDMI drivers. You can only catch U-Boot messages through serial communication (UART<->USB), which requires to open the box.
<beeno> ok, I noticed that with the Odroid. I'm not so sure this ut3s would have a connector for uart. I'll have to open it I guess and see
<Myy> Well, I got told yesterday that all Rockchip chips have UART connectors. I can only assert that for MiQi devices though.
<beeno> You saying the MiQi and ugoos are the same product?
<Myy> No. I'm just saying that I heard that most Rockchip boards have UART connectors.
<beeno> Do you know at what times people generally appear in this chat room? I'm on GMT+2
<Myy> Mostly the morning then
<Myy> 5H~15H if you're GMT+2
<beeno> On that MiQi website "After enter maskrom mode, on your host side, $sudo upgrade_tool db rk3288_boot.bin". So in this case they need you to do that over uart as well?
vagrantc has joined #linux-rockchip
<beeno> strange because I had this channel open the whole day and asked a question this morning, but not a word was said until you replied to LongChair
<Myy> You might have more luck during the week-ends, I guess.
<Myy> You don't need UART for using upgrade_tool
<Myy> Just connect the system to your PC through USB
<Myy> It's just that without UART, you cannot see UBoot messages and kernel messages. If you flash the firmware and all goes well, you won't need UART.
<beeno> and that brings up another issue I'm having. I tried running upgrade_tool on x64 ubuntu and seems it won't run. Should I be using a 32bit version?
<Myy> If something goes wrong, however, you'll need it to know what exactly is going wrong.
<Myy> I don't think so. I used in on a 64 bits Gentoo and everything went fine (the first time)
<beeno> yeah it's strange, always says the file (program) can not be found
<Myy> That said, you really need to follow upgrade procedures with upgrade_tool, else half of the commands won't work.
<Myy> When executing it ?
<beeno> yes, just trying to run it in the terminal. I can see it and the auto complete even finds it, but it won't run
<beeno> and it is +x
<Myy> Well, two things then :
<Myy> 1) Make sure the current partition hosting the file does not have "noexec"
<Myy> 2) Do readelf -a upgrade_tool and have a look at the first headers
<Myy> Most notably...
<Myy> [Requesting program interpreter: /lib64/]
<Myy> The program interpreter line
<Myy> readelf -l upgrade_tool might be more useful
<Myy> Have a look at the "program interpreter" line and check if the file specified exists
<Myy> Worst case, install strace and do "strace ./upgrade_tool", copy the output on pastebin, ghostbin, whatever, ... and copy the link here
<beeno> Mine wants /lib/
<Myy> Should be available, no ? ls -l /lib/ returns something ?
<beeno> I don't seem to have one
<Myy> If it returns nothing, you might need libc6-i686
<Myy> or i386
<beeno> ok makes sense. now to try install that :)
<Myy> Alright, then !
<beeno> ah ok now it's asking for the libstdc++ as well. so basically it just wants the 32bit support
<Myy> Yup :)
<Myy> There might be a way to recompile it for 64 bits system but I guess that installing 32bit support will be way faster.
<beeno> ok my upgrade_tool is now working at least. Thanks for the tips!
<Myy> You're welcome ! Note that upgrade_tool requires specific procedures. Some commands will not work before others have been sent, etc...
<beeno> I plan to use it with the build/ script provided. all the other scripts seemed to work fine
<beeno> even the version that copies to the SD instead, but as I said, it doesn't work
<beeno> when I manually copied some initial uboot files to the emmc, it did result in the hdmi activating and there it stopped. So I was under the impression that I should be seeing something on screen
<beeno> so clearly doing it manually isn't something I should be doing but I think without the com port access you're not going to get anything done
<beeno> just concerning me that using the automated scripts resulted in a SD that didn't boot at all
<beeno> so I wonder if trying to run the 3288evb or firefly config should even boot at all?
<Myy> Well, if the HDMI got activated, that's already something. You might want to connect it via Ethernet to your computer and use Wireshark to analyse network activity, just in case.
<beeno> I think I did try a firefly img, and that did come up with linux loading messages but it got stuck before getting to a login prompt
<Myy> Some linux images try to scan for a network for a veeeeerrryyy long time before continuing the boot process
<beeno> hmmm, would you suggest I just unplug the network card?
<Myy> So keeping it connected on the network might provide some informations about the boot process
<beeno> hmmm, would you suggest I just unplug the network cable
<Myy> I would suggest to try running a small dhcp server on a machine and connect it to the machine. Or at least connect it to your computer and snoop network activity. Some boot network management scripts are very dumb, to say the least.
<Myy> Even without network cable, they might just wait a few minutes "just in case".
<beeno> Which boards do you use? I'm having to find a product to use for a 3d display. The RK3288 is pretty good performance but seems finding something that comes in a retail type box while getting good support is not that easy
<Myy> I have a MiQi board actually.
<Myy> I got the 3D working with DRM and Wayland using mainline kernels, while others got it working on X11 using rockchip 4.4 kernels.
<beeno> and what has been your experience in getting it to run linux
<beeno> do you think you can use fbdev?
<Myy> It was fun. But I also got a lot of troubles with some units, due to poor upgrade_tool skills
<Myy> I was able to run Mali OpenGL fbdev samples
<Myy> However, I'm currently focused on playing with DRM/KMS now.
<Myy> (and evdev for input management)
<beeno> I think wayland would be something to try if it doesn't provide any compositing overhead
<beeno> Do you think you can get vulkan working on there yet?
<Myy> Actually I'm actually playing with DRM without wayland. Meaning direct OpenGL from the console. I'll play with Wayland when I got everything sorted out.
<Myy> If Rockchip provide Vulkan enabled Mali drivers, yeah
<Myy> Else it will require a serious amount of engineering.
<beeno> well clearly they would need to come from arm. Their website seem to say that it's there or coming, I've not seen any files for it
<Myy> Yeah. Currently only Samsung devices seem to have them. Maybe some Huawei too.
<Myy> However, this is still kept in close doors. They might need to polish it up, I don't know.
<beeno> I'll be happy for now just to get EGL3.1. I had to try downgrade my player to EGL2.0 for the Mali450 and found it just wasn't worth it. The 400/450 has stupidly low precision in fragment shaders
<Myy> Well, I was able to run the fbdev OpenGL ES 3.1 and 3.2 examples
<Myy> Mostly the compute shaders one and the occlusion queries ones.
<beeno> I have no experience with DRM. I wonder how you create a surface
lkcl has quit [Ping timeout: 255 seconds]
<Myy> Currently, I just made a copy of the simple "kmscube" example and slightly arrange it. However it's "fullscreen" only, ATM.
<beeno> excellent. Is this your own git repo?
<Myy> Still, DRM seems to be like "Acquire the connected displays" and then GBM seems to help you do the rest.
<Myy> Yup !
<Myy> But it was forked from ...
<Myy> You might also be interested by ...
<Myy> I didn't try it though ( ̄〜 ̄)
<beeno> funny enough I've come across that one too some time ago. not sure why
<beeno> so with your DRM effort, did you get proper vsync?
<Myy> Yes. When playing with glmark2, I always got 60 fps.
<Myy> While on X11, when I got it working a few times, I got 100+ fps on rotating cubes, DRM/Wayland tests stayed at 60 fps
<Myy> So there's synchronisation enabled. However the scenes are too simple to really detect screen tearing.
<Myy> patched for Mali drivers
<Myy> I should commit another patch though... Mali drivers seems to confuse XRGB8888 for RGB with no alpha channel.
<beeno> well I need to get 4 quarter screen videos playing in 1080p, that will be enough of a test :)
<Myy> So if EGL chooses a configuration with Alpha enabled, you get a bad match. So you need to use ARGB888 instead
<beeno> and at 60fps
<Myy> Well, note that you can already test KMS / OpenGL on your system, if you system use Mesa drivers
<beeno> I was actually able to manage that on the odroid c2 with a mali450. I see no reason why the rk3288 won't do that easily
<Myy> Well, if the project doesn't use X11, I can give it a test on my MiQi !
<beeno> of course, without even a working system, I'm not getting to my application even...
<beeno> how do you rate the MiQi for build quality?
<Myy> Well, some people made extensive tests here...
<beeno> I have the usb-uart from odroid, I wonder if it would be compatible
<Myy> The metal case is quite cheap but system feels solid for the moment. I don't have any complaint hardware wise, at the moment.
<Myy> Should be
<Myy> MiQi systems only require 3 pins for UART.
<Myy> Green, white and black.
<beeno> my cable has 4, black, green, blue and red
<Myy> Mine too. I just don't use the red one
<beeno> does it have a 4 pin plug?
<Myy> 3 pin plug, yeah.
<Myy> The three ones, on the upper left
<beeno> strange that I never saw this product. is it fairly new?
<Myy> Quite new, yeah. Most of the kickstarters were unpopular though.
lkcl has joined #linux-rockchip
<Myy> Still, it's a nice board for software development.
<beeno> ok unfortunately I'll have to sign off for today. will you be around tomorrow?
<Myy> I might be, yeah.
<beeno> ok cool. I think we may have lots to talk about :)
<Myy> Meanwhile, if you need a kernel for RK3288 devices, you can try this one
<Myy> Beside the DTB, it should be usable with any RK3288 board.
<beeno> yeah, I'll try that tomorrow morning. hope I can get at least the kernel loading
<Myy> Alright !
<Myy> See you then !
<beeno> thanks, till then, cheers.
<Myy> Time for dinner
Cooleo has joined #linux-rockchip
Cooleo has quit [Client Quit]
<Omegamoon> @beeno, still here?
<Omegamoon> there are serial pads on the Ugoos UT3S
<Omegamoon> I soldered a serial console on mine last weekend
<Myy> Well, if you put photos/tutorials URL here, he might be able to catch them through the IRC logs
<Myy> Nice ! Bookmarked
<Myy> Well, that's it for today. See you everyone !
Myy has quit [Quit: Leaving]
premoboss has joined #linux-rockchip
beeno has quit [Ping timeout: 260 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc 4.9.2 Aria]
Omegamoon has left #linux-rockchip [#linux-rockchip]
premoboss has quit [Ping timeout: 255 seconds]
lkcl has quit [Ping timeout: 240 seconds]
nighty has quit [Quit: Disappears in a puff of smoke]
paulk-collins has quit [Quit: Leaving]