D.
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 that the PLX software
>> team that worked on this driver is no longer with the company, so they
>> cannot o
a */" code
to determine if/why/when it's necessary?
On Fri, Jan 22, 2016 at 10:46 AM, Justin DeFields
wrote:
>
> 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 i
, Justin DeFields
wrote:
> 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 suppor
Alan,
Yes 'req->td->dmadesc = 0;' is set from within start_dma right before
the 'paranoia' block is called.
(adding email train back to list serv)
On Thu, Jan 21, 2016 at 4:41 PM, Alan Stern wrote:
> On Thu, 21 Jan 2016, Justin DeFields wrote:
>
>> Alan, I
, meaning that all short read/write
operations can be problematic
Does anyone have any ideas on this issue?
On Wed, Jan 20, 2016 at 2:43 PM, Justin DeFields
wrote:
> System: Custom Xilinx Zynq based system
> Kernel: Xilinx linux v2015.1 (linux 3.18)
>
> I was attempting to add support
termining if a
packet was short, or is there another way for a short OUT packet to be
triggered that I'm not accounting for (i.e. start_dma is not the
source of the packet)?
On Wed, Jan 20, 2016 at 2:43 PM, Justin DeFields
wrote:
> System: Custom Xilinx Zynq based system
> Kernel: Xi
d combinations of the various quirk flags in this
driver, and most didn't change driver operation at all surprisingly
(or at least not to any degree that I could measure). I'm looking for
some assistance or tips in debugging this issue.
Thanks,
Justin DeFields
Embedded Software Enginee
