Hello kernel hackers,

please excuse the way I'm writing this. I know I'm for sure braking rules.
I'm trying to use the usbip vhcd_hcd driver to monitor a beehive via an 
exported usb mic. Usbip is great, because I can use a very small router running 
openwrt and export the mic via usbip. Thanks for it!

The usbip README said patches should be sent to Greg Kroah-Hartman but in the 
MAINTAINERS file you all are mentioned. So please excuse me for writing to you 
all.

USBIP works just as expected. But the driver on the client side polutes the 
kernel ring buffer (and syslog) with this message:
[...]
[ 8761.874551] vhci_hcd: Not yet implemented
[ 8761.875561] vhci_hcd: Not yet implemented
[ 8761.876558] vhci_hcd: Not yet implemented
[ 8761.877704] vhci_hcd: Not yet implemented
[ 8761.878592] vhci_hcd: Not yet implemented
[...]

This is annoying because I want to record the sound inside the beehive for at 
least one complete year.
The function that is printing this must be:

drivers/usb/usbip/vhci_hcd.c (lines 942ff):
static int vhci_get_frame_number(struct usb_hcd *hcd)
{
        pr_err("Not yet implemented\n");
        return 0;
}


It would be nice if you could add some lines like this:
usbip: vhci_get_frame_number
static int vhci_get_frame_number(struct usb_hcd *hcd)
{
        static unsigned int to_be_seen = 5;

        if (to_be_seen) {
                pr_err("Not yet implemented\n");
                to_be_seen--;
        }
        return 0;
}


I'm not a programer nor do I know if this compiles. I can't test this, because 
the server is a standard ubuntu LTS server. I don't want it to run kernels made 
by me.
Maybe a module parameter option or something complete different is the better 
solution.
I'm just a linux user.

Thank you again for this great driver and all the open source you're creating!
Have a good time.

Best regards
Lars Täuber

PS: I'm not subscribed to the mailing list.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to