All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Derycke <johanderycke@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] imx-drm not getting installed
Date: Thu, 10 Oct 2019 15:05:18 +0200	[thread overview]
Message-ID: <CAKHhJn3iFOTsB8HW2Mi6vVCYH94+o_2YHqoBJN5JpAaoe1QVog@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5Bu4cxZ6n5ceTwP5DqXwaH-23xVOxQAGaEwDWufB9dB9A@mail.gmail.com>

Hi,

While testing this (it works :-)) I discovered that those .so files are all
identical files.
Shouldn't this be all symlinks? My rootfs image actually got to big to fit
my embedded device ...

Best regards,




Op di 8 okt. 2019 om 21:54 schreef Fabio Estevam <festevam@gmail.com>:

> Hi Peter,
>
> On Tue, Oct 8, 2019 at 4:39 PM Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Enabling 'BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO=y' enables the
> > missing drivers...
>
> Excellent, thanks!
>
> Should BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO=y be automatically
> selected when a gallium driver is selected?
>
> Otherwise we will need to patch the existing defconfig files to avoid
> a regression.
>
> Thanks
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191010/924074eb/attachment.html>

  reply	other threads:[~2019-10-10 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 13:31 [Buildroot] imx-drm not getting installed Fabio Estevam
2019-10-08 19:39 ` Peter Seiderer
2019-10-08 19:53   ` Fabio Estevam
2019-10-10 13:05     ` Johan Derycke [this message]
2019-10-10 17:01       ` Peter Seiderer
2019-10-10 18:53         ` Peter Seiderer
2019-10-11  8:22           ` Johan Derycke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKHhJn3iFOTsB8HW2Mi6vVCYH94+o_2YHqoBJN5JpAaoe1QVog@mail.gmail.com \
    --to=johanderycke@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.