Hello,
> I know that usbip is insecure but personally I think that this series
> makes it much more insecure.
Later, I remembered USB/IP has TCP wrappers option.
It is activated with ./configure --with-tcp-wrappers and
/etc/hosts.[deny|allow].
And I tested and found a BUG in my patch which
On Wed, Oct 05, 2016 at 01:54:01PM -0500, Bjorn Helgaas wrote:
> On Wed, Oct 05, 2016 at 10:45:22AM -0400, Alan Stern wrote:
> > In short, Pierre's USB host controller doesn't send wakeup signals from
> > runtime suspend, because the firmware limits the runtime-suspend state
> > to D0 and the
On 10/4/2016 2:49 PM, Greg KH wrote:
On Tue, Oct 04, 2016 at 12:04:40PM -0700, Vijay Kumar wrote:
Grub finds incorrect of_node path for devices behind usb hub.
Added devspec sysfs entry for devices behind usb hub so that
right of_node path is returned during grub sysfs walk for these
devices.
[+cc Rafael, Lukas]
On Wed, Oct 05, 2016 at 10:45:22AM -0400, Alan Stern wrote:
> [Adding Bjorn and linux-pci to the CC: list]
>
> In short, Pierre's USB host controller doesn't send wakeup signals from
> runtime suspend, because the firmware limits the runtime-suspend state
> to D0 and the
[Adding Bjorn and linux-pci to the CC: list]
In short, Pierre's USB host controller doesn't send wakeup signals from
runtime suspend, because the firmware limits the runtime-suspend state
to D0 and the controller can't issue PME# from the D0 state. In this
situation we would prefer to avoid
* Łukasz Pułka [161004 23:36]:
>
> Can you point me what else should I check to make USB HS working in ohci mode?
Sounds like you're pretty close, in addition to the
pin muxing and PHY configuration, check also that you
have proper VBUS coming to the ports.
Regards,
Tony
--
This adds support to ftdi_sio for the Infineon TriBoard TC2X7
engineering board for first-generation Aurix SoCs with Tricore CPUs.
Mere addition of the device IDs does the job.
Signed-off-by: Stefan Tauner
---
drivers/usb/serial/ftdi_sio.c | 3 ++-
On Wed, 2016-10-05 at 10:29 +0200, Stefan Tauner wrote:
> On Wed, 05 Oct 2016 09:31:29 +0200
> Oliver Neukum wrote:
>
> > On Fri, 2016-09-30 at 17:39 +0200, Stefan Tauner wrote:
> > > Signed-off-by: Stefan Tauner
> >
> > A minimal change log
Hi,
On Tuesday 04 October 2016 04:13 PM, Vivek Gautam wrote:
> No-Op phy transceiver can be used on platforms that have
> controllers which themselves provide PHY functionality and
> there's no separate PHY controller available.
>
> This driver provides a basic skeleton for a nop-phy driver.
>
On Wed, Oct 05 2016, Felipe Balbi wrote:
> Hi Baolin,
>
> Baolin Wang writes:
But you do!
The mA number from the USB configuration is passed to usb_gadget_vbus_draw.
Your patch passes that to usb_charger_set_cur_limit_by_type()
which calls
On Wed, 05 Oct 2016 09:31:29 +0200
Oliver Neukum wrote:
> On Fri, 2016-09-30 at 17:39 +0200, Stefan Tauner wrote:
> > Signed-off-by: Stefan Tauner
>
> A minimal change log entry would be good.
Hi Oliver,
I thought about it but there is
On 04.10.2016 17:11, Alan Stern wrote:
On Tue, 4 Oct 2016, Mathias Nyman wrote:
On 03.10.2016 23:54, Pierre de Villemereuil wrote:
Hi Mathias,
Just to know: does that mean the firmware from Asus is faulty in here? Do you
think I should contact Asus about this?
Probably, _S0W, _DSM and
Hi Felipe,
On 5 October 2016 at 15:47, Felipe Balbi wrote:
>
> Hi Baolin,
>
> Baolin Wang writes:
But you do!
The mA number from the USB configuration is passed to usb_gadget_vbus_draw.
Your patch passes that to
Hi Vivek,
On 5 October 2016 at 10:15, Vivek Gautam wrote:
> Hi Anand,
>
>
> On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote:
>> Hi Vivek,
>>
>
> [snip]
>
>>
>> What I feel is that their need to be some reset of usb phy so that
>> device are
Hi Baolin,
Baolin Wang writes:
>>> But you do!
>>> The mA number from the USB configuration is passed to usb_gadget_vbus_draw.
>>> Your patch passes that to usb_charger_set_cur_limit_by_type()
>>> which calls __usb_charger_set_cur_limit_by_type() which will set the
>>>
Hi,
Guoqing Zhang writes:
> For USB2 ports, the port test modes TEST_J_State, Test_K_State,
> Test_Packet and Test_SE0_NAK can be enabled as described in USB2
> spec.
>
> Signed-off-by: Guoqing Zhang
> ---
> drivers/usb/host/xhci-hub.c | 55
>
On Fri, 2016-09-30 at 17:39 +0200, Stefan Tauner wrote:
> Signed-off-by: Stefan Tauner
A minimal change log entry would be good.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a
Hi Felipe,
>> But you do!
>> The mA number from the USB configuration is passed to usb_gadget_vbus_draw.
>> Your patch passes that to usb_charger_set_cur_limit_by_type()
>> which calls __usb_charger_set_cur_limit_by_type() which will set the
>> cur_limit for whichever type uchger->type currently
On Tue, Oct 04, 2016 at 11:07:20PM -0700, Ashton Holmes wrote:
> On Tue, Oct 4, 2016 at 10:18 PM, Greg KH wrote:
> > On Tue, Oct 04, 2016 at 05:15:17PM -0700, Ashton Holmes wrote:
> >> On Tue, Oct 4, 2016 at 12:11 AM, Greg KH
> >> wrote:
>
Hi,
I am trying to make 4.4 kernel working with old am3517 SOM
(http://www.dave.eu/products/som/texas_instruments/am3505-am3517_lizard).
Most of the peripherals are working know - however I got stuck with
usb ohci driver.
Both USB HS ports are connected to ISP1105, hardware is working with
old
On Tue, Oct 4, 2016 at 10:18 PM, Greg KH wrote:
> On Tue, Oct 04, 2016 at 05:15:17PM -0700, Ashton Holmes wrote:
>> On Tue, Oct 4, 2016 at 12:11 AM, Greg KH wrote:
>> >> Also my knowledge of git isn't that extensive and I got the source
>>
21 matches
Mail list logo