On Sun, Jan 11, 2015 at 03:01:55AM +0600, Rohan Vichare wrote:
> Hi Sir,
>
> Actually, I wanted use the usbfs_get_node function to get the inode.
Really? For what? Care to point me at your kernel code that uses this
function?
> Can you let me how can i approach this now. Where can read somethi
If a USB serial device is unplugged while there is an active program
using the device it will spam the logs with -EPROTO (71) messages as it
attempts to retry.
Most serial usb drivers (metro-usb, pl2303, mos7840, ...) only output
these messages for debugging. The generic driver treats these as
er
If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
unplugged, an -ENODEV (19) error will be produced after it gives up
trying to resubmit a read.
usb_serial_generic_submit_read_urb - usb_submit_urb failed: -19
Add -ENODEV as one of the permanent errors along with -EPERM that
u
(Jan 15) Just a resend of v2 [1].
[1]: https://lkml.org/lkml/2014/12/20/16
If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
unplugged, a bunch of -ENODEV and -EPROTO errors will be produced in the
logs. This patch set quiets these messages without changing the
original beha
> From: Yunzhi Li [mailto:l...@rock-chips.com]
> Sent: Saturday, January 10, 2015 8:07 AM
>
> 在 2015/1/9 10:15, Paul Zimmerman 写道:
> >> [...]
> >>/*
> >> - * Attempt to find a generic PHY, then look for an old style
> >> - * USB PHY, finally fall back to pdata
> >> + * If platform probe
On Sun, 11 Jan 2015, Rohan Vichare wrote:
> Hi,
>
> Wanted to use the usbfs, Inode/Dentry functions. I used to work with
> 2..6.32. Now using the Linux 3.x but didn't found
> driver/usb/core/inode.c file. Please how this changes are placed in
> new kernel version.
The usbfs code is now contained
On Sun, 11 Jan 2015, vichy wrote:
> hi all:
> usually the usb_driver is matched by usb_device_id or usb_dynids.
> But there is any of them above defined in usb fs driver.
> if so, what is usb fs driver used for when registered in the usb_init
> of core/usb.c?
usbfs is meant for userspace programs
On Sun, Jan 11, 2015 at 01:34:51AM +0600, Rohan Vichare wrote:
> Hi,
>
> Wanted to use the usbfs, Inode/Dentry functions. I used to work with
> 2..6.32. Now using the Linux 3.x but didn't found
> driver/usb/core/inode.c file. Please how this changes are placed in
> new kernel version.
Use the dev
Hi,
Wanted to use the usbfs, Inode/Dentry functions. I used to work with
2..6.32. Now using the Linux 3.x but didn't found
driver/usb/core/inode.c file. Please how this changes are placed in
new kernel version.
Thanks & Regards,
Rohan.
--
To unsubscribe from this list: send the line "unsubscribe
On Sun, Jan 11, 2015 at 12:26:51AM +0800, vichy wrote:
> hi all:
> usually the usb_driver is matched by usb_device_id or usb_dynids.
> But there is any of them above defined in usb fs driver.
> if so, what is usb fs driver used for when registered in the usb_init
> of core/usb.c?
Look at /dev/usb/
hi all:
usually the usb_driver is matched by usb_device_id or usb_dynids.
But there is any of them above defined in usb fs driver.
if so, what is usb fs driver used for when registered in the usb_init
of core/usb.c?
appreciate all your kine explanation in the advance,
--
To unsubscribe from this l
Hi paul:
在 2015/1/9 10:15, Paul Zimmerman 写道:
[...]
/*
-* Attempt to find a generic PHY, then look for an old style
-* USB PHY, finally fall back to pdata
+* If platform probe couldn't find a generic PHY or an old style
+* USB PHY, fall back to pdata
Hi Paul:
On 2015/1/9 10:15, Paul Zimmerman wrote:
/*
-* Attempt to find a generic PHY, then look for an old style
-* USB PHY, finally fall back to pdata
+* If platform probe couldn't find a generic PHY or an old style
+* USB PHY, fall back to pdata
On Fri, Jan 9, 2015 at 7:58 PM, Linus Walleij wrote:
> On Fri, Jan 9, 2015 at 12:40 AM, Octavian Purdila
> wrote:
>> On Thu, Jan 1, 2015 at 9:56 AM, Linus Walleij
>> wrote:
>>> On Thu, Dec 11, 2014 at 2:02 PM, Octavian Purdila
>>> wrote:
>>>
Use the irq_chip bus_sync_unlock method to upda
14 matches
Mail list logo
