Re: [PATCH net-next v2 0/6] support new chip

2014-01-01 Thread David Miller
From: Hayes Wang Date: Thu, 2 Jan 2014 11:22:38 +0800 > Remove the trailing "/* CRC */" for patch #3. > > Change the return value type of rtl_ops_init() from int to boolean > for patch #4. > > Replace VENDOR_ID_SAMSUNG with SAMSUNG_VENDOR_ID for patch #6. Series applied, thank you. -- To unsub

[PATCH net-next v2 3/6] r8152: change some definitions

2014-01-01 Thread Hayes Wang
Replace RX_BUF_THR with RX_THR_HIGH. Replace RWSUME_INDICATE with RESUME_INDICATE. Add CRC_SIZE, TX_ALIGN, and RX_ALIGN. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 27 --- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/drivers/net/usb/r8152.c

[PATCH net-next v2 1/6] r8152: move rtl8152_unload and ocp_reg_write

2014-01-01 Thread Hayes Wang
Change the locations of rtl8152_unload() and ocp_reg_write(). Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 58 - 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c index 5107

[PATCH net-next v2 6/6] r8152: support RTL8153

2014-01-01 Thread Hayes Wang
Support new chip RTL8153 which is the USB 3.0 giga ethernet adapter. Signed-off-by: Hayes Wang --- drivers/net/usb/cdc_ether.c | 10 + drivers/net/usb/r8152.c | 615 +++- drivers/net/usb/r815x.c | 2 +- 3 files changed, 621 insertions(+), 6 dele

[PATCH net-next v2 4/6] r8152: add rtl_ops

2014-01-01 Thread Hayes Wang
The different chips may have different settings. This makes it easy to let different chips have the same flow with differnt settings. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 57 +++-- 1 file changed, 50 insertions(+), 7 deletions(-) di

[PATCH net-next v2 0/6] support new chip

2014-01-01 Thread Hayes Wang
Remove the trailing "/* CRC */" for patch #3. Change the return value type of rtl_ops_init() from int to boolean for patch #4. Replace VENDOR_ID_SAMSUNG with SAMSUNG_VENDOR_ID for patch #6. Hayes Wang (6): r8152: move rtl8152_unload and ocp_reg_write r8152: modify the method of accessing PHY

[PATCH net-next v2 2/6] r8152: modify the method of accessing PHY

2014-01-01 Thread Hayes Wang
The old method to access PHY is through mdio channel. Replace it with the OCP channel. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 52 + 1 file changed, 18 insertions(+), 34 deletions(-) diff --git a/drivers/net/usb/r8152.c b/drivers/n

[PATCH net-next v2 5/6] r8152: split rtl8152_enable

2014-01-01 Thread Hayes Wang
Split the contents of rtl8152_enable() into rtl_set_eee_plus() and rtl_enable(). Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c index 8a7c876..bc5d569

Re: 0471:206c IR receiver, mceusb & NULL pointer dereference

2014-01-01 Thread Alan Ott
On 01/01/2014 05:13 PM, Sander Smeenk wrote: Plugging in a 0471:206c 'Spinel plusf0r Asus' IR receiver with the more recent mceusb module versions Oops'es the kernel with a null pointer deref. I'm currently seeing this in 3.12.0 (Ubuntu stock) but i recall seeing this problem since about 3.8+ ker

0471:206c IR receiver, mceusb & NULL pointer dereference

2014-01-01 Thread Sander Smeenk
Hi, Plugging in a 0471:206c 'Spinel plusf0r Asus' IR receiver with the more recent mceusb module versions Oops'es the kernel with a null pointer deref. I'm currently seeing this in 3.12.0 (Ubuntu stock) but i recall seeing this problem since about 3.8+ kernels. I kinda hoped it'd go away over time

Problem connecting a Wyred 4 Sound DAC2 DSD SE DAC on Renesas USB3.0 card

2014-01-01 Thread Dominique COMET
Hi, I'm a new to Linux and I try to build a computer dedicated to audio with a Linux Distribution calles Daphile (www.daphile.com). It appears that this DAC cannot be initialized correctly with Linux when I plug it on a NEC/RENESAS USB3.0 card with u720202 chipset. $result: it isn't recognized

Re: USB HID devices communicating with each other

2014-01-01 Thread Alan Ott
On 01/01/2014 09:48 AM, Joe M wrote: I am developing a USB HID device (simple keyboard). I want to have 2 different such keyboards connected to the same computer to share the shift, control, alt or any such modifier key. So, I do not have to have the same modifier key on the different keyboards c

Re: USB HID devices communicating with each other

2014-01-01 Thread Joe M
Hello Greg, > > I am developing a USB HID device (simple keyboard). I want to have 2 > > different such keyboards connected to the same computer to share the > > shift, control, alt or any such modifier key. So, I do not have to > > have the same modifier key on the different keyboards connected t