Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-05-20 Thread Tim Harvey
On Thu, May 12, 2016 at 3:48 PM, Justin DeFields wrote: > On Thu, May 12, 2016 at 6:27 PM, Tim Harvey wrote: >> On Tue, Jan 26, 2016 at 6:40 AM, Justin DeFields >> wrote: >>> I spoke with the Avago/PLX FAE, and they said

Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-05-12 Thread Justin DeFields
I've never received any answers for my questions unfortunately :(. If I remember correctly, just to get the deivce working (though I'm not sure how stable) I added a new structure for the 2380, and gave it all the same options as the 3380, except that I split the PLX_SUPERSPEED into 2 flags

Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-05-12 Thread Tim Harvey
On Tue, Jan 26, 2016 at 6:40 AM, Justin DeFields wrote: > I spoke with the Avago/PLX FAE, and they said that the PLX software > team that worked on this driver is no longer with the company, so they > cannot offer support :( > > I'm not sure there is going to be a good

Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-01-26 Thread Justin DeFields
I spoke with the Avago/PLX FAE, and they said that the PLX software team that worked on this driver is no longer with the company, so they cannot offer support :( I'm not sure there is going to be a good answer for this issue. Hopefully someone here can help me evaluate the "/* paranoia */" code

Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-01-22 Thread Justin DeFields
It turns out that I had a filesystem issue on my target when testing my removal of the /* paranoia */ block. I thought I was writing the file to NAND, when in fact it was being written over NFS to my Virtual Machine!!! After resolving this issue, and with the removal of the paranoia logic, the

Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-01-21 Thread Justin DeFields
In the start_dma function, I added the following lines at the start of the function: if (req->req.length % ep->ep.maxpacket) { printk("%s packet is short(%d)...\n", (ep->is_in) ? "IN" : "OUT", req->req.length); } The packet is never listed as short via my method above during this erroneous

Re: NET2280: Adding PLX usb2380 support (issues encountered)

2016-01-21 Thread Alan Stern
On Thu, 21 Jan 2016, Justin DeFields wrote: > In the start_dma function, I added the following lines at the start of > the function: > > if (req->req.length % ep->ep.maxpacket) > { > printk("%s packet is short(%d)...\n", (ep->is_in) ? "IN" : "OUT", > req->req.length); > } > > The packet is

NET2280: Adding PLX usb2380 support (issues encountered)

2016-01-20 Thread Justin DeFields
System: Custom Xilinx Zynq based system Kernel: Xilinx linux v2015.1 (linux 3.18) I was attempting to add support for the PLX usb2380 chip to the net2280.c driver. As far as I can tell, this chip is the same as the 3380, but does not support USB3.0 (2.0 only). I have changed all checks for the