Am 11.04.2013 20:29, schrieb Felipe Balbi: > and who said OMAP USB depends on CONFIG_USB_PHY ? Some platforms need to > control a PHY and some don't. I've read that so. > Go check out kernel 2.6.39 (maybe even 3.1 and 3.2) and you'll see that > we're much better off today where we can actually have multiple PHY > drivers and multiple UDC drivers enabled (either as modules or > built-in), but the fact is that changing all of this over takes time and > sometimes people make mistakes, but that's alright, since we have the > -rc series to catch those unwanted errors. I'll still have to stick to 3.2 because nothing afterwards boots from EHCI on my beagleboard. > > Without the help of the rest of the community, though, it'll just get > slower and slower. With the whole single zImage effort going on in the > ARM land, things have gotten much more critical WRT getting rid of > "selects" and turning legacy "drivers" into real drivers, not just a > bunch of exported functions which a single architecture uses. > > Add to that all the rework going on in the Gadget Framework, PHY layer > and EHCI drivers (which now has a core re-usable library thanks to Alan > Stern) and you have a lot of work to do. > > Next time you consider ranting about something, use that 'frustration' > and turn it into motivation to write patches, then we all win. Also I frequently tried and gave up. But thanks for the good suggestions. Regards, Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
