Hi! I got your git from a forum, but I can’t figure out how to installed in my
OpenWRT CC, any help?
Argus Luconi Rosenhaim
AV Tecnologias Inovadoras
+55 51 9283 7934
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
M
On Sun, Mar 09, 2014 at 05:53:51PM +0200, Valentina Manea wrote:
> I was notified that one of the patches in the series (staging: usbip:
> claim ports used by shared devices) breaks the build.
> I take full responsability for this as I haven't compiled the kernel
> with allyesconfig and I am sorry.
I was notified that one of the patches in the series (staging: usbip:
claim ports used by shared devices) breaks the build.
I take full responsability for this as I haven't compiled the kernel
with allyesconfig and I am sorry.
This can be fixed by moving struct dev_state, usb_hub_claim_port() and
On Sat, Mar 08, 2014 at 02:53:18PM +0200, Valentina Manea wrote:
> This is a resend of the patches sent a few days ago, including
> the migration of USB/IP userspace side to use libudev instead
> of libsysfs and various other fixes, all ordered in a big patch
> series.
Very nice work, thanks so mu
This is a resend of the patches sent a few days ago, including
the migration of USB/IP userspace side to use libudev instead
of libsysfs and various other fixes, all ordered in a big patch
series.
The patches have been modified according to received feedback.
Valentina Manea (18):
staging: usbi
On Tue, Mar 04, 2014 at 09:10:40PM +0200, Valentina Manea wrote:
> This patch series modifies the USB/IP userspace side (usbip-utils)
> to use libudev instead of libsysfs. This change was necessary as
> libsysfs is no longer maintained and we have discovered a bug that
> affected USB
This patch series modifies the USB/IP userspace side (usbip-utils)
to use libudev instead of libsysfs. This change was necessary as
libsysfs is no longer maintained and we have discovered a bug that
affected USB/IP.
On the other hand, libudev is actively maintained and recommended
for interacting
0x0100 -> 0x0111 without obvious (to me at least)
> reasons.
> So Linux-side rejects connections because of protocol
> mistmatch. Currently, I have recompiled usbip-utils on Linux system
> with fixed version and it became speaking to Windows now. But I have
> not tested devices
de rejects connections because of protocol mistmatch.
Currently, I have recompiled usbip-utils on Linux system with fixed
version and it became speaking to Windows now. But I have not tested
devices yet.
I think this should be fixed somehow in usbip-utils - by downgrading
version, or accep
