All of lore.kernel.org
 help / color / mirror / Atom feed
From: vinoth eswaran <evinoth1206@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot VESA driver Unsupported software interrupt #0x15
Date: Tue, 14 Jun 2016 14:41:33 +0200	[thread overview]
Message-ID: <CAJst-kEcTe5OGT_tQuhkMnQEUzX9iPuWAe9ghJaETEhTEGd_0g@mail.gmail.com> (raw)

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

             reply	other threads:[~2016-06-14 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 12:41 vinoth eswaran [this message]
2016-06-14 13:19 ` [U-Boot] U-boot VESA driver Unsupported software interrupt #0x15 Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJst-kEcTe5OGT_tQuhkMnQEUzX9iPuWAe9ghJaETEhTEGd_0g@mail.gmail.com \
    --to=evinoth1206@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.