HUSAM AL SAYED | 26 May 20:00 2014

Your Urgent reply.

Dear Friend,

Compliments of the day.This mail May be a surprise to you Because you
did not give me the permission to do so and Neither do you know me but
before I tell you about myself I want you to please forgive me for
sending this mail without your permission I have been in search of
someone with this last name so when I saw you online, I was pushed to
contact you and see how best we can assist each other. I am Mr. Husam
Al Sayed, a Bank Officer here in U.A.E. I believe it is the wish of
God for me to come across you now. I am having an important business
discussion I wish to share with you which I  believe will interest
you, because it is in connection with your last name and you are going
to benefit from it.

One Late peter who was among the death victims in the May 27 2006
Earthquake disaster in Java, Indonesia that killed over 5,000 people.
He was in Indonesia on a business trip and that was how he met his
end. My bank management is yet to know about his death, I knew about
it because he was my friend and I am his account officer.he did not
mention any Next of Kin/ Heir when the account was opened, and he was
not married and no children. Last week my Bank Management requested
that he should give instructions on what to do about his funds,I know
this will happen and that is why I have been looking for a means to
handle the situation,

If you are interested send me your private Email Address so that i can
send you more details of the transaction,
Thanks for your understanding

I am waiting for your reply.
(Continue reading)

Mathias Nyman | 26 May 16:47 2014
Picon

Re: ASMedia AS2105 interface on USB 3.0 corrupts data

On 05/22/2014 05:22 PM, David Laight wrote:
> From: Alan Stern
>> On Thu, 22 May 2014, Heinz Diehl wrote:
>>
>>> On 21.05.2014, Alan Stern wrote:
>>>
>>>> In that case, I have no idea what else could be causing the problem.
>>>
>>> Thanks for your	efforts!
>>>
>>> If somebody of the developers is interested in debugging this, I'm
>>> willing to provide/give away the device for free. Send me
>>> an email with your postal adress in this case, and I'll send you
>>> the controller mentioned in this thread. My GPG-key is available
>>> from the link given in the header.
>>
>> Mathias, this sounds like a pretty good opportunity for somebody at
>> Intel to use a USB-3 bus analyzer to solve some of the recurring
>> problems that have been affecting many people using Intel's xHCI
>> controllers.
> 
> I'd also suggest you look through the patches I've posted.
> Some of the changes would make the code much easier to read.
> 

Hi

Seems that I lost track of which patches you refer to here,
could you point out the relevant ones to me again?

(Continue reading)

Mathias Nyman | 26 May 16:43 2014
Picon

Re: ASMedia AS2105 interface on USB 3.0 corrupts data

On 05/22/2014 05:10 PM, Alan Stern wrote:
> On Thu, 22 May 2014, Heinz Diehl wrote:
> 
>> On 21.05.2014, Alan Stern wrote:
>>
>>> In that case, I have no idea what else could be causing the problem.
>>
>> Thanks for your	efforts!
>>
>> If somebody of the developers is interested in debugging this, I'm
>> willing to provide/give away the device for free. Send me
>> an email with your postal adress in this case, and I'll send you 
>> the controller mentioned in this thread. My GPG-key is available 
>> from the link given in the header.
> 
> Mathias, this sounds like a pretty good opportunity for somebody at
> Intel to use a USB-3 bus analyzer to solve some of the recurring
> problems that have been affecting many people using Intel's xHCI
> controllers.
> 

This would be helpful, I've got a LeCroy protocol analyzer in Finland.

Heinz, if you're willing to send it to Europe Finland I'll gladly take it,
(I'll send the address details in a separate personal mail)

Otherwise if you can tell me where exactly what device this is I might
be able to purchase a similar one.

Thanks
(Continue reading)

Sergei Shtylyov | 26 May 16:12 2014

Re: [PATCH v2 4/6] usb: musb: fix bit masks for CSR in musb_h_tx_flush_fifo()

Hello.

On 05/24/2014 11:22 AM, Daniel Mack wrote:

>>> I I'd say it's not supposed to. I just wanted the bit to be 0 when
>>> writing back the CSR.

>>     You failed to achieve that since you forgot ~; you're clearing all bits but
>> this one.

> Ouch, totally missed that, thanks!

    And I've missed CSR0 thing at first, so we have a tie. :-)

>>>>> diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
>>>>> index f98a7c0..9d3a5b2 100644
>>>>> --- a/drivers/usb/musb/musb_host.c
>>>>> +++ b/drivers/usb/musb/musb_host.c
>>>>>  <at>  <at>  -120,7 +120,8  <at>  <at>  static void musb_h_tx_flush_fifo(struct musb_hw_ep *ep)
>>>>>     		if (csr != lastcsr)
>>>>>     			dev_dbg(musb->controller, "Host TX FIFONOTEMPTY csr: %02x\n", csr);
>>>>>     		lastcsr = csr;
>>>>> -		csr |= MUSB_TXCSR_FLUSHFIFO;
>>>>> +		csr &= MUSB_TXCSR_H_RXSTALL;
>>>>> +		csr |= MUSB_TXCSR_FLUSHFIFO | MUSB_CSR0_TXPKTRDY;

>>      Yes, the manual tells us to set TxPktRdy along with FlushFIFO. This has
>> been a long standing bug, perhaps because the old versions of the MUSBHDRC
>> manuals didn't mention that.

(Continue reading)

Daniel Mack | 26 May 14:52 2014
Picon

[PATCH v4 0/7] Multiple fixes for musb and cppi41

Here is v4 of my cleanup series for musb in CPPI DMA mode.

v3 -> v4:
	* s/MUSB_CSR0_TXPKTRDY/MUSB_TXCSR_TXPKTRDY/ in patch #4
	* s/packet_done/rx_packet_done/ in #5

v2 -> v3:
	* Dropped the RXSTALL bit modification from patch #4
	* Droped some occasions where musb_ep_select() is not
	  necessary, in patch #6
	* Slightly reworded the commit log of #5
	* Added a 7th patch to fix a wrongly indented block
	  in musb_host.c

v1 -> v2:
	* Some commit logs fixed and reworded
	* Squashed #6 and #7, as they are basically doing the same
	  thing
	* Added some more occasions where musb_ep_select() was
	  missing before CSR register access, and added those
	  hunks to #6 as well.

With this series applied, iperf works correctly with Wifi sticks
connected via USB.

Again, #1 can go via slave-dma.git, and #3 - #6 are potentially
interesting for stable <at> .

Thanks,
Daniel
(Continue reading)

Bjørn Mork | 26 May 12:53 2014
Picon

[PATCH net-next 0/8] cdc_ncm: fixes and conversion to sysfs API

After considering the comments received after the ethtool coalesce
support was commited, I have ended up concluding that we should
remove it again, while we can, before it hits a release. The idea
was not well enough thought through, and all comments received
pointed to advantages of using a sysfs based API instead.

This series removes the ethtool coalesce support and replaces it
with sysfs attributes in a driver specific group under the netdev.

The first 3 patches are unrelated fixes:

patch 1: reducing truesize as discussed
patch 2: fixing a potentional buffer overrun when changing tx_max
patch 3: prevent framing errors when changing rx_max

Bjørn Mork (8):
  net: cdc_ncm: reduce skb truesize in rx path
  net: cdc_ncm: always reallocate tx_curr_skb when tx_max increases
  net: cdc_ncm: inform usbnet when rx buffers are reduced
  net: cdc_ncm: use sysfs for rx/tx aggregation tuning
  net: cdc_ncm: drop ethtool coalesce support
  net: cdc_ncm: export NCM Transfer Block (NTB) parameters
  net: cdc_ncm: allow tuning min_tx_pkt
  net: cdc_ncm: document the sysfs API

 Documentation/ABI/testing/sysfs-class-net-cdc_ncm | 143 ++++++++++++
 drivers/net/usb/cdc_ncm.c                         | 268 ++++++++++++++++------
 2 files changed, 335 insertions(+), 76 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-class-net-cdc_ncm

(Continue reading)

Kishon Vijay Abraham I | 26 May 11:42 2014
Picon

Re: [PATCH 1/5] phy: add support for USB cluster on the Armada 375 SoC

hI,

On Saturday 24 May 2014 03:20 AM, Gregory CLEMENT wrote:
> On 23/05/2014 11:20, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Friday 16 May 2014 09:52 PM, Gregory CLEMENT wrote:
>>> The Armada 375 SoC comes with an USB2 host and device controller and
>>> an USB3 controller. The USB cluster control register allows to manage
>>> common features of both USB controllers.
>>>
>>> This commit adds a driver integrated in the generic PHY framework to
>>> control this USB cluster feature.
>>>
>>> Signed-off-by: Gregory CLEMENT <gregory.clement@...>
>>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@...>
>>> ---
>>>  drivers/phy/Kconfig                              |   6 +
>>>  drivers/phy/Makefile                             |   1 +
>>>  drivers/phy/phy-armada375-usb2.c                 | 140 +++++++++++++++++++++++
>>>  include/dt-bindings/phy/armada-375-usb-cluster.h |  18 +++
> [...]
> 
>>> +static struct phy_ops armada375_usb_phy_ops = {
>>> +	.init = armada375_usb_phy_init,
>>> +	.owner		= THIS_MODULE,
>>
>> nitpick: unnecessary tab.
> 
> OK
(Continue reading)

Picon

WILL EXECUTION!!!?

Late Mr.Robert Adler bequeathed US$20,500,000.00 USD, to you in his will.More info,contact your
attorney(Clifford Chance Esq) via email address:
lawfirm.cliffordchanceesq@... Tell +447010043884 
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Daniel Mack | 25 May 10:36 2014
Picon

[PATCH v3 0/7] Multiple fixes for musb and cppi41

Here is v3 of my cleanup series for musb in CPPI DMA mode.

v2 -> v3:
	* Dropped the RXSTALL bit modification from patch #4
	* Droped some occasions where musb_ep_select() is not
	  necessary, in patch #6
	* Slightly reworded the commit log of #5
	* Added a 7th patch to fix a wrongly indented block
	  in musb_host.c

v1 -> v2:
	* Some commit logs fixed and reworded
	* Squashed #6 and #7, as they are basically doing the same
	  thing
	* Added some more occasions where musb_ep_select() was
	  missing before CSR register access, and added those
	  hunks to #6 as well.

With this series applied, iperf works correctly with Wifi sticks
connected via USB.

Again, #1 can go via slave-dma.git, and #3 - #6 are potentially
interesting for stable <at> .

Thanks,
Daniel

Daniel Mack (6):
  dma: cppi41: handle 0-length packets
  usb: musb: remove unnecessary (void) prefix at function calls
(Continue reading)

philippedeswert | 24 May 19:28 2014
Picon

[PATCH v3 0/4] libusbg: Fix potential issues found with coverity

From: Philippe De Swert <philippe.deswert@...>

This patch series fixes a number of issues found with coverity in libusbg
A pull request has also be made:
https://github.com/libusbg/libusbg/pull/4

This is the third revision with all comments corrected.

Philippe De Swert (4):
  libusbg: Fix readlink/buffer overrun issue. CID#56130, CID#56129
  libusbg: Fix buffer overrun issue. CID#56128
  libusbg: Do not try to dereference func when it is NULL. CID#56127
  libusbg: Do not dereference usb config attributes when they are NULL.
    CID#56126

 src/usbg.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

--

-- 
1.8.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Alan Stern | 24 May 17:18 2014
Picon

Re: ehci-hcd.c causes: irq <number>: nobody cared

On Sat, 24 May 2014, Dr. Werner Fink wrote:

> On Wed, May 14, 2014 at 10:32:21AM -0400, Alan Stern wrote:
> > On Tue, 13 May 2014, Dr. Werner Fink wrote:
> > 
> > > On Tue, May 13, 2014 at 06:10:46PM +0200, Dr. Werner Fink wrote:
> > > > On Tue, May 13, 2014 at 11:59:38AM -0400, Alan Stern wrote:
> > > > > 
> > > > > What about something like this instead?
> > > > > 
> > > > >  	masked_status = status & (INTR_MASK | STS_FLR);
> > > > >  
> > > > >  	/* Shared IRQ? */
> > > > >  	if (!masked_status || unlikely(ehci->rh_state == EHCI_RH_HALTED)) {
> > > > > +		if (status & STS_RECL) {
> > > > > +			ehci_writel(ehci, STS_RECL, &ehci->regs->status);
> > > > > +			ehci_readl(ehci, &ehci->regs->status);
> > > > > +		}
> > > > >  		spin_unlock_irqrestore(&ehci->lock, flags);
> > > > >  		return IRQ_NONE;
> > > > >  	}
> > > > > 
> > > > > That should do about the same thing as your change, except for
> > > > > returning IRQ_NONE rather than IRQ_HANDLED.
> > > > 
> > > > I'll forward this to my home to try it out.  It will take some time
> > > > as my wife is also working on this system.  Nevertheless I'm curious
> > > > about it.
> > > 
> > > The code is active now:
(Continue reading)


Gmane