From: BALATON Zoltan <balaton@eik.bme.hu>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: Programmingkid <programmingkidx@gmail.com>,
QEMU devel list <qemu-devel@nongnu.org>,
Gerd Hoffmann <gerd@kraxel.org>
Subject: Re: Mac OS real USB device support issue
Date: Sat, 10 Apr 2021 13:29:03 +0200 (CEST) [thread overview]
Message-ID: <8827217c-8fee-7845-045-16ff9622d90@eik.bme.hu> (raw)
In-Reply-To: <CABLmASEPFVDejmfJw-Ak1_veREySYv8F-+ZKW_S2cDsEbfu7Gg@mail.gmail.com>
On Sat, 10 Apr 2021, Howard Spoelstra wrote:
> On Fri, Apr 9, 2021 at 9:37 PM Programmingkid <programmingkidx@gmail.com> wrote:
>> Have you tried the proposed changes yet for libusb?
>
> Hi,
>
> Yes, I experimented with the current libusb from brew, the latest
> libusb code from github and a patched version based on that. I
> couldn't get a flash drive passed through with any of them. Running as
> root made no difference. My Mojave host doesn't allow unloading the
> kext loaded for the flash drive where Sierra allowed that, but then
> that should be handled by the patches.
>
> I'll link to the latest libusb and the patched version plus the
> patches. I guess it will not work on your host, but you might be able
> to persuade qemu to use them by using
> install_name_tool -change /usr/local/opt/libusb/lib/libusb-1.0.0.dylib
> @executable_path/libusb-1.0.0-latest.dylib qemu-system-ppc
>
> I'll also include the patches, libusb is easily built.
> https://surfdrive.surf.nl/files/index.php/s/Qs0rtTVe2qIudw4/download
I think you (John and Gerd) found that detecting if a kernel driver is
attached does not seem to work so it does not even get to unloading what
these patches are about I think. So you first need to debug and fix
libusb_kernel_driver_active() so the unloading function is called at all.
I don't know how that's done on macOS but maybe querying the IO registry
somehow that should have all info about devices and IOKit drivers.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2021-04-10 11:31 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 [this message]
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
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=8827217c-8fee-7845-045-16ff9622d90@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=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).