lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC>
<minerva> Okay, I can reduce the speed of its a dts thing
<DC-IRC>
<minerva> What I don't understand is why the old armbian kernel 5.10 does run just fine from emmc (so, it's mounted properly there)
<DC-IRC>
<minerva> There was any change on the dts? I doubt that.
<DC-IRC>
<minerva> Do you also think it's a dts thing @MacKahan
<DC-IRC>
<minerva> If so, I can attemp to reduce the frequency of the emmc on the dtb.
<DC-IRC>
<tenkawa42> I compared 2 dts and they were different
<DC-IRC>
<tenkawa42> even between kernel versions
<DC-IRC>
<tenkawa42> for the same target
<DC-IRC>
<Tonymac32> I would reduce the speed as a bandaid. 100 MHz should do it
<DC-IRC>
<tenkawa42> There was a few changes in the dts for 6.1
<DC-IRC>
<tenkawa42> I didn't try yet to move it forward to 6.2 and see if that helps.. going to do that tomorrow
<DC-IRC>
<tenkawa42> ... since mainline has a lot of changes there and that should be useable
<DC-IRC>
<minerva> I tried that, but didn't work out 🥲
<DC-IRC>
<minerva> Hopefully that was the entry of the emmc...
<DC-IRC>
<minerva> @MacKahan
<DC-IRC>
<minerva> I will check the old system dtb to check if there is any significant diff
<DC-IRC>
<Tonymac32> Bus width 04 says it's the SD card 😜
<DC-IRC>
<minerva> Fuck
<DC-IRC>
<minerva> Haha
<DC-IRC>
<minerva> Which bus should be the emmc. I changed both entries anyway
<DC-IRC>
<minerva> Just in case
<DC-IRC>
<mariob> sdhci
<DC-IRC>
<Tonymac32> I haven't caught up to how it's doing it in the first place, maybe rpardini could help
_whitelogger has joined #armbian-rockchip
<DC-IRC>
<rpardini> Yeah fire away, I've had my a$$ whopped by that code so many times I can somewhat wiggle around it these days
<DC-IRC>
<c0rnelius77> Basically I just wanna know how to bypass it. Mainline u-boot for RK can handle the `rkbins / atf` on it's own by either using the correct naming scheme `atf-bl31` and dropping the files into the source during compilation and by using exports `export ROCKCHIP_TPL="rk3568_ddr_1560MHz_v1.13.bin"`. The patch set I use for v2022.07 also works this way, but the naming scheme is different.
<DC-IRC>
<rpardini> For that, in the board file....
<DC-IRC>
<rpardini> 1. Remove rockchip64's `uboot_custom_postprocess`. In the board file, set up a `post_family_config` hook that does `unset uboot_custom_postprocess`
<DC-IRC>
<rpardini> 2. Implement the juggling that you do need, in the board file, by defining `pre_config_uboot_target` and (maybe?) `post_uboot_custom_postprocess` hooks, that do what you need.
<DC-IRC>
<rpardini> 3. probably some UBOOT_TARGET_MAP arm-twisting
<DC-IRC>
<c0rnelius77> k. i'll play with it.
<DC-IRC>
<rpardini> Good luck, let me know. I've the odroidm1 to test. Would be very interested in straight SPI -> NVMe boot, sans any SD/eMMC. 😉
<DC-IRC>
<speakertomeat> Good morning all on the GMT+4 and eastern side.
<DC-IRC>
<speakertomeat> Good morning all on the GMT+4 and western side.
<DC-IRC>
<speakertomeat> Question before I go on trying my hand at butchering asound.conf would anybody perchance have an existing asound.conf file for an orange pi 4 lts or similar board with 3.5mm and hdmi audio out to send audio to both outs by default that you could share please?
<DC-IRC>
<kwiboo> I have pending patches on mailing list and local pending patches to add support for M1 with working SPI -> NVMe or SATA boot on M1, they should hit the list this weekend, I keep a few test builds of 2023.07-rc4 at https://github.com/Kwiboo/u-boot-build/actions/runs/5248877472 if there is any interest
<DC-IRC>
<tenkawa42> @minervarhatesthepi you had any luck in your testing.. I'm going to try some more stuff here in a bit
<DC-IRC>
<speakertomeat> The u-boot in our boards goes into the SoC, right?
<DC-IRC>
<Tonymac32> No it is stored on the SD card, emmc, or SPI flash
<DC-IRC>
<.richn> you have to fdisk the emmc
<DC-IRC>
<.richn> [2:36 PM]
<DC-IRC>
<.richn> sometimes you have to wipe and make a single partition on the emmc to get it to show u in the install script
<DC-IRC>
<.richn> I havehad the issue
<DC-IRC>
<.richn> same with nvme
<DC-IRC>
<speakertomeat> At the start of the device? like old BIOS style on pc?
<DC-IRC>
<speakertomeat> Because I don't think the SoC will have fs drivers to read off a partition.. or does it?
<DC-IRC>
<Tonymac32> Yeah it's offset from the start of the device
<DC-IRC>
<Tonymac32> The SoC pulls in a fixed number of bytes and executes it
<DC-IRC>
<speakertomeat> Nod
<DC-IRC>
<Tonymac32> There is a tiny amount of code but in to do that access
<DC-IRC>
<speakertomeat> And I guess stuff like boot.scr which I just discovered, and which seems to be created from boot.cmd, gets read and used by u-boot
<DC-IRC>
<speakertomeat> it's two staged like grub?
<DC-IRC>
<.richn> i dont know how many boards use grub currently
<DC-IRC>
<.richn> most just efi and or uboot
<DC-IRC>
<Tonymac32> Well we're talking from power on, the staging is an example
<DC-IRC>
<Tonymac32> So yeah, the built in code pulls the few kb into the built-in sram and executes it, that brings up the power/cores/specific peripherals to load the "real" bootloader into RAM
<DC-IRC>
<speakertomeat> Including fs? or stage two is at an offset as well?
<DC-IRC>
<Tonymac32> Hang on, it's vendor/SoC specific
<DC-IRC>
<speakertomeat> Separate question, I see the only way to set display mode is via u-boot using either edid or forced? so if my display cable is off or device off when booted, the only recourse if I don't want to force a resolution (for being able to change devices) is somehow detect if a resolution/communication was established, and do a reboot loop until it is? and is this possible at all? maybe via /sys ?
<DC-IRC>
<monkablyat> off-topic : if you want to disguise your identity for whatever reason with a new account then you should better pay attention to the screenshots that could reveal your real identity, just as a little security note for next time 🍻 hope you are doing well buddy and have a nice day
<DC-IRC>
<speakertomeat> In this case I care more about x11 than bootlogo and even than plymouth so I wonder if xrandr can react to a post-boot monitor connection and configure accordingly
<DC-IRC>
<minervarhatesthepi> Hahahha clever guy
<DC-IRC>
<minervarhatesthepi> I just want my pbp alive again
<DC-IRC>
<minervarhatesthepi> But I am leaving the ecosystem, that's why
<DC-IRC>
<rpardini> Damn Salva _caught in the act_ 🤣
<DC-IRC>
<speakertomeat> And the answer is, I can use xrandr.
<DC-IRC>
<.richn> wayland is wrander
<DC-IRC>
<.richn> and others use arander
<DC-IRC>
<.richn> you can boot and wipe the emmc
<DC-IRC>
<.richn> fdisk
<DC-IRC>
<speakertomeat> Hmmm I need to check if I'm using wayland
<DC-IRC>
<.richn> but you can wipe and reset the emmc by fdisking it
<DC-IRC>
<.richn> so you can reinstall to it
<DC-IRC>
<speakertomeat> Is this for me?
<DC-IRC>
<.richn> no for the one looking to get the emmc back on PBP
<DC-IRC>
<.richn> Minerva
<DC-IRC>
<minervarhatesthepi> So far no changes. Even changing the frequency doesnt actually work
<DC-IRC>
<minervarhatesthepi> I will check the old dtb of my old system later on to check any differences
<DC-IRC>
<minervarhatesthepi> I would like to not have to use an ancient system just to use the emmc.
<DC-IRC>
<minervarhatesthepi> And the sd card is a no go bc of lack of UHS
<DC-IRC>
<tenkawa42> Yean I am going to attempt to work on reverting to an old u-boot... fortunately I have microsd/towboot running everything on the os currently so I can try different things
<DC-IRC>
<tenkawa42> (i can recover if something goes wrong)
<DC-IRC>
<.richn> i need toget towboot onto mine
<DC-IRC>
<.richn> when the parts get here
<DC-IRC>
<speakertomeat> What are the advantages of twoboot?
<DC-IRC>
<speakertomeat> towboot
<DC-IRC>
<tenkawa42> gives a ncurses like menu to boot kernels.... now that I've tested extlinux with multiple enttries some more I might try regular u-boot as long as I can interact with the keyboard pre-init
<DC-IRC>
<tenkawa42> I think one of the hiccups in the past I had was the kb had no response with just u-boot/extlinux
<DC-IRC>
<patrickdk> have had no luck with bookworm on the r6s 😦 it's just totally not working right 😦