Rick Engebretson wrote:
Definitely (having changed to fb myself recently since my new graphics card doesn't provide a good high-resolution textmode anymore).
Actually, the matrox card has a resolution set to (if I remember, early in the morning here) 1280x1024x16, with higher modes available!! And clear text!!
Text mode or graphics mode? In graphics mode, this is not surprising (even my rather cheap card can do 1600x1200x32). But since few people use text mode today, most current cards only support pathetic text modes. And to use graphics mode for Linux VC, you need fb.
A little note; I think your crtdemo does a SVGAtextmode switch. It might have cost a used PCparts guy a replacement monitor : -)
Really? I think it only uses rather simple modes. (And why would someone install SVGAtextmode, and disable the safety settings or provide wrong timing ranges, just to destroy their monitors, BTW? ;-)
But I think I can disable this part, since, as I wrote, probably few people are (able to) use SVGAtextmode for good modes today, unfortunately.
The reason I'm plowing through C libraries is to mmap /dev/fb0.
You did see MMapHandle (low-level) and MemoryMap (higer-level) in the GPC module? :-)
Yes I did. But I did not see the msync() call implemented. AFAIK this is how to assure writes from memory to file.
Yes, for files. For memory devices it's not necessary AFAIK. These and read-only files are all I've mapped so far, so I hadn't added it. If you need it, I can probably add it in the next release.
Frank