ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
sams has quit [Quit: priatno.]
sams has joined #armbian
<DC-IRC> <drose> how would i go about adding this patch to my build for rock 5a?
<DC-IRC> <drose> also will apt upgrade break the patch?
pablocastellanos has quit [Server closed connection]
pablocastellanos has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
<DC-IRC> <spooky8086> I know the 5A has had eMMC issues but I have not followed it closely, so I dont know if this patch would solve anything on the 5A. Anyway you simply add the pinctrl as shown below to the device tree.
<DC-IRC> <spooky8086> ```diff
<DC-IRC> <spooky8086> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts b/arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts
<DC-IRC> <spooky8086> index 487a5a11f24d..030002187365 100644
<DC-IRC> <spooky8086> --- a/arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts
<ArmbianHelper> - a/arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts [en~>en]
<DC-IRC> <spooky8086> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts
<DC-IRC> <spooky8086> @@ -875,6 +875,12 @@ bt_wake_host: bt-wake-host {
<DC-IRC> <spooky8086> };
<DC-IRC> <spooky8086> };
<DC-IRC> <spooky8086>
<DC-IRC> <spooky8086> + emmc {
<DC-IRC> <spooky8086> + emmc_data_strobe: emmc-data-strobe {
<DC-IRC> <spooky8086> + rockchip,pins = <2 RK_PA2 1 &pcfg_pull_down>;
<DC-IRC> <spooky8086> + };
<DC-IRC> <spooky8086> + };
<DC-IRC> <spooky8086> +
<DC-IRC> <spooky8086> hym8563 {
<DC-IRC> <spooky8086> rtc_int: rtc-int {
<DC-IRC> <spooky8086> rockchip,pins = <0 RK_PB0 RK_FUNC_GPIO &pcfg_pull_up>;
<DC-IRC> <spooky8086> ```
<DC-IRC> <spooky8086> I know the 5A has had eMMC issues but I have not followed it closely, so I dont know if this patch would solve anything on the 5A. Anyway you simply add the pinctrl as shown below to the device tree.
<DC-IRC> <spooky8086> https://pastebin.com/7Ayc0Tv4
<DC-IRC> <spooky8086> I know the 5A has had eMMC issues but I have not followed it closely, so I dont know if this patch would solve anything on the 5A. Anyway you simply add the pinctrl as shown below to the device tree.
<DC-IRC> <spooky8086> https://pastebin.com/7Ayc0Tv4
zeemate has quit [Ping timeout: 256 seconds]
crabbedhaloablut has quit []
sunshavi has quit [Remote host closed the connection]
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 256 seconds]
juri__ has joined #armbian
archetech has quit [Quit: Konversation terminated!]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 276 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 256 seconds]
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian
juri_ has joined #armbian
juri__ has quit [Ping timeout: 255 seconds]
archetech has joined #armbian
juri__ has joined #armbian
archetech has quit [Remote host closed the connection]
juri_ has quit [Ping timeout: 276 seconds]
archetech has joined #armbian
juri_ has joined #armbian
juri__ has quit [Ping timeout: 260 seconds]
juri_ has quit [Ping timeout: 276 seconds]
juri_ has joined #armbian
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 276 seconds]
juri__ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 260 seconds]
juri_ has joined #armbian
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 276 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 276 seconds]
jclsn has quit [Ping timeout: 245 seconds]
jclsn has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 256 seconds]
archetech has quit [Quit: Leaving]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 276 seconds]
juri_ has quit [Ping timeout: 256 seconds]
juri_ has joined #armbian
archetech has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 276 seconds]
juri__ has quit [Ping timeout: 276 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 252 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 255 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri__ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has joined #armbian
juri__ has quit [Ping timeout: 255 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri__ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has joined #armbian
juri__ has quit [Ping timeout: 252 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 276 seconds]
p0g0__ has joined #armbian
ikmaak2 has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
pablocastellanos has quit [*.net *.split]
kolla has quit [*.net *.split]
p0g0_ has quit [*.net *.split]
ikmaak has quit [*.net *.split]
hbbs has quit [*.net *.split]
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
pablocastellanos has joined #armbian
juri_ has quit [Ping timeout: 276 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
crabbedhaloablut has joined #armbian
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 252 seconds]
juri_ has quit [Ping timeout: 276 seconds]
juri_ has joined #armbian
alekksander has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri__ has joined #armbian
juri__ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
<DC-IRC> <drose> Is this during the build or after build via armbian-config?
juri__ has quit [Ping timeout: 255 seconds]
jantones has quit [Quit: Leaving]
juri_ has joined #armbian
juri_ has quit [Ping timeout: 268 seconds]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 276 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
zeemate has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
stipa has quit [Quit: WeeChat 4.1.1]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
clever has quit [Server closed connection]
juri__ has quit [Ping timeout: 252 seconds]
clever has joined #armbian
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 276 seconds]
juri__ has quit [Read error: Connection reset by peer]
juri_ has joined #armbian
juri__ has joined #armbian
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
juri__ has joined #armbian
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #armbian
juri__ has quit [Ping timeout: 264 seconds]
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #armbian
lyri has quit [Ping timeout: 276 seconds]
lyri has joined #armbian
<DC-IRC> <viraniac> Tested RC image on vim1s. Apart from the known issues, disconnecting wifi crashes the device. Also bluetooth doesn't work. Raised Jira for the same and will work on fixing them. Now testing vim4 images
stipa has joined #armbian
<DC-IRC> <viraniac> Vim4 also seems to have the same bugs. No bluetooth and disconnecting wifi crashes the device.
<DC-IRC> <clever___> broadcom is the only platform i'm heavily familiar with
<DC-IRC> <clever___> but i dont know how you would do 3d hdmi on broadcom
<DC-IRC> <tenkawa42> @clever___ yeah it was a old feature the 2711 "could" do.... apparently it got removed/updated out in an eeprom
<DC-IRC> <tenkawa42> It used the dual outputs
<DC-IRC> <clever___> eeprom updates shouldnt have any impact on hdmi
<DC-IRC> <tenkawa42> thought you may had been famuliar with it
<DC-IRC> <tenkawa42> thought you may had been familiar with it
<DC-IRC> <tenkawa42> eeprom updates change base code of the soc so of course it could affect output availability to the OS layer
<DC-IRC> <clever___> the only thing the pi4 eeprom does is bring the lpddr4 online and load start4.elf
<DC-IRC> <clever___> i have seen zero trace of microcode
<DC-IRC> <tenkawa42> EEPROM contains essential system configuration and boot code that is responsible for initializing the Raspberry Pi hardware
<DC-IRC> <clever___> dram is essential 😛
<DC-IRC> <tenkawa42> "hardware".... hdmi
<DC-IRC> <clever___> the linux kms drivers are in full charge of hdmi, once booting has completed
<DC-IRC> <tenkawa42> Once booting is complete... but if it has been changed/reordered it could be disabled
<DC-IRC> <tenkawa42> they've done it before
<DC-IRC> <clever___> do you have a link to 2 versions, where they changed it?
<DC-IRC> <clever___> before&after
<DC-IRC> <tenkawa42> Not handy (it was years ago) and I can't even remember what it was related to but there was something I can vaguely remember from the early days
<DC-IRC> <clever___> in the early days, the eeprom didnt even touch hdmi, and it was start4.elf that did hdmi init
<DC-IRC> <clever___> only with the addition of the hdmi diagnostics screen, did the eeprom begin touching hdmi
<DC-IRC> <tenkawa42> Ahh... found I think what clee needs
<DC-IRC> <tenkawa42> He needs to read up on the Vulkan work
<DC-IRC> <tenkawa42> @c133 apparently the 3d supposedly works with this driver
<DC-IRC> <clever___> vulkan and opengl are just ways of driving the 3d core and generating a 2d image
<DC-IRC> <clever___> if you want 3d hdmi, you generate a pair of 2d images as the output
<DC-IRC> <clever___> how you get both out the hdmi, is another problem, unrelated to vulkan/opengl
<DC-IRC> <clever___> thats my understanding of things
<DC-IRC> <tenkawa42> Need to have a renderer first... so he needs to see if that will even work
<DC-IRC> <clever___> yeah
<DC-IRC> <clever___> oh, but if its a 3d bluray movie....
<DC-IRC> <tenkawa42> if it won't no need to try the output
<DC-IRC> <clever___> its already been rendered, its already a pair of 2d images
<DC-IRC> <tenkawa42> I don't think these are pre rendered
<DC-IRC> <tenkawa42> That's one of the reasons this is so tricky (we were discussing this on weekly chat last night)
<DC-IRC> <clever___> is a 3d bluray movie just a pair of 2d video streams? one per eye?
<DC-IRC> <clever___> or is it 3d models??
<DC-IRC> <tenkawa42> 2 vid streams I think
<DC-IRC> <clever___> then as you decode that, you get a pair of 2d images, for each frame
<DC-IRC> <clever___> fully rendered
<DC-IRC> <clever___> and you just have to feed both 2d images to the display
<DC-IRC> <tenkawa42> he'll have to confirm..
archetech has quit [Remote host closed the connection]
archetech has joined #armbian
archetech has quit [Client Quit]
archetech has joined #armbian
<DC-IRC> <c133> it’s a main stream with additional metadata embedded for the second eye
<DC-IRC> <clever___> and what kind of data is in that metadata stream?
<DC-IRC> <c133> my understanding is that it’s a “delta” for each frame to reconstruct the right eye output based on the full frame from the left eye
<DC-IRC> <clever___> ah, i can sort of see that, they will usually be very similar
<DC-IRC> <c133> anyway the main thing is
<DC-IRC> <c133> the Pi video output needs to actually signal to the television “hey turn on 3D mode”
<DC-IRC> <clever___> once a 3d aware decoder is done its job, it will still be a pair of 2d images in the end
<DC-IRC> <clever___> yeah, and then you have to also agree on how that 3d signal is sent over hdmi
<DC-IRC> <c133> yep. the specific mode I’m looking for is called “frame packed” mode
<DC-IRC> <clever___> i can imaging ~3 ways to send 3d over hdmi
<DC-IRC> <clever___> 1: just left+right, composite them as you scan-out, and send a double-wide hdmi stream
<DC-IRC> <clever___> 2: top+bottom, same thing
<DC-IRC> <clever___> 3: treat it like interlaced, tweak the blanking intervals so the left/right differ
<DC-IRC> <clever___> the difference betwee 2&3 is if you have a vsync between the 2 images
<DC-IRC> <clever___> the difference betwee 2&3 is if you have a VBI between the 2 images
<DC-IRC> <clever___> *looks*
<DC-IRC> <clever___> ```c
<DC-IRC> <clever___> vc4_firmware_kms.c: * switch(mode->flag & DRM_MODE_FLAG_3D_MASK) {
<DC-IRC> <clever___> vc4_firmware_kms.c: * case DRM_MODE_FLAG_3D_NONE:
<DC-IRC> <clever___> vc4_firmware_kms.c: * case DRM_MODE_FLAG_3D_FRAME_PACKING:
<DC-IRC> <clever___> vc4_firmware_kms.c: * case DRM_MODE_FLAG_3D_FIELD_ALTERNATIVE:
<DC-IRC> <clever___> vc4_firmware_kms.c: * case DRM_MODE_FLAG_3D_LINE_ALTERNATIVE:
<DC-IRC> <clever___> vc4_firmware_kms.c: * case DRM_MODE_FLAG_3D_SIDE_BY_SIDE_FULL:
<DC-IRC> <clever___> ```
<DC-IRC> <clever___> i do see a reference to frame-packing in the fkms driver
<DC-IRC> <clever___> ```c
<DC-IRC> <clever___> /*
<DC-IRC> <clever___> * FIXME: To implement
<DC-IRC> <clever___> * switch(mode->flag & DRM_MODE_FLAG_3D_MASK) {
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_NONE:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_FRAME_PACKING:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_FIELD_ALTERNATIVE:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_LINE_ALTERNATIVE:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_SIDE_BY_SIDE_FULL:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_L_DEPTH:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_L_DEPTH_GFX_GFX_DEPTH:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_TOP_AND_BOTTOM:
<DC-IRC> <clever___> * case DRM_MODE_FLAG_3D_SIDE_BY_SIDE_HALF:
<DC-IRC> <clever___> * }
<DC-IRC> <clever___> */
<DC-IRC> <clever___> ```
<DC-IRC> <clever___> but its not implemented!
<DC-IRC> <clever___> @tenkawa42 assuming those constants are key, they have never been functional in the kms or fkms driver, according to `git log`
<DC-IRC> <clever___> i'm not sure how this could have ever worked in the past
<DC-IRC> <clever___> my only thought, is that `omxplayer` may have had a direct connection into the dispmanx stack, and was able to do 3d there
<DC-IRC> <clever___> and with the transition to kms, that has been lost
e3ef13f4ff44 has left #armbian [WeeChat 3.5]
<DC-IRC> <c133> my understanding is that this specific feature has been broken on Pi4 since the start, but it USED to work on older software releases for Pi3. probably before KMS, yeah.
<DC-IRC> <tenkawa42> Will be interesting to see if it can work on the 2712
martinayotte has quit [Ping timeout: 256 seconds]
<DC-IRC> <Werner> Please use a pastebin service for longer stuff. IRC users will appreciate. @clever___
<DC-IRC> <clever___> ah yeah, i keep forgetting about the irc bridge
<DC-IRC> <clever___> it will probably work on pi3, and maybe even pi4, if you just flip over to fkms, and use something based on dispmanx, but thats been deprecated for a while now
kcz has quit [Quit: kcz]
kcz has joined #armbian
lyri has quit [Remote host closed the connection]
buzzmarshall has joined #armbian
martinayotte has joined #armbian
<DC-IRC> <drose> heres my dts file, but im getting unable to parse input tree, any ideas?
<DC-IRC> <drose> ``` /dts-v1/;
<DC-IRC> <drose> /plugin/;
<DC-IRC> <drose> &emmc {
<DC-IRC> <drose> status = "okay";
<DC-IRC> <drose> bus-width = <8>;
<DC-IRC> <drose> no-sdio;
<DC-IRC> <drose> no-sd;
<DC-IRC> <drose> non-removable;
<DC-IRC> <drose> max-frequency = <200000000>;
<DC-IRC> <drose> mmc-hs400-1_8v;
<DC-IRC> <drose> mmc-hs400-enhanced-strobe;
<DC-IRC> <drose> full-pwr-cycle-in-suspend;
<DC-IRC> <drose> pinctrl-names = "default";
<DC-IRC> <drose> pinctrl-0 = <&emmc_data_strobe>;
<DC-IRC> <drose> };
<DC-IRC> <drose> emmc_data_strobe: emmc-data-strobe {
<DC-IRC> <drose> rockchip,pins = <2 RK_PA2 1 &pcfg_pull_down>;
<DC-IRC> <drose> };
<DC-IRC> <drose> ```
lyri has joined #armbian
<DC-IRC> <spooky8086> Take a look at this commit, its all you need to modify
<DC-IRC> <drose> ``` /dts-v1/;
<DC-IRC> <drose> /plugin/;
<DC-IRC> <drose> &emmc_data_strobe: emmc-data-strobe {
<DC-IRC> <drose> rockchip,pins = <2 RK_PA2 1 &pcfg_pull_down>;
<DC-IRC> <drose> };```
<DC-IRC> <drose> so would this be the appropriate dts file?
<DC-IRC> <spooky8086> I have no idea what file that is, you would need to modify `arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts`
<DC-IRC> <drose> this would be a dts overlay, dont really wanna modify the kernel and would rather add this using armbian-add-overlay
<DC-IRC> <spooky8086> Oh that makes sense
<DC-IRC> <drose> im not sure you can just modify that file.. as i believe it needs to be compiled? not sure
<DC-IRC> <spooky8086> It does need to be compiled, the overlay should be simple enough. give me a moment and i can make something up
<DC-IRC> <drose> thank you 🙂
<DC-IRC> <drose> have a production line and a bunch of our devices went out already with the latest chips, the forsee ones seem to be fine
lyri has quit [Ping timeout: 256 seconds]
lyri has joined #armbian
lyri has quit [Ping timeout: 264 seconds]
lyri has joined #armbian
<DC-IRC> <spooky8086> You can try this as an overlay:
<DC-IRC> <drose> hmm still getting the same error that syntax error, unable to parse input tree
<DC-IRC> <drose> i can try and compile with dts and move to overlays file? but im p sure thats what amrbian add overlay does anyway
<DC-IRC> <drose> maybe need an apt update/upgrade?
<DC-IRC> <spooky8086> Im not familiar with the armbian-add-overlay process, i normally will modify the kernel myself and build it that way
<DC-IRC> <drose> gotcha
<DC-IRC> <drose> okay lemme try and compile
<DC-IRC> <drose> if you modify the kernel what happens when you run apt upgrade?
<DC-IRC> <spooky8086> Hmm the overlay should work, are you using this file?
archetech has quit [Quit: Konversation terminated!]
<DC-IRC> <spooky8086> Sorry, i have no idea, it will build just fine when compiling the kernel
<DC-IRC> <drose> all good!
archetech has joined #armbian
<DC-IRC> <drose> do you have a reference for compiling the a custom kernel when building an os?
alekksander has quit [Quit: Konversation terminated!]
alekksander has joined #armbian
buzzmarshall has quit [Quit: Konversation terminated!]
Lucanis has quit [Quit: Leaving]
Lucanis has joined #armbian
crabbedhaloablut has quit []
lanefu has quit [Ping timeout: 260 seconds]