Tiny Core Base > piCore Test Releases
piCore14.0 Beta
aus9:
Hi Juanito
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README
--- Quote ---Name: vc4-fkms-v3d-pi4
Info: Enable Eric Anholt's DRM VC4 V3D driver on top of the dispmanx
display stack.
Load: dtoverlay=vc4-fkms-v3d-pi4,<param>
Params: cma-512 CMA is 512MB (needs 1GB)
cma-448 CMA is 448MB (needs 1GB)
cma-384 CMA is 384MB (needs 1GB)
cma-320 CMA is 320MB (needs 1GB)
cma-256 CMA is 256MB (needs 1GB)
cma-192 CMA is 192MB (needs 1GB)
cma-128 CMA is 128MB
cma-96 CMA is 96MB
cma-64 CMA is 64MB
cma-size CMA size in bytes, 4MB aligned
cma-default Use upstream's default value
--- End quote ---
I finally wore my goggles and spotted the hypen vs your = ;D
2) I decided to time from my inline power switch to various outcomes as below, with Xorg-3d.tcz in onboot as prev discussed
xsession no sleep 37 seconds to failed in waitfor X
" " config.txt dtoverlay=vc4-kms-v3d-pi4,cma-384 36 seconds to failed in waitforX
xsession sleep 6 config.txt dtoverlay=vc4-kms-v3d-pi4 Desktop appears 37 seconds
I did not test cmdline.txt for a cma config on the grounds I am happy with sleep.
Rich is still the winner :D
3) Because I am weirdo
###################
xsession no sleep and commented out the dtoverlay from pi4 -> desktop appears in 29 seconds.
Its late here so I will digest this tomorrow.
thanks for reading
Juanito:
--- Quote from: aus9 on June 02, 2023, 11:16:02 AM ---I finally wore my goggles and spotted the hypen vs your =
--- End quote ---
Indeed - sorry, corrected above
Rich:
Hi aus9
There was a small typo in my reply #63 that has been corrected.
mortegai:
I think that by doing modprobe of the snd-soc-hdmi-codec module in tc-config, just before the instructions for udev, no sleep or special order in the loading of extensions (graphics, alsa-modules) would be necessary, since would be loaded, as the vc4 module needs.
To generalize these situations, a bootcode similar to blacklist could be enabled where modules were put to load previously to udev (for whatever reason).
Paul_123:
--- Quote from: mortegai on June 02, 2023, 02:47:28 PM ---I think that by doing modprobe of the snd-soc-hdmi-codec module in tc-config, just before the instructions for udev, no sleep or special order in the loading of extensions (graphics, alsa-modules) would be necessary, since would be loaded, as the vc4 module needs.
--- End quote ---
The audio kernel modules will not be even mounted by then. Onboot.lst is processed near the end of tc-config. The better place to do what you want is /opt/bootsync.sh. But I'm guessing the driver is long loaded by the time it gets to bootsync.
--- Quote ---But I still ask that you please consider next image of /etc/inittab to remove comment from getty2 please.
--- End quote ---
Aus9,
If you want to play with inittab. Edit your inittab file at /etc/inittab
--- Code: ---mount /mnt/mmcblk0p1
cd /
sudo find /etc | grep inittab | sudo cpio -o -H newc | gzip -9 > /mnt/mmcblk0p1/inittab.gz
--- End code ---
Then add inittab.gz to your initramfs line in your config. (Like I had you load the cma driver before).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version