First off, let me say that finding this OS was a treat. I've been so busy in the horrific world of Windows programming I've never felt I've had time to look for projects. Recently that's changed.

I'm an avid assembly programmer with 20 years experience. I keep a DOS system just for the joy of programming with full controls. However, I'd like to start playing with Menuet instead.

I will be going through the 32-bit source starting tonight. I always like to have a goal in mind - to that end I'm curious as to where I might start looking to add 1920x1080 graphics support. Please advise and thanks in advance.

See VESA12.INC in the kernel sources. It documents the video driver interface.

You can only support the modes vesa (also UEFI) implements on you card, unless you want to write a driver for every graphic card etc.

Also do the maths, as the res get higher you are doubling the data that needs to be moved, 1/2 the FPS.

Its like using windows when it can not find your card and it just sticks the default one in.

Vesa doesn't set limitations for the graphics modes that the manufacturer can add and support.

So if your card supports 1920x1080 Vesa mode, you can activate it with an interrupt.
But first, you need to increase the size of screen pixel reference area.

Ville wrote:

Vesa doesn't set limitations for the graphics modes that the manufacturer can add and support.

When i said

Quote:

You can only support the modes vesa (also UEFI) implements on you card

I should of said, only if the vesa mode for that res was supported on the card, could you use it, but it came across wrong

Thanks for the timely responses. It's likely the first implementation will be slower than it should be. But as Pascal stated "early optimization is the death of us all". I try to always remember that. But I write so much in-line assembler at work that everyone refers to my code as "Gary C".

I have looked through the code and started to identify points where surgery must take place. In practice, how is such an add-on preferred to be handled today? As in: via compile-time, by adding call parameter(s), or field to a struct, etc. (I don't know how past additions have been or'ed in.)

BTW, is anything "wrong" with the 32-bit source? I want to use it because I have a lot of 386 SBCs that I've collected over the years and I love those little workhorses. However, I will make every effort to make something that can easily port (if anyone cares to use it).

Process management, memory protection and command restrictions (ring-3) work very well. But there are areas that can be further optimized.