On Tue, 5 Feb 2008 11:17:46 -0800 (PST), Siddharth Choudhuri <[EMAIL PROTECTED]> wrote:
> - Linux 2.6.19 on ARM > The problem is, I see the following in /tmp/log (no data words): > c04087dc 666657025 C Bo:002:02 0 31 > > c000ec14 666657209 S Bo:002:02 -115 512 D The problem stems from the fact that usbmon's hooks may not have access to the virtual address of the data. On cache-coherent architectures, such as x86, usbmon works around it by remapping data temporarily. I think the problem should be transparent if you look at the code in and around usb_hcd_submit_urb(). You can change usb-storage to not pre-map commands and replies easily, but data often comes from the highmem zone and thus kernel does not have its virtual address. So, if you want to see the data, you need to attack the main issue. If you find a way to implement mon_dmapeek() for ARM, I'll be happy to include it. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html