Control: tag -1 moreinfo On Wed, 2014-05-07 at 18:10 -0700, Vagrant Cascadian wrote: > On Wed, May 07, 2014 at 01:46:53PM -0700, Vagrant Cascadian wrote: > > The following patch enables configuration options needed for use with > > BeagleBone Black. > > > > Ethernet, serial console, MMC support work. Video may require some > > additional > > patches from upstream... > > Updated patch with support for video output as modules: > CONFIG_DRM_I2C_NXP_TDA998X=m > CONFIG_DRM_TILCDC=m > > Thanks to Robert C. Nelson for the additional options! > > USB support seems flaky, at best... not sure if there are other options that > could improve that.
I think that's because the MUSB driver can only be built with support for one type of DMA controller, and so doesn't support DMA at all in multiplatform kernels. > live well, > vagrant > > diff --git a/config/armhf/config.armmp b/config/armhf/config.armmp > index c43f74e..0ab26fc 100644 > --- a/config/armhf/config.armmp > +++ b/config/armhf/config.armmp [...] > @@ -170,6 +185,8 @@ CONFIG_IMX_SDMA=y > CONFIG_IMX_DMA=y > CONFIG_MXS_DMA=y > CONFIG_DMA_OMAP=y > +CONFIG_TI_CPPI41=y Why not =m? (It looks like this is only needed for USB anyway, which means it's not used at all yet.) [...] > +## file: drivers/i2c/Kconfig > +## > +CONFIG_I2C_CHARDEV=y This symbol seems to be enabled in most configurations that have I2C, but often as a module. When built as a module, it won't be auto-loaded, though userland could explicitly load it if needed. What userland programs need this, and do they try to load the module (which will be needed in some configurations)? [...] > +CONFIG_SERIAL_OF_PLATFORM=y [...] This seems to select some glue code for 8250-like serial ports, and the following symbols don't depend on it. And in am33xx.dtsi, all the UARTs have compatible = "ti,omap3-uart". Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein
signature.asc
Description: This is a digitally signed message part
