All of lore.kernel.org
 help / color / mirror / Atom feed
* [U-Boot] U-boot VESA driver Unsupported software interrupt #0x15
@ 2016-06-14 12:41 vinoth eswaran
  2016-06-14 13:19 ` Bin Meng
  0 siblings, 1 reply; 2+ messages in thread
From: vinoth eswaran @ 2016-06-14 12:41 UTC (permalink / raw)
  To: u-boot

Hello Mr.Bin,

 In the latest U-boot-x86 version I am seeing some error messages when
I enable the debug messages in the bios.c file.

I am checking the VESA driver initialization and it seems that for a
particular functional call it takes more time to process.
    realmode_call(addr + 0x0003, num_dev, 0xffff, 0x0000, 0xffff, 0x0,
0x0);  -- it takes around 2 seconds. Do you have any idea how to
optimize this function call or why it is taking that much time.

I tried to enable the debug messages to understand what is happening
and found that there are some software interrupts that are not
supported

[0.325805 0.002018] Real mode stub @600: 919 bytes
[0.328829 0.003024] Calling Option ROM at c0000, pci device 0x10...
[1.850796 1.521967] Unsupported software interrupt #0x15 eax 0x90005f14
[1.877799 0.027003] Unsupported software interrupt #0x15 eax 0x5f35
[1.977798 0.099999] done
[1.978944 0.001146] VBE: Getting information about VESA mode 411a

How can I disable this software interrupts ?


Mit Freundlichen Gr??en
VinothKumar
+49 1798909072

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [U-Boot] U-boot VESA driver Unsupported software interrupt #0x15
  2016-06-14 12:41 [U-Boot] U-boot VESA driver Unsupported software interrupt #0x15 vinoth eswaran
@ 2016-06-14 13:19 ` Bin Meng
  0 siblings, 0 replies; 2+ messages in thread
From: Bin Meng @ 2016-06-14 13:19 UTC (permalink / raw)
  To: u-boot

On Tue, Jun 14, 2016 at 8:41 PM, vinoth eswaran <evinoth1206@gmail.com> wrote:
> Hello Mr.Bin,
>
>  In the latest U-boot-x86 version I am seeing some error messages when
> I enable the debug messages in the bios.c file.
>
> I am checking the VESA driver initialization and it seems that for a
> particular functional call it takes more time to process.
>     realmode_call(addr + 0x0003, num_dev, 0xffff, 0x0000, 0xffff, 0x0,
> 0x0);  -- it takes around 2 seconds. Do you have any idea how to
> optimize this function call or why it is taking that much time.
>

This is 16-bit BIOS call. It is expected that it is slow.

> I tried to enable the debug messages to understand what is happening
> and found that there are some software interrupts that are not
> supported
>
> [0.325805 0.002018] Real mode stub @600: 919 bytes
> [0.328829 0.003024] Calling Option ROM at c0000, pci device 0x10...
> [1.850796 1.521967] Unsupported software interrupt #0x15 eax 0x90005f14
> [1.877799 0.027003] Unsupported software interrupt #0x15 eax 0x5f35
> [1.977798 0.099999] done
> [1.978944 0.001146] VBE: Getting information about VESA mode 411a
>
> How can I disable this software interrupts ?
>

INT15 is Intel's custom vgabios call. This can be ignored, since it is working.

Regards,
Bin

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-06-14 13:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-14 12:41 [U-Boot] U-boot VESA driver Unsupported software interrupt #0x15 vinoth eswaran
2016-06-14 13:19 ` Bin Meng

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.