Re: Amiga screen modes in wscons
Carlos Milán Figueredo <[email protected]> Sun, 12 Nov 2023 16:08:46 +0000
| Newsgroups | gmane.os.netbsd.ports.amiga |
|---|---|
| Message-ID | <CO6P220MB0564D63056D314CABF38B12CC9ACA@CO6P220MB0564.NAMP220.PROD.OUTLOOK.COM> |
Hi David,=0A= =0A= From: David Brownlee <[email protected]>=0A= Sent: Sunday, November 12, 2023 12:52=0A= =0A= > If you have a fast cross build box the time to rebuild a new kernel=0A= > with adjusted values is approximately nothing (though the time to copy=0A= > to the Amiga and for it to reboot into it is very much not :)=0A= =0A= I have the cross build box. Indeed it takes more time to scp the kernel to = the Amiga and reboot than the compilation itself :) If for wrong parameters= I cannot see the screen and I have to hard-reset the Amiga, the fsck will = take easily 15 minutes. I could go around that by blindly writing or serial= console...=0A= =0A= > Looking for a more general solution - the values could be optionally=0A= > passed in at boot time from the bootloader, either as parameters or by=0A= > reading from a boot.cfg file=0A= =0A= Not sure if that would be worth as they are really low-level, mostly for de= bugging. I think what would make sense is to give the user the option to se= lect the screen mode as parameter from bootloader. I can see there are seve= ral screenmodes defined in grfabs_cc.c: GRF_PAL, GRF_NTSC, GRF_AGA, GRF_AGA= _VGAONLY, GRF_SUPER72, GRF_A2024...=0A= =0A= I think the -A kernel parameter -though nice- is not fine-grained enough.= =0A= =0A= > Actually - are these values which would make sense to be able to=0A= > adjust dynamically at runtime - so via sysctl or ioctl the screenmode=0A= > could be tweaked while running?=0A= =0A= In that case, yes, low-level welcome! It would really help to adjust screen= issues such as the one I am experiencing.=0A= =0A= Regards,=0A= Carlos=0A= =0A= Carlos Mil=E1n Figueredo | HispaMSX System Operator | http://www.hispamsx.o= rg | telnet://bbs.hispamsx.org | https://calnus.com=