From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Ed Maste <emaste@freebsd.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] kFreeBSD and USB support
Date: Thu, 06 Jun 2013 14:47:04 +0200 [thread overview]
Message-ID: <51B084C8.1000204@redhat.com> (raw)
In-Reply-To: <51AF9CBE.2030800@msgid.tls.msk.ru>
Hi,
> This effectively disables host usb support for
> kFreeBSD. And since I guess the kernel headers
> are the same on regular FreeBSD, I think the same
> issue happens on regular FreeBSD too, that is,
> host usb does not work there as well.
>
> What is the status of this situation now?
I have no idea how well the host-bsd code actually works. I've used an
OpenBSD (virtual machine) for build tests. Last time I tried it did not
build on FreeBSD. No idea where NetBSD (or any other variant) stands.
My long-term plan for usb-host support is to build on libusbx
exclusively (merged in the 1.5 devel cycle), thereby offloading all
portability issues to libusbx. Right now we are in a transition period,
the old code is still around so you can flip back and forward between
libusbx implementation and the os-specific bits for linux/bsd, mainly
because a pretty recent linusbx version is required and also to ease
regression testing. At some point in the future I want get rid of the
old code though.
FreeBSD reportly has its own libusb implementation, with a library
interface compatible to libusbx. That should work with kFreeBSD too. I
don't know what the other BSD variants are doing, but due to libusbx
being used by alot of userspace usb apps/drivers I'd expect it is
present in some form usable for qemu's host-libusb code ...
cheers,
Gerd
next prev parent reply other threads:[~2013-06-06 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 20:17 [Qemu-devel] kFreeBSD and USB support Michael Tokarev
2013-06-05 20:27 ` Andreas Färber
2013-06-05 20:34 ` Ed Maste
2013-06-05 20:51 ` Brad Smith
2013-06-06 12:47 ` Gerd Hoffmann [this message]
2013-06-06 15:08 ` Hans de Goede
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=51B084C8.1000204@redhat.com \
--to=kraxel@redhat.com \
--cc=emaste@freebsd.org \
--cc=mjt@tls.msk.ru \
--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).