On Thu, Apr 03, 2014 at 02:51:16PM +0200, Alexander Graf wrote: > > I guess we can ask Sascha here too :). > > >The main things to do for boards support are : > >1) Get boards booting Linux (should be a minimum). > >2) Have a maximum number of supported devices (USB, sound, video, etc.) on > >each board (even if it does mean to have '=y' instead of '=m'). > >3) Clean-up / fix our kernel / kernel configs to use modules (=m) instead of > >built-in (=y) when it is possible. > > I agree with 1), but it'll be a real nightmare to clean things up > once we start going down the path of 2). Let's see if Sascha has > ideas to get us out of the mess where we need =y for things that > really shouldn't have to be compiled in.
I just tried vanilla v3.14 with the imx_v6_v7_defconfig. The OTG port on the sabrelite works for me. The other hoast ports bail out with: hub 2-0:1.0: cannot reset port 1 (err = -32) hub 2-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? I also tried building USB as modules, same result. Oh damn, sound fails badly when SDMA is compiled as a module: pc : [<801406a8>] lr : [<8031eca4>] psr: a0000113 sp : bf05fce0 ip : bf05fcf0 fp : bf05fcec r10: bf025f80 r9 : be89ffc0 r8 : bf13ac00 r7 : bf13ac10 r6 : fffffdfb r5 : bf7e3544 r4 : be89fe10 r3 : bf05e000 r2 : 00000000 r1 : 00000000 r0 : bf13ac18 Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c53c7d Table: 1000404a DAC: 00000017 Process swapper/0 (pid: 1, stack limit = 0xbf05e240) Stack: (0xbf05fce0 to 0xbf060000) fce0: bf05fcfc bf05fcf0 8031eca4 801406a8 bf05fdcc bf05fd00 8047fc8c 8031ec90 fd00: 00000000 be89ffc0 be89fe10 bf1249f8 bf05fd34 be89fe20 8014314c 02028000 fd20: 0202bfff bf7e3580 00000200 00000000 00000000 00000000 00000000 be8dcc08 fd40: 00000000 bf1249f8 00000000 80882014 bf05e000 00000001 bf05fd8c bf05fd68 fd60: 00000004 00000025 00000001 00000000 00000000 be8dcc08 bf05e000 00000001 fd80: bf05fdb4 bf05fd90 80141304 8014292c bf13ac10 bf13ac18 00000000 00000000 fda0: 80882014 bf13ac10 80882014 00000000 00000000 80882014 bf05e000 80820f48 fdc0: bf05fde4 bf05fdd0 80323af4 8047fa40 80dd0060 bf13ac10 bf05fe0c bf05fde8 fde0: 80322514 80323ae0 00000000 bf13ac10 80882014 bf13ac44 00000000 80814498 fe00: bf05fe2c bf05fe10 803226cc 80322408 bf11dcdc 00000000 80882014 80322630 fe20: bf05fe54 bf05fe30 80320ae4 8032263c bf0048a8 bf11dcd0 be8dd258 80882014 fe40: be8dd280 80861a80 bf05fe64 bf05fe58 8032200c 80320a94 bf05fe8c bf05fe68 fe60: 80321c08 80321ff8 8079d340 bf05fe78 80882014 00000006 8088c480 807e355c fe80: bf05fea4 bf05fe90 80322d84 80321b38 8082d478 00000006 bf05feb4 bf05fea8 fea0: 80323a14 80322d10 bf05fec4 bf05feb8 808144b0 803239d0 bf05ff54 bf05fec8 fec0: 80008a68 808144a4 805ecd00 800656cc 00000000 00000000 bf05ff1c bf05fee8 fee0: bf05ff0c bf05fef0 807e3500 80295590 807e355c bfffcc52 80605308 000000ae ff00: bf05ff54 bf05ff10 800430dc 807e3568 bf05ff34 00000006 00000006 807e0af0 ff20: 00000000 80789348 bf05ff54 8082d478 00000006 8088c480 807e355c 000000ae ff40: 80820f3c 80820f48 bf05ff94 bf05ff58 807e3cc0 80008980 00000006 00000006 ff60: 807e355c ffffffff bf05e000 00000000 805e1340 00000000 00000000 00000000 ff80: 00000000 00000000 bf05ffac bf05ff98 805e1350 807e3bc8 ffffffff 00000000 ffa0: 00000000 bf05ffb0 8000ebe8 805e134c 00000000 00000000 00000000 00000000 ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 ffffffff ffffffff Backtrace: [<8014069c>] (sysfs_remove_file_ns) from [<8031eca4>] (device_remove_file+0x20/0x24) [<8031ec84>] (device_remove_file) from [<8047fc8c>] (fsl_ssi_probe+0x258/0x748) [<8047fa34>] (fsl_ssi_probe) from [<80323af4>] (platform_drv_probe+0x20/0x50) ... I haven't looked into this, but this should be fixable quite easily. I'll have look. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
