qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 08/12] macfb: add common monitor modes supported by the Ma


From: Laurent Vivier
Subject: Re: [PATCH v2 08/12] macfb: add common monitor modes supported by the MacOS toolbox ROM
Date: Wed, 6 Oct 2021 14:24:31 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

Le 05/10/2021 à 17:33, Mark Cave-Ayland a écrit :
> On 05/10/2021 16:08, Laurent Vivier wrote:
> 
>> Le 05/10/2021 à 13:38, Mark Cave-Ayland a écrit :
>>> On 05/10/2021 10:50, Laurent Vivier wrote:
>>>
>>>> Le 04/10/2021 à 23:19, Mark Cave-Ayland a écrit :
>>>>> The monitor modes table is found by experimenting with the Monitors 
>>>>> Control
>>>>> Panel in MacOS and analysing the reads/writes. From this it can be found 
>>>>> that
>>>>> the mode is controlled by writes to the DAFB_MODE_CTRL1 and 
>>>>> DAFB_MODE_CTRL2
>>>>> registers.
>>>>>
>>>>> Implement the first block of DAFB registers as a register array including 
>>>>> the
>>>>> existing sense register, the newly discovered control registers above, 
>>>>> and also
>>>>> the DAFB_MODE_VADDR1 and DAFB_MODE_VADDR2 registers which are used by 
>>>>> NetBSD to
>>>>> determine the current video mode.
>>>>>
>>>>> These experiments also show that the offset of the start of video RAM and 
>>>>> the
>>>>> stride can change depending upon the monitor mode, so update 
>>>>> macfb_draw_graphic()
>>>>> and both the BI_MAC_VADDR and BI_MAC_VROW bootinfo for the q800 machine
>>>>> accordingly.
>>>>>
>>>>> Finally update macfb_common_realize() so that only the resolution and 
>>>>> depth
>>>>> supported by the display type can be specified on the command line.
>>>>>
>>>>> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>>>>> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
>>>>> ---
>>>>>    hw/display/macfb.c         | 124 ++++++++++++++++++++++++++++++++-----
>>>>>    hw/display/trace-events    |   1 +
>>>>>    hw/m68k/q800.c             |  11 ++--
>>>>>    include/hw/display/macfb.h |  16 ++++-
>>>>>    4 files changed, 131 insertions(+), 21 deletions(-)
>>>>>
>>>>> diff --git a/hw/display/macfb.c b/hw/display/macfb.c
>>>>> index f98bcdec2d..357fe18be5 100644
>>>>> --- a/hw/display/macfb.c
>>>>> +++ b/hw/display/macfb.c
>>>>>
>>>> ...
>>>>> +static MacFbMode *macfb_find_mode(MacfbDisplayType display_type,
>>>>> +                                  uint16_t width, uint16_t height,
>>>>> +                                  uint8_t depth)
>>>>> +{
>>>>> +    MacFbMode *macfb_mode;
>>>>> +    int i;
>>>>> +
>>>>> +    for (i = 0; i < ARRAY_SIZE(macfb_mode_table); i++) {
>>>>> +        macfb_mode = &macfb_mode_table[i];
>>>>> +
>>>>> +        if (display_type == macfb_mode->type && width == 
>>>>> macfb_mode->width &&
>>>>> +                height == macfb_mode->height && depth == 
>>>>> macfb_mode->depth) {
>>>>> +            return macfb_mode;
>>>>> +        }
>>>>> +    }
>>>>> +
>>>>> +    return NULL;
>>>>> +}
>>>>> +
>>>>
>>>> I misunderstood this part when I reviewed v1...
>>>>
>>>> It means you have to provide the monitor type to QEMU to switch from the 
>>>> default mode?
>>>
>>> Not as such: both the MacOS toolbox ROM and MacOS itself offer a fixed set 
>>> of resolutions and depths
>>> based upon the display type. What I've done for now is default the display 
>>> type to VGA since it
>>> offers both 640x480 and 800x600 in 1, 2, 4, 8, 16 and 24-bit colour which 
>>> should cover the most
>>> common use of cases of people wanting to boot using the MacOS toolbox ROM.
>>>
>>> Even if you specify a default on the command line, MacOS still only cares 
>>> about the display type and
>>> will allow you to change the resolution and depth dynamically, remembering 
>>> the last resolution and
>>> depth across reboots.
>>>
>>> During testing I found that having access to the 1152x870 resolution 
>>> offered by the Apple 21"
>>> monitor display type was useful to allow larger screen sizes, although only 
>>> up to 8-bit depth so I
>>> added a bit of code that will switch from a VGA display type to a 21" 
>>> display type if the graphics
>>> resolution is set to 1152x870x8.
>>>
>>> Finally if you boot a Linux kernel directly using -kernel then the provided 
>>> XxYxD is placed directly
>>> into the relevant bootinfo fields with a VGA display type, unless a 
>>> resolution of 1152x870x8 is
>>> specified in which case the 21" display type is used as above.
>>>
>>>> But, as a user, how do we know which modes are allowed with which 
>>>> resolution?
>>>>
>>>> Is possible to try to set internally the type here according to the 
>>>> resolution?
>>>>
>>>> Could you provide an command line example how to start the q800 with the 
>>>> 1152x870 resolution?
>>>
>>> Sure - simply add "-g 1152x870x8" to your command line. If the -g parameter 
>>> is omitted then the
>>> display type will default to VGA.
>>>
>>
>> Thank you for the explanation.
>>
>> Perhaps you can add in the error message the list of the available mode and 
>> depth?
>> (it's not a blocker for the series, it can be added later)
>>
>> As an user, it's hard to know what are the allowed values.
> 
> This is where it becomes a bit trickier, since technically booting Linux with 
> -kernel you can use
> any supported values as long as everything fits in the video RAM which is why 
> there isn't currently
> a hard-coded list :)
> 

We need the list of "supported values". I don't want to read the code or try 
values combination
until it works.

In a perfect world, I would like to be able to use any value I want with 
"-kernel".

For instance I was using "-g 1200x800x24" and it was working fine.

Now I have:

qemu-system-m68k: unknown display mode: width 1200, height 800, depth 24

If it's not possible (because the original hardware cannot provide it, and we 
don't know the base
address or things like that), we don't need the list of the display id, but the 
list of available
modes: (width,height,depth).

Rougly, something like:

qemu-system-m68k: unknown display mode: width 1200, height 800, depth 24
Available modes:
    1152x870x8
    1152x870x4
    1152x870x2
    1152x870x1
    800x600x24
    800x600x8
    800x600x4
    800x600x2
    800x600x1
    640x480x24
    640x480x8
    640x480x4
    640x480x2
    640x480x1

diff --git a/hw/display/macfb.c b/hw/display/macfb.c
index 5b8812e9e7d8..4b352eb89c3f 100644
--- a/hw/display/macfb.c
+++ b/hw/display/macfb.c
@@ -438,6 +438,26 @@ static MacFbMode *macfb_find_mode(MacfbDisplayType 
display_type,
     return NULL;
 }

+static gchar *macfb_mode_list(void)
+{
+    gchar *list = NULL;
+    gchar *mode;
+    MacFbMode *macfb_mode;
+    int i;
+
+    for (i = 0; i < ARRAY_SIZE(macfb_mode_table); i++) {
+        macfb_mode = &macfb_mode_table[i];
+
+        mode = g_strdup_printf("    %dx%dx%d\n", macfb_mode->width,
+                               macfb_mode->height, macfb_mode->depth);
+        list = g_strconcat(mode, list, NULL);
+        g_free(mode);
+    }
+
+    return list;
+}
+
+
 static void macfb_update_display(void *opaque)
 {
     MacfbState *s = opaque;
@@ -620,8 +640,13 @@ static bool macfb_common_realize(DeviceState *dev, 
MacfbState *s, Error **errp)

     s->mode = macfb_find_mode(s->type, s->width, s->height, s->depth);
     if (!s->mode) {
+        gchar *list;
         error_setg(errp, "unknown display mode: width %d, height %d, depth %d",
                    s->width, s->height, s->depth);
+        list =  macfb_mode_list();
+        error_append_hint(errp, "Available modes:\n%s", list);
+        g_free(list);
+
         return false;
     }


Thanks,
Laurent




reply via email to

[Prev in Thread] Current Thread [Next in Thread]