I can only put up this proposal:
Generally speaking I would be nice to be able to change screen resolutions
at runtime on the de10_nano board,
instead of having to generate a custom quartus hdmi bitfile and dtb for
each resolution(screen) needed.
I once found a different de10 nano project on github that seemed to have
this exact functionality:
https://github.com/MiSTer-devel
However at the time I investigated this project I was unable to nail down
the exact commits/additions needed to port
the change screen resolution functionality from the mister quartus project
and the linux framebuffer driver. --> mksocfpga
perhaps with some helping hands this functionality can be ported over from
the mister emulator.
On Saturday, February 22, 2020 at 9:58:21 PM UTC+1, justin White wrote:
Any plans to add this to the build script? Playing with Quartus isn't
> something I generally love to do.
>
If some sort of group effort can be put into porting the resolution change
mechanism from the mister project,
this will then result in an updated de10 mksocfpga project (with screen
resolution change bitfiles) and also
an updated framebuffer driver (which goes into the kernel part of the
buildscript)
>
> On Tuesday, February 18, 2020 at 5:44:32 AM UTC-5, Michael Brown wrote:
>
>
>
> On Tue, 18 Feb 2020, 11.39 Michael Brown <[email protected]> wrote:
>
> BTW the newest de10 SD images are around here:
> https://github.com/the-snowwhite/soc-image-buildscripts
>
>
> Look for binary releases
>
> Sorry for the messy mails but I'm currently in hospital attempting to get
> thru via my phone...
>
>
>
> On Tue, 18 Feb 2020, 11.26 Michael Brown <[email protected]> wrote:
>
> It's unfortunately not as simple as the frame buffer is hardwired to the
> display parameters in quartus. Resolution change requires changing the FB
> parameters in quartus... Generating a new bit file and then generating an
> altered device tree with the new display parameters.
> Michael B.
>
> On Tue, 18 Feb 2020, 01.22 justin White <[email protected]> wrote:
>
> I know I've seen some resolution numbers in the quartus files so I assumed
> this was using part of the FPGA to do a framebuffer or something and it was
> actually part of the Quartus project. I thought the BBB actually had a GPU
> unlike the nano. I'll definitely try it when I get a chance, the 800x480
> monitor looks like trash, even being small.....hoping to pick up and get
> this going on a 1024x600 version.
>
> I believe the de10-nano image here is the one I used
> https://drive.google.com/drive/folders/1THXnrnt-v7iNownBqmdOQrJ-i8EVAsSZ
>
>
>
> On Monday, February 17, 2020 at 5:34:07 PM UTC-5, Charles Steinkuehler
> wrote:
>
> I don't currently have a DE10-Nano running, but I reviewed the code and
> it looks like you should be able to set the resolution the same as you
> would for any other embedded display (by passing some kernel
> parameters). Refer to:
>
> * The modedb documentation:
>
> https://www.kernel.org/doc/Documentation/fb/modedb.txt
>
> * My posts on setting resolutions on the BBB:
>
>
> http://blog.machinekit.io/2013/06/force-beaglebone-black-hdmi-resolution.html
>
> http://blog.machinekit.io/2013/07/custom
> <http://blog.machinekit.io/2013/07/custom-hdmi-resolution.html>
>
> ...
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/machinekit/ed43e04a-3763-43fe-afec-729f70f66203%40googlegroups.com.
