public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Rob Taglang <rob@taglang.io>
Cc: edk2-devel@lists.01.org, Ming Huang <ming.huang@linaro.org>,
	Star Zeng <star.zeng@intel.com>, Ruiyu Ni <ruiyu.ni@intel.com>
Subject: Re: OVMF UsbBulkTransfer returns EFI_OUT_OF_RESOURCES
Date: Tue, 3 Apr 2018 13:49:37 +0200	[thread overview]
Message-ID: <cc18e7e6-f47c-5724-9dff-d7b19d465e58@redhat.com> (raw)
In-Reply-To: <1522707137.3698.1@server175.web-hosting.com>

Hi Rob,

On 04/03/18 00:12, Rob Taglang wrote:
> Hello,
> 
> I can pass a host USB device to QEMU boot with OVMF, and it shows up as
> a EFI_USB_IO_PROTOCOL device and the interface descriptors and endpoints
> are detected correctly. A UsbControlTransfer operation succeeds.
> However, UsbBulkTransfer returns EFI_OUT_OF_RESOURCES regardless of how
> much memory I allocate for QEMU.
> 
> This application does work correctly on real hardware. Is this expected
> behavior in OVMF?

I seem to recall recent patches for the core USB drivers in edk2 that
modified various timeouts and transfer block sizes. For example:

  [edk2] [MdeModulePkg/Usb v2 0/1] Calculating the count of blocks to
                                   transfer

Committed at
<https://github.com/tianocore/edk2/commit/824b6e3b5fa080df36626db3eb8465c25a12c053>.

Can you try a fresh edk2 build, and/or state git commit hashes at which
the tree does or does not work for you?

It would also be interesting to know the exact USB device (vendor, model
etc) that produces this issue for you. Chances are the edk2 USB drivers
would have the same issue if they encountered your device on the bare
metal (i.e. with edk2 running as physical platform firmware).

Thanks!
Laszlo


  reply	other threads:[~2018-04-03 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 22:12 OVMF UsbBulkTransfer returns EFI_OUT_OF_RESOURCES Rob Taglang
2018-04-03 11:49 ` Laszlo Ersek [this message]
2018-04-03 15:10   ` Rob Taglang
2018-04-03 15:49     ` Rob Taglang
2018-04-03 16:48       ` Rob Taglang
2018-04-04  8:09         ` Zeng, Star

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-list 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=cc18e7e6-f47c-5724-9dff-d7b19d465e58@redhat.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox