From: Gerd Hoffmann <gerd@kraxel.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Howard Spoelstra <hsp.cat7@gmail.com>,
QEMU devel list <qemu-devel@nongnu.org>
Subject: Re: Mac OS real USB device support issue
Date: Fri, 9 Apr 2021 10:08:04 +0200 [thread overview]
Message-ID: <20210409080804.vs2r546gy3ntdmgr@sirius.home.kraxel.org> (raw)
In-Reply-To: <C055FBC4-09F8-4057-9742-99C660F97607@gmail.com>
Hi,
> The questions that come to mind are:
> - Does libusb_detach_kernel_driver() work on Mac OS?
> - Is libusb_detach_kernel_driver() called on Mac OS in QEMU?
>
> The only mention of this function in QEMU comes from host-libusb.c.
>
> After some tests I found out the function
> host-libusb.c:usb_host_detach_kernel() is being called on Mac OS 11.1.
> It never reaches the libusb_detach_kernel_driver() function. It stops
> at the continue statement.
Yep. Most likely libusb_kernel_driver_active() returns 0 because the
kernel driver management functions are not implemented for macos.
take care,
Gerd
next prev parent reply other threads:[~2021-04-09 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:44 Mac OS real USB device support issue Programmingkid
2021-04-06 14:01 ` Howard Spoelstra
2021-04-06 14:20 ` BALATON Zoltan
2021-04-06 14:33 ` Programmingkid
2021-04-06 14:31 ` Programmingkid
2021-04-06 16:53 ` BALATON Zoltan
2021-04-06 19:28 ` Programmingkid
2021-04-06 23:18 ` BALATON Zoltan
2021-04-07 1:52 ` Programmingkid
2021-04-07 5:26 ` Howard Spoelstra
2021-04-07 5:28 ` Howard Spoelstra
2021-04-07 10:27 ` BALATON Zoltan
2021-04-09 19:37 ` Programmingkid
2021-04-10 7:28 ` Howard Spoelstra
2021-04-10 11:29 ` BALATON Zoltan
2021-05-16 0:33 ` Programmingkid
2021-04-08 11:05 ` Gerd Hoffmann
2021-04-08 16:40 ` Howard Spoelstra
2021-04-08 19:50 ` Programmingkid
2021-04-08 19:43 ` Programmingkid
2021-04-09 8:08 ` Gerd Hoffmann [this message]
2021-04-14 14:03 ` Programmingkid
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=20210409080804.vs2r546gy3ntdmgr@sirius.home.kraxel.org \
--to=gerd@kraxel.org \
--cc=hsp.cat7@gmail.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).