VirtualBox

Ignore:
Timestamp:
Jan 30, 2007 3:42:55 PM (18 years ago)
Author:
vboxsync
Message:

Main: Added USBDevice to the DeviceType enum to provide USB device activity (search for USB_DEVICE_ACTIVITY in ConsoleImpl.cpp). Thanks to MS COM C++ bingings polluting the global namespace with enum values, I had to rename the USBDevice class to OUSBDevice (and to add the COM_DECL_READONLY_ENUM_AND_COLLECTION_EX_BEGIN macro for even more flexible collection declarations).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/VBox/Main/idl/VirtualBox.xidl

    r359 r436  
    263263        <const name="NetworkDevice"     value="4">
    264264            <desc>Network device.</desc>
     265        </const>
     266        <const name="USBDevice"         value="5">
     267            <desc>USB device.</desc>
    265268        </const>
    266269    </enum>
     
    54835486                buffer does not have to be aligned and lockable.
    54845487
    5485                 The callee is also allowed to use the memory buffer
    5486                 pointed to by the vram parameter. For non linear
    5487                 modes (such as text and standard VGA), the parameter
    5488                 is NULL and must not be used. When using it, all the
    5489                 IFramebuffer implementation has to do is return the
    5490                 same pointer as the Address property. It is recommended
    5491                 to use it as it will remove one copy operation.
     5488                The callee is also allowed to use the guest video memory
     5489                buffer (pointed to by the @a vram parameter) directly instead
     5490                of allocating its own buffer. To indicate that the framebuffer
     5491                wants to use the guest video memory, its <link to="#address"/>
     5492                implementation must return the same address as it gets in
     5493                the @a vram parameter of this method.
     5494               
     5495                For non linear modes (such as text and standard VGA), the
     5496                @vram parameter is NULL and must not be used. When it's not
     5497                NULL, it is recommended to use it to access the guest video
     5498                memory instead of creating a separate buffer as it will at
     5499                least remove one copy operation.
    54925500
    54935501                The caller checks if the call was successful
    5494                 via IFramebuffer property 'PixelFormat'.
    5495 
    5496                 Note: The method is called by IDisplay under the Framebuffer lock.
     5502                via the <link to="#pixelFormat"/> property.
     5503
     5504                <note>
     5505                    This method is called by IDisplay under the IFramebuffer
     5506                    lock.
     5507                </note>
    54975508            </desc>
    54985509            <param name="pixelFormat" type="FramebufferPixelFormat" dir="in">
    5499                 <desc>Specifies the pixel format of the surface (bpp and layout)</desc>
     5510                <desc>Pixel format of the surface (BPP and layout)</desc>
    55005511            </param>
    55015512            <param name="vram" type="unsigned long" dir="in">
    5502                 <desc>Pointer to original guest VRAM (NULL for non linear modes)</desc>
     5513                <desc>Pointer to the guest VRAM (NULL for non linear modes)</desc>
    55035514            </param>
    55045515            <param name="lineSize" type="unsigned long" dir="in"/>
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette