Hi Andreas, On 7/27/14, Andreas Färber <afaerber@xxxxxxx> wrote: > Hi Ajay, > > Am 25.07.2014 21:22, schrieb Ajay Kumar: >> This series is based on exynos-drm-next branch of Inki Dae's tree at: >> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git >> >> I have tested this after adding few DT changes for exynos5250-snow, >> exynos5420-peach-pit and exynos5800-peach-pi boards. > > I'm trying to test this with a modified exynos5250-spring DT based off > kgene's for-next branch due to DT, and I run into the following: > > CC drivers/gpu/drm/bridge/ptn3460.o > drivers/gpu/drm/bridge/ptn3460.c: In function ‘ptn3460_post_encoder_init’: > drivers/gpu/drm/bridge/ptn3460.c:275:2: error: implicit declaration of > function ‘drm_connector_register’ [-Werror=implicit-function-declaration] > drm_connector_register(&ptn_bridge->connector); > ^ Hope this might help: http://www.spinics.net/lists/dri-devel/msg60578.html Switch back to drm_sysfs_connector_add if your kernel doesn't have this patch. Ajay > cc1: some warnings being treated as errors > scripts/Makefile.build:257: recipe for target > 'drivers/gpu/drm/bridge/ptn3460.o' failed > make[4]: *** [drivers/gpu/drm/bridge/ptn3460.o] Error 1 > scripts/Makefile.build:404: recipe for target 'drivers/gpu/drm/bridge' > failed > make[3]: *** [drivers/gpu/drm/bridge] Error 2 > make[3]: *** Warte auf noch nicht beendete Prozesse... > scripts/Makefile.build:404: recipe for target 'drivers/gpu/drm' failed > make[2]: *** [drivers/gpu/drm] Error 2 > scripts/Makefile.build:404: recipe for target 'drivers/gpu' failed > make[1]: *** [drivers/gpu] Error 2 > Makefile:899: recipe for target 'drivers' failed > make: *** [drivers] Error 2 > > Any hint which prerequisite I'm missing? Didn't spot it in Inki's tree, > and it must be new since v4. > > Thanks, > Andreas > > -- > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
