On 07/08/2013 03:40 PM, Paul Zimmerman wrote: >> From: Stephen Warren [mailto:swarren@xxxxxxxxxxxxx] >> Sent: Tuesday, July 02, 2013 7:41 PM >> >> On 07/02/2013 07:47 PM, Stephen Warren wrote: >>> On 06/26/2013 02:20 PM, Paul Zimmerman wrote: >> ... >>>> I hope whoever is supporting the Pi in the mainline kernel will try adding >>>> dwc2 support now that it seems to be working. I'm not sure who that would >>>> be, though. >>> >>> Well, it appears to work! I tested it on both a model A and B (rev 2) >>> and devices enumerate on the bus OK now. I haven't actually tested data >>> transfer yet though. >> >> ... although unfortunately, pretty much any use of the USB devices >> crashes or hangs the kernel:-( I guess due to the wildly varying >> symptoms, there is some random memory corruption going on. >> >> I did manage to dd about 1MiB off an SD card in a USB->SD card adapter >> (with powered hub between the adapter and the Pi), but often just >> plugging in the card or having it plugged in during boot causes hangs >> and crashes. Similarly, I have a ZD1211 WiFi USB adapter, and having >> that plugged during boot in causes all kinds of oops within a few or >> tens of seconds after booting, in code unrelated to USB or networking. >> >> Paul, are you able to try out upstream Linux and see what the issue >> might be? The following G+ post should outline the steps required: >> >> https://plus.google.com/101715070573995136397/posts/gWkwrfNfYVm >> >> although these days you might want to use u-boot.git not u-boot-arm.git >> (or perhaps git://github.com/swarren/u-boot.git rpi_dev), and >> git://github.com/swarren/linux-rpi.git rpi_dev to get the USB enabled. > > Hi Stephen, > > As I mentioned in private email, I was not able to get your > mainline-based kernel from git://github.com/swarren/linux-rpi.git > to boot. I would appreciate if you could send me your compiled > u-boot.bin and boot.scr.uimg, in case the problem is with compiling > u-boot. And also your kernel .config. Sorry for the slow response; holidays and birthday! The files you need are available at: http://avon.wwwdotorg.org/downloads/rpi-paulz-20130708/rpi-boot.tar You can simply untar that into /boot on partition 1 of an SD card. I don't believe you need any config.txt for the RPi firmware, although I currently have one that simply contains: gpu_mem=32 The source for the U-Boot and kernel binaries is available at: git://github.com/swarren/u-boot.git git://github.com/swarren/linux-rpi.git branch gpl-compliance/for-paulz-20130708 in both cases. The kernel .config file is (arch/arm/configs/) bcm2835_defconfig. I expect this to work with any recent RPi firmware. I've used at least 3 different versions successfully. FWIW, I appear to have the following firmware.git commit currently, which I believe I copied to the SD card: 470b34d "firmware: make recovery mode not use hdmi_safe, and let arm control mode userland: Report preferred mode in tvservice -m kernel: ignore I2C interrupts that aren't expected" (!) > I suspect the majority of the issues you saw are due to missing dt > support for several of the module parameters that need to be set to > non-default values for the pi, like the DMA mode and the FIFO sizes. Hmm. I thought the HW config registers reflected exactly how the USB HW was synthesized? It'd be odd to have registers that attempt to reflect that, but actually have incorrect data! I vaguely recall an earlier version of the DWC2 driver complaining, or perhaps even outright refusing to initialize(?), if the parameters provided to th driver didn't match up with the values in the HW registers. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
