On Mon, 18 Mar 2019, Felipe Balbi wrote:
> > The spec says:
> >
> > All Debug Devices, with the exception of fixed address devices,
> > must implement all required standard commands in the core
> > device framework.
> >
> > But that refers to standard _commands_, not standard _descri
Hi,
Alan Stern writes:
>> Randy Dunlap writes:
>> > Linux v5.0-11053-gebc551f2b8f9 of March 12, on x86_64:
>> >
>> > with
>> > CONFIG_USB_G_DBGP=m
>> > # CONFIG_USB_G_DBGP_PRINTK is not set
>> > CONFIG_USB_G_DBGP_SERIAL=y
>> > CONFIG_USB_U_SERIAL=m
>> >
>> > Loading g_dbgp module and then unloa
On Mon, 18 Mar 2019, Felipe Balbi wrote:
> Hi,
>
> Randy Dunlap writes:
> > Linux v5.0-11053-gebc551f2b8f9 of March 12, on x86_64:
> >
> > with
> > CONFIG_USB_G_DBGP=m
> > # CONFIG_USB_G_DBGP_PRINTK is not set
> > CONFIG_USB_G_DBGP_SERIAL=y
> > CONFIG_USB_U_SERIAL=m
> >
> > Loading g_dbgp module
Hi,
Randy Dunlap writes:
> Linux v5.0-11053-gebc551f2b8f9 of March 12, on x86_64:
>
> with
> CONFIG_USB_G_DBGP=m
> # CONFIG_USB_G_DBGP_PRINTK is not set
> CONFIG_USB_G_DBGP_SERIAL=y
> CONFIG_USB_U_SERIAL=m
>
> Loading g_dbgp module and then unloading it causes:
>
> WARNING: CPU: 0 PID: 24523 at