Hi,
On Tue, Aug 07, 2012 at 09:33:42AM +0530, Pratyush Anand wrote:
From: Pratyush ANAND pratyush.an...@st.com
For core 1.94A and latter, specification says to issue DEPCFG with
Config Action: Modify for physical endpoint 0/1.
Signed-off-by: Pratyush Anand pratyush.an...@st.com
---
On 08/06/2012 07:21 AM, Olivier Sobrie wrote:
This driver provides support for several Kvaser CAN/USB devices.
Such kind of devices supports up to three can network interfaces.
s/can/CAN/
It has been tested with a Kvaser USB Leaf Light (one network interface)
connected to a pch_can
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable phy. Tested with
smdk6410 and smdkv310. More SoCs can be brought under later.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
---
Adding the transceiver to hsotg driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Praveen Paneri p.pan...@samsung.com
---
drivers/usb/gadget/s3c-hsotg.c | 38 --
1 files changed, 28
This patch removes old phy code from platform side. 'setup-usb-phy.c'
will be used for providing transceiver platform data in next
patch. Not all of the platform data code is removed as there are others
making use of platform_data defined for hsotg. That can be removed once
all the SoCs start
Changes from v1:
Rebased patches to latest usb-next branch
Changed the name 'sec_usbphy' to 'samsung_usbphy'
This patch set introduces a phy driver for samsung SoCs. It uses the existing
transceiver infrastructure to provide phy control functions. Use of this driver
can be extended for usb host
Adding usbphy node for Exynos4210 along with the platform data.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
---
arch/arm/boot/dts/exynos4210.dtsi |5 +
arch/arm/mach-exynos/include/mach/map.h |1 +
arch/arm/mach-exynos/mach-exynos4-dt.c |8
Adding platform device for samsung_usbphy driver. Enabling it for
s3c64xx based machines using s3c-hsotg.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
---
arch/arm/mach-s3c64xx/include/mach/map.h |2 +
arch/arm/mach-s3c64xx/mach-crag6410.c|3 ++
Le 07/08/2012 03:43, Dmitry Torokhov a écrit :
On Tue, Aug 07, 2012 at 02:56:40AM +0200, Yann Cantin wrote:
Hi,
Le 06/08/2012 23:43, Greg KH a écrit :
On Mon, Aug 06, 2012 at 11:21:44PM +0200, Yann Cantin wrote:
Signed-off-by: Yann Cantin yann.can...@laposte.net
---
Hi Praveen,
Some minor comments:
On 7 August 2012 12:58, Praveen Paneri p.pan...@samsung.com wrote:
Adding the transceiver to hsotg driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Praveen Paneri p.pan...@samsung.com
---
Le 07/08/2012 03:45, Dmitry Torokhov a écrit :
On Tue, Aug 07, 2012 at 03:21:45AM +0200, Yann Cantin wrote:
Le 07/08/2012 00:07, Dmitry Torokhov a écrit :
On Monday, August 06, 2012 02:43:40 PM Greg KH wrote:
On Mon, Aug 06, 2012 at 11:21:43PM +0200, Yann Cantin wrote:
Signed-off-by: Yann
Am Dienstag, 7. August 2012, 09:28:40 schrieb Praveen Paneri:
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable phy. Tested with
smdk6410 and smdkv310. More SoCs can be brought under later.
Signed-off-by: Praveen
In case of USB bulk transfer, when himem page
is received, the usb_sg_init function sets the
urb transfer buffer to NULL. When such URB
transfer is handled, kernel crashes in PIO mode.
Handle this by mapping the highmem buffer in PIO mode.
Signed-off-by: Virupax Sadashivpetimath
On Tue, 07 Aug 2012 11:04:10 +0800
Peiyong Feng peiyong.feng.ker...@gmail.com wrote:
2012/8/6 Lukasz Majewski l.majew...@samsung.com:
Hi,
Hi,
On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote:
I got a kernel panic when try hsotg of ok6410 which is based on
s3c6410:
Praveen Paneri wrote:
Changes from v1:
Rebased patches to latest usb-next branch
Changed the name 'sec_usbphy' to 'samsung_usbphy'
Yes, looks better. But I'm not sure Felipe or Greg would prefer to use '_'
not '-'...you used samsung-usbphy as a name in your patch.
This patch set
Hello.
On 07.08.2012 2:29, Steven J. Hill wrote:
From: Steven J. Hill sjh...@mips.com
One line fix after 'struct ehci_regs' definition was changed
in commit a46af4ebf9ffec35eea0390e89935197b833dc61.
Please also specify that commit's summary in parens.
Signed-off-by: Steven J. Hill
On Tue, Aug 7, 2012 at 1:41 PM, Heiko Stübner he...@sntech.de wrote:
Am Dienstag, 7. August 2012, 09:28:40 schrieb Praveen Paneri:
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable phy. Tested with
smdk6410 and
Thanks Sachin! Will incorporate.
On Tue, Aug 7, 2012 at 1:33 PM, Sachin Kamat sachin.ka...@linaro.org wrote:
Hi Praveen,
Some minor comments:
On 7 August 2012 12:58, Praveen Paneri p.pan...@samsung.com wrote:
Adding the transceiver to hsotg driver. Keeping the platform data
for continuing
On Tue, Aug 7, 2012 at 3:30 PM, Kukjin Kim kgene@samsung.com wrote:
Praveen Paneri wrote:
Changes from v1:
Rebased patches to latest usb-next branch
Changed the name 'sec_usbphy' to 'samsung_usbphy'
Yes, looks better. But I'm not sure Felipe or Greg would prefer to use '_'
not
The following warnings are fixed:
drivers/usb/musb/musb_core.c:357:6: warning: symbol 'musb_otg_timer_func' was
not declared. Should it be static?
drivers/usb/musb/musb_core.c:1339:27: warning: incorrect type in initializer
(different address spaces)
drivers/usb/musb/musb_core.c:1339:27:
drivers/usb/host/xhci.c:1826:14: warning: symbol 'xhci_get_block_size' was not
declared. Should it be static?
drivers/usb/host/xhci.c:1844:14: warning: symbol 'xhci_get_largest_overhead'
was not declared. Should it be static?
drivers/usb/host/xhci-ring.c:2304:36: warning: context imbalance in
On Tuesday, August 07, 2012, Ming Lei wrote:
On Mon, Aug 6, 2012 at 10:47 PM, Alan Stern st...@rowland.harvard.edu wrote:
No, no, you have completely misunderstood the whole point of this
change.
Sorry, you are right. And the callback should be renamed as
'.runtime_post_resume', which
When MISSED_ISOC is set, BUSY is also set. Since, we are handling
MISSED_ISOC as a separate case in third scenario, therefore handle only
BUSY but not MISSED_ISOC in second scenario.
Signed-off-by: Pratyush Anand pratyush.an...@st.com
---
drivers/usb/dwc3/gadget.c |3 ++-
1 files changed, 2
Hi,
On Tue, Aug 07, 2012 at 10:37:19AM +0800, yuzheng ma wrote:
This path fix musb_start_urb oops
diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
index e090c79..63303c7 100644
--- a/drivers/usb/musb/musb_host.c
+++ b/drivers/usb/musb/musb_host.c
@@ -2045,7 +2045,7
Hi,
On Thu, Aug 02, 2012 at 11:11:40AM +0300, Roger Quadros wrote:
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect more data than the endpoint's packet size and
have not yet received a short packet.
The last packet if short is always transferred using DMA
Hi Robert/Felipie
On Thu, Aug 2, 2012 at 1:41 PM, Roger Quadros rog...@ti.com wrote:
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect more data than the endpoint's packet size and
have not yet received a short packet.
The last packet if short is always
On Tue, Aug 7, 2012 at 5:26 PM, Rajaram R rajaram.officem...@gmail.com wrote:
Hi Robert/Felipie
On Thu, Aug 2, 2012 at 1:41 PM, Roger Quadros rog...@ti.com wrote:
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect more data than the endpoint's packet size and
Hi,
On 08/07/2012 02:57 PM, Rajaram R wrote:
On Tue, Aug 7, 2012 at 5:26 PM, Rajaram R rajaram.officem...@gmail.com
wrote:
Hi Robert/Felipie
On Thu, Aug 2, 2012 at 1:41 PM, Roger Quadros rog...@ti.com wrote:
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we
On Monday, August 06, 2012, Rafael J. Wysocki wrote:
On Monday, August 06, 2012, Alan Stern wrote:
On Sun, 5 Aug 2012, Rafael J. Wysocki wrote:
[...]
What about the appended experimental patch?
For now, I think it would be best to start with a single func argument.
If it turns
Hi,
On Tue, Aug 07, 2012 at 04:54:18PM +0530, Pratyush Anand wrote:
When MISSED_ISOC is set, BUSY is also set. Since, we are handling
MISSED_ISOC as a separate case in third scenario, therefore handle only
BUSY but not MISSED_ISOC in second scenario.
Signed-off-by: Pratyush Anand
On 8/7/2012 5:54 PM, Felipe Balbi wrote:
Hi,
On Tue, Aug 07, 2012 at 04:54:18PM +0530, Pratyush Anand wrote:
When MISSED_ISOC is set, BUSY is also set. Since, we are handling
MISSED_ISOC as a separate case in third scenario, therefore handle only
BUSY but not MISSED_ISOC in second scenario.
On Tue, Aug 07, 2012 at 06:09:10PM +0530, Pratyush Anand wrote:
On 8/7/2012 5:54 PM, Felipe Balbi wrote:
Hi,
On Tue, Aug 07, 2012 at 04:54:18PM +0530, Pratyush Anand wrote:
When MISSED_ISOC is set, BUSY is also set. Since, we are handling
MISSED_ISOC as a separate case in third scenario,
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect data of at least the endpoint's packet size and
have not yet received a short packet.
The last packet if short is always transferred using DMA mode 0.
This patch fixes USB throughput issues in mass storage mode
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/musb/musb_gadget.c | 34 +++---
1 files changed, 15 insertions(+), 19 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget.c b/drivers/usb/musb/musb_gadget.c
index 5c4392b..2bb50ca 100644
---
On Tue, Aug 07, 2012 at 04:09:57PM +0300, Roger Quadros wrote:
Signed-off-by: Roger Quadros rog...@ti.com
a little pedantic, but I really need a commit log here ;-)
--
balbi
signature.asc
Description: Digital signature
Remove unnecessary if condition. No change in logic.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/musb/musb_gadget.c | 34 +++---
1 files changed, 15 insertions(+), 19 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget.c
unsubscribe linux-usb
--
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
On 8/7/2012 7:06 PM, pkond...@codeaurora.org wrote:
unsubscribe linux-usb
Sorry for the noise and spam :-( For some reason, I stopped receiving
emails from this list. I am suggested to re-subscribe to the list. I end
up sending unsubscribe request to wrong list. Every thing is good now.
Currently the errors returned by fifo_setup get masked
by EINVAL, propagate the same to the caller.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/usb/musb/musb_core.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c
The function usb_add_phy trusts the sanity of the caller.
Also it accesses x after the NULL check.
Remove the unneeded check.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/usb/otg/otg.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Hi Laurent,
Thanks for your review.
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Tuesday, August 07, 2012 8:23 PM
To: Bhupesh SHARMA
Cc: linux-usb@vger.kernel.org; ba...@ti.com
Subject: Re: [PATCH V2 1/2] usb: gadget/uvc: Port UVC
On Tue, 7 Aug 2012, Ming Lei wrote:
On Tue, Aug 7, 2012 at 7:23 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Yes, I agree, but I don't think it may make .runtime_post_resume
not doable, do I?
No more device PM callbacks, please.
IMO, what the patch is doing is to introduce one callback
Thanks Felipe! I'll send it off to Greg today.
Sarah Sharp
On Tue, Aug 07, 2012 at 02:10:03PM +0300, Felipe Balbi wrote:
drivers/usb/host/xhci.c:1826:14: warning: symbol 'xhci_get_block_size' was
not declared. Should it be static?
drivers/usb/host/xhci.c:1844:14: warning: symbol
Signed-off-by: Andy Shevchenko andriy.shevche...@linux.intel.com
---
drivers/usb/gadget/rndis.c | 22 ++
1 file changed, 2 insertions(+), 20 deletions(-)
diff --git a/drivers/usb/gadget/rndis.c b/drivers/usb/gadget/rndis.c
index b35babe..e4192b8 100644
---
On Tue, Aug 7, 2012 at 11:42 PM, Alan Stern st...@rowland.harvard.edu wrote:
No, that's really not what the patch is doing.
The idea behind the new API is that func will be called as soon as we
know the device is at full power. That could be after the next runtime
resume or it could be
On Mon, Aug 06, 2012 at 03:14:36PM +0200, Lukasz Majewski wrote:
On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote:
I got a kernel panic when try hsotg of ok6410 which is based on
s3c6410:
As you said, you are using the ok6410. And it is based on the s3c6410
CPU. S3C6410 is a
Hello.
On 08/07/2012 05:09 PM, Roger Quadros wrote:
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect data of at least the endpoint's packet size and
have not yet received a short packet.
The last packet if short is always transferred using DMA mode 0.
Hello.
On 08/07/2012 05:09 PM, Roger Quadros wrote:
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/usb/musb/musb_gadget.c | 34 +++---
1 files changed, 15 insertions(+), 19 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget.c
On Tue, 7 Aug 2012, Rafael J. Wysocki wrote:
All those changes (and some of the following ones) are symptoms of a
basic mistake in this approach.
Every time you say something like this (i.e. liks someone who knows better)
s/liks/like/
I kind of feel like being under attach,
Andy Shevchenko andriy.shevche...@linux.intel.com writes:
Signed-off-by: Andy Shevchenko andriy.shevche...@linux.intel.com
Obviously.
Acked-by: Michal Nazarewicz min...@mina86.com
In addition, it also adds ACSII print out. :)
---
drivers/usb/gadget/rndis.c | 22 ++
On Mon, 6 Aug 2012, Kuninori Morimoto wrote:
This patch enables to call platform specific power callback function.
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
For all four patches in this series:
Acked-by: Alan Stern st...@rowland.harvard.edu
--
To unsubscribe from
Hi Denis,
I found a couple issues with your second patch. There are non-PCI xHCI
host controllers, so we can't assume the xHCI host is a PCI host. So
this code can't run in the generic xHCI shutdown method:
void xhci_shutdown(struct usb_hcd *hcd)
{
+ struct pci_dev *pdev;
+ const
On Tue, 7 Aug 2012, Virupax Sadashivpetimath wrote:
In case of USB bulk transfer, when himem page
is received, the usb_sg_init function sets the
urb transfer buffer to NULL. When such URB
transfer is handled, kernel crashes in PIO mode.
Handle this by mapping the highmem buffer in PIO mode.
On Tue, Aug 07, 2012 at 05:44:34PM +, Ian Atkin wrote:
Hi,
Don't know if this is the right place to ask about USB 3 support and legacy
kernels, so apologies in advance if it is not. I have an ageing Linux
environment based on the OpenSuse 2.6.27.7 kernel. This environment is an OEM
On Tue, Aug 07, 2012 at 10:49:00AM -0700, Sarah Sharp wrote:
On Tue, Aug 07, 2012 at 05:44:34PM +, Ian Atkin wrote:
Hi,
Don't know if this is the right place to ask about USB 3 support and
legacy kernels, so apologies in advance if it is not. I have an
ageing Linux environment
Hi Greg and Sarah,
First, thank you both for replying so promptly. I'm still here at work hunched
over my keyboard (surrounded by new hardware) wondering what to do.. ;-)
[Sarah said...]
It's going to be pretty hard to port all 1000+ xHCI patches to the
2.6.27 kernel. I had to touch parts of
On Mon, 6 Aug 2012, Tomas Sokorai wrote:
Ding, Ding, Ding!, we have a winner :-)
I did an ugly check:
if (ohci-ed_rm_list)
finish_unlinks (ohci, ohci_frame_no(ohci));
if ((ints OHCI_INTR_SF) != 0
!ohci-ed_rm_list
On Tuesday, August 07, 2012, Ming Lei wrote:
On Tue, Aug 7, 2012 at 7:23 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Yes, I agree, but I don't think it may make .runtime_post_resume
not doable, do I?
No more device PM callbacks, please.
IMO, what the patch is doing is to introduce one
On Tuesday, August 07, 2012, Ming Lei wrote:
On Tue, Aug 7, 2012 at 11:42 PM, Alan Stern st...@rowland.harvard.edu wrote:
No, that's really not what the patch is doing.
The idea behind the new API is that func will be called as soon as we
know the device is at full power. That could be
On Tuesday, August 07, 2012, Alan Stern wrote:
On Tue, 7 Aug 2012, Rafael J. Wysocki wrote:
All those changes (and some of the following ones) are symptoms of a
basic mistake in this approach.
Every time you say something like this (i.e. liks someone who knows
better)
We allocate memory for 'req' with usb_alloc_urb() and then test
'if (!req || rx_submit(pnd, req, GFP_KERNEL | __GFP_COLD))'.
If we enter that branch due to '!req' then there is no problem. But if
we enter the branch due to 'req' being != 0 and the 'rx_submit()' call
being false, then we'll leak
On Fri, Aug 03, 2012 at 12:17:03PM +0300, Felipe Balbi wrote:
Hi Greg,
here's a small set of fixes for v3.6-rc1. They're all on MUSB drivers
and are quite simple. Let me know if you want me to change anythying.
cheers
The following changes since commit
On Thu, Jul 26, 2012 at 08:44:33AM +, Fangxiaozhi (Franko) wrote:
From: fangxiaozhi huana...@huawei.com
1. This patch is based on the kernel of 3.5
2. In this patch, we add new micro for matching the series USB devices with
vendor ID and interface information.
3. In this patch, we add
On Wed, Aug 01, 2012 at 02:05:18AM +, Fangxiaozhi (Franko) wrote:
From: fangxiaozhi huana...@huawei.com
1. This patch is based on the kernel of 3.5
2. In this patch, we add new micro for matching the series USB devices with
vendor ID and interface information.
3. In this patch, we add
Hi Alen/Peter ,
I do get the following error while the system is up and
running . Basically the USB device get disconnected . Any
insight into the problem ?
[160549.977172] hub 2-1:1.0: state 7 ports 6 chg evt 0010^M
[160549.977275] ehci_hcd :00:1d.0: detected
On Tue, Aug 7, 2012 at 3:42 PM, Alan Stern st...@rowland.harvard.edu wrote:
I don't have time today to look further into this, but I'll get back to
you later.
No hurries, in fact I was gathering a bit more info about this behavior.
I dumped the ed_rm_list when it is hung, and we have only one
[160549.977524] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
3^M
[160549.977528] hub 2-1:1.0: port 4, status 0100, change 0001, 12 Mb/s^M
[160549.977650] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
4^M
[160549.977652] usb 2-1.4: USB disconnect, address 3^M
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/tty/serial/vt8500_serial.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/tty/serial/vt8500_serial.c
b/drivers/tty/serial/vt8500_serial.c
index 2be006f..a7f58c9 100644
--- a/drivers/tty/serial/vt8500_serial.c
+++
This patchset updates arch-vt8500 to devicetree and removes all the old-style
code. Support for WM8650 has also been added.
Example dts/dtsi files are given for the three currently supported models.
Major changes:
GPIO code has been converted to a platform_device and rewritten as WM8505
support
Add devicetree support for vt8500-ehci.
Convert vt8500-uhci to a generic non-pci platform-uhci with
device tree support.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/usb/host/Kconfig |4 +-
drivers/usb/host/ehci-vt8500.c | 24 --
drivers/usb/host/uhci-hcd.c
Converted the existing arch-vt8500 gpio to a platform_device.
Added support for WM8505 and WM8650 GPIO controllers.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/gpio/Kconfig |6 +
drivers/gpio/Makefile |1 +
drivers/gpio/gpio-vt8500.c | 318
Bindings for gpio, interrupt controller, power management controller,
timer, realtime clock, serial uart, ehci and uhci controllers and
framebuffer controllers used on the arch-vt8500 platform.
Framebuffer binding also specifies a 'display' node which is required
for determining the lcd panel
Update vt8500-fb, wm8505-fb and wmt-ge-rops to support device
tree bindings.
Small change in wm8505-fb.c to support WM8650 framebuffer color
format.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/video/Kconfig |6 +--
drivers/video/vt8500lcdfb.c | 77
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/rtc/rtc-vt8500.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/rtc/rtc-vt8500.c b/drivers/rtc/rtc-vt8500.c
index 9e94fb1..7364564 100644
--- a/drivers/rtc/rtc-vt8500.c
+++ b/drivers/rtc/rtc-vt8500.c
@@ -23,6 +23,7
Add device tree files for VT8500, WM8505 and WM8650 SoC's and
reference boards.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
arch/arm/boot/dts/vt8500.dtsi| 99 ++
arch/arm/boot/dts/vt8500_ref.dts | 31 ++
arch/arm/boot/dts/wm8505.dtsi| 125
On Wed, Aug 8, 2012 at 4:45 AM, Rafael J. Wysocki r...@sisk.pl wrote:
On Tuesday, August 07, 2012, Ming Lei wrote:
On Tue, Aug 7, 2012 at 7:23 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Yes, I agree, but I don't think it may make .runtime_post_resume
not doable, do I?
No more device PM
On Wed, Aug 08, 2012 at 01:57:06AM +, Fangxiaozhi (Franko) wrote:
Dear Greg：
Sorry, this email has included the whole patch. 1/8, I mean that it is submit
at Aug. 1st.
No, please don't put the date in the Subject:, that's what the normal
Date field in the email is for :)
By the way,
Sorry guys I was away due to personal emergency, however now I am back
and will check the reply ASAP.
On 28 July 2012 21:49, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 28 Jul 2012, Daniel Mack wrote:
Hmm, interesting. Thanks for sharing this. I personally never saw this
bug kicking
Hi Julia,
On Tue, Jul 24 2012, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
Add missing usb_free_urb on failure path after usb_alloc_urb.
Thanks, pushed to mmc-next for 3.7.
- Chris.
--
Chris Ball c...@laptop.org http://printf.net/
One Laptop Per Child
--
To unsubscribe
2012/8/7 Lukasz Majewski l.majew...@samsung.com:
On Tue, 07 Aug 2012 11:04:10 +0800
Peiyong Feng peiyong.feng.ker...@gmail.com wrote:
2012/8/6 Lukasz Majewski l.majew...@samsung.com:
Hi,
Hi,
On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote:
I got a kernel panic when
Hi Oliver,
On Mon, Aug 06, 2012 at 10:10:43AM +0200, Oliver Neukum wrote:
On Monday 06 August 2012 07:21:29 Olivier Sobrie wrote:
This driver provides support for several Kvaser CAN/USB devices.
Such kind of devices supports up to three can network interfaces.
It has been tested with a
On Tue, Aug 7, 2012 at 6:39 PM, Roger Quadros rog...@ti.com wrote:
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect data of at least the endpoint's packet size and
have not yet received a short packet.
Could you please let us know what all combination this was
82 matches
Mail list logo
