[Buildroot] [PATCH 1/2] X11/odroidc2-driver: New Package.

daggs daggs at gmx.com
Sun Oct 23 04:40:40 UTC 2016


Greetings Arnout,

> On 20-10-16 19:41, daggs wrote:
> > Greetings Arnout,
> > 
> >> On 18-10-16 10:02, daggs wrote:
> >>> Greetings Arnout,
> >>>
> >>>> On 17-10-16 23:11, daggs wrote:
> >>>>
> >>
> >>>> [snip]
> >>>>>>> +XDRIVER_XF86_VIDEO_ODROIDC2_LICENSE_FILES = README.txt 
> >>>>>>> +XDRIVER_XF86_VIDEO_ODROIDC2_DEPENDENCIES = \
> >>>>>>> +	odroid-mali \
> >>>>>>> +	xproto_fontsproto \
> >>>>>>> +	xproto_xproto \
> >>>>>>
> >>>>>>  You also select dri2proto, is that not needed? But actually, I don't see any
> >>>>>> inclusion of either of these three proto packages, only of xserver stuff (and a
> >>>>>> few that I can't place, like ump.h)
> >>>>> ump.h is part of the x11 egl pkg.
> >>>>> I've added the above deps based on compilation errors I've got.
> >>>>
> >>>>  I suspect that it actually comes from the headers of odroid-mali. If that is
> >>>> the case, it would be better to put the dependency in odroid-mali itself
> >>>> (conditional on using the X11 version, of course).
> >>> I don't understand one thing, the existence of dri2proto does affects odroid-mali, why should I depend odroid-mali dri2proto it when there is no logic to do so?
> >>
> >>  I'm sorry but I couldn't parse your sentence. So I'll just re-explain.
> >>
> >>  I suspect that xproto_fontsproto and xproto_xproto are not included by the
> >> video driver itself, but are included by odroid-mali headers. So I checked and
> >> indeed, the odroid-mali headers include X11/Xlib.h and X11/Xutil.h. So, in
> >> odroid-mali.mk you should add something like
> >>
> >> ifeq ($(BR2_PACKAGE_ODROID_MALI_X11),y)
> >> # The X11 version of the headers include X11/Xlib.h and X11/Xutil.h
> >> ODROID_MALI_DEPENDENCIES += xlib_libX11
> >> endif
> > won't this means that xlib_libX11 will be built? if so, the headers mentioned above won't be deleted by xlib_libX11?
> 
>  Yes, xlib_libX11 will be built, so Xlib.h and Xutil.h get installed to staging,
> which is exactly what we want, no?
indeed, thought of that a few hours after I send this mail.

> 
> > 
> >>
> >> and in Config.in:
> >> 	select BR2_PACKAGE_XLIB_LIBX11 if BR2_PACKAGE_ODROID_MALI_X11
> >>
> > ok, I understand this.
> > 
> >>
> >>  For the video driver, the required packages seem to be:
> >>
> >> xserver_xorg-server (for damage.h, dri2.h, exa.h, micmap.h, ...)
> >> libdrm (for xf86drm.h)
> >>
> >>  But I haven't actually tried building it so I'm not sure.
> > it needs testing, will do after I'll finish understanding all the rejects.
> > 
> > what about the xorg.conf? I'm pretty sure that it won't work without the xorg.conf.
> > what is the right way to address it?
> 
>  Of course it won't work without xorg.conf adaptations. But many drivers need or
> may need xorg.conf adaptations. So what you should do is to add an explanation
> to the help text in Config.in. Look at xdriver_xf86-video-imx-viv as an example.
imho the one in xdriver_xf86-video-imx-viv isn't good for this driver. the xdriver_xf86-video-imx-viv has a generic explanation.
this driver needs specific xorg.conf, imho pasting the entire file to the help is not a good idea.
so I have an alternative suggestion, instead of installing it to /etc/X11/xorg.conf, it will be installed to /usr/share/X11/xorg.conf.odroidc2.
in addition, a entry to the help screen pointing to the location of the file is added.
thus the user can easily copy the file to the right location and there is not possible collision upon build.
this can be done to the trubofb driver.
thoughts?

Dagg.


More information about the buildroot mailing list