On Mon, Dec 26, 2005 at 03:48:19PM +0000, Daniel Drake wrote:
> Alan Stern wrote:
> >I didn't go through the details of the firmware transfer, but everything
> >else looked correct. It's not obvious why the device doesn't respond to
> >your program.
>
> I just found the problem.
>
> I upgraded to amd64 and my driver didn't work at all. Kernel panic
> ("PCI-DMA: high address but no IOMMU") during the first firmware packet
> transfer.
>
> Turns out you can't just use the data part of the firmware struct in
> usb_control_msg context, you have to copy it to a GFP_ATOMIC buffer. Oops!
Or any type of kmalloced buffer.
> After fixing that, I get an interrupt at the point when it is expected.
>
> You hereby have permission to slap me silly :)
You aren't the only one that has done this in the past, so don't feel
bad :)
Glad it's working for you now.
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
