From: Programmingkid <programmingkidx@gmail.com>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: QEMU devel list <qemu-devel@nongnu.org>, Gerd Hoffmann <gerd@kraxel.org>
Subject: Re: Mac OS real USB device support issue
Date: Thu, 8 Apr 2021 15:50:14 -0400 [thread overview]
Message-ID: <0BF93C96-9F20-41F4-88B5-3A96BAE54F2D@gmail.com> (raw)
In-Reply-To: <CABLmASFLSZBapgZCNQuvDd4hvpVe4SSdY7ar+VH0w_ZjquoUKQ@mail.gmail.com>
> On Apr 8, 2021, at 12:40 PM, Howard Spoelstra <hsp.cat7@gmail.com> wrote:
>
> On Thu, Apr 8, 2021 at 1:05 PM Gerd Hoffmann <gerd@kraxel.org> wrote:
>>
>> Hi,
>>
>>>> Those might be a good place to start. IOKit provides the drivers and
>>>> also the io registry which is probably where you can get if a driver
>>>> is bound to a device and which one is it. How to dissociate the
>>>> driver from the device though I don't know.
>>
>>> https://developer.apple.com/library/archive/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/DeviceRemoval/DeviceRemoval.html
>>
>>> According to this article a driver has a stop() and detach() method
>>> that is called by the IOKit to remove a device. I'm thinking QEMU can
>>> be the one that calls these methods for a certain device.
>>
>> libusb should do that. Interfaces exist already (see
>> libusb_detach_kernel_driver & friends) because we have the very same
>> problem on linux.
>>
>> take care,
>> Gerd
>>
>
> As far as I understand the patches here
> https://github.com/libusb/libusb/issues/906 they are internal to
> libusb, so we would need to build a libusb for use with e.g., brew to
> build a macOS executable. Or wait for them to be finalised to get
> included in libusb and then included in brew and then ....
>
> Best,
> Howard
We could also consider our own git submodule incase the libusb people fail to fix their issue.
next prev parent reply other threads:[~2021-04-08 19:51 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 [this message]
2021-04-08 19:43 ` Programmingkid
2021-04-09 8:08 ` Gerd Hoffmann
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=0BF93C96-9F20-41F4-88B5-3A96BAE54F2D@gmail.com \
--to=programmingkidx@gmail.com \
--cc=gerd@kraxel.org \
--cc=hsp.cat7@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).