All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagannadh.teki@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] libqeglfs.so not found on imx6
Date: Mon, 6 Mar 2017 16:33:46 +0530	[thread overview]
Message-ID: <CAD6G_RQ5FB9gJYvfz8Z0cRLhUSrjjXUaG13YdbbGdJJ-8E=BCw@mail.gmail.com> (raw)
In-Reply-To: <CAAMH-ysZ-QBLyRy3krifSj5p98d=Aw5pEih07x6cHGHW4bFpWQ@mail.gmail.com>

On Mon, Mar 6, 2017 at 3:49 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi Fabio,
>
> On Sat, Mar 4, 2017 at 8:41 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>> Hi Gary,
>>>
>>> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>>
>>>> Not yet, still stuck at the "drmModeGetResources failed" error.
>>>
>>> I can also get this same error with the new kmscube package from:
>>> https://cgit.freedesktop.org/mesa/kmscube/log/
>>>
>>> # kmscube
>>> drmModeGetResources failed: Invalid argument
>>> failed to initialize legacy DRM
>>>
>>> It works if I explicitly pass the /dev/dri device:
>>>
>>> kmscube -D /dev/dri/card1
>>>
>>> I think QT5 is trying to access /dev/dri/card0, but it should be using
>>> /dev/dri/card1 instead.
>>
>> Yes, this is the problem.
>>
>> If I do an ugly hack like this:
>>
>> --- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>> +++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>> @@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
>>      Q_ASSERT(m_gbm_device == Q_NULLPTR);
>>
>>      qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
>> -    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
>> | O_CLOEXEC);
>> +    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
>>      if (m_dri_fd == -1) {
>>          qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
>>          return false;
>> --
>> 2.7.4
>>
>> Then the demo is launched. It still do not run very well, but at least
>> it starts.
>>
>> Does anyone have an idea on what would be a proper fix?
>
> That's strange I didn't have to do that. Worst part is that my demo
> image is using Qt5.6.2 (same as your image) and that I checked no
> special env variable is set.
>
> Maybe you can try your kernel on my image, see if that works.

I just used rootfs, from the link, and kernel 4.9.13 mainline.

Able to see the demo nicely.

Order:
- kmscube
- Boundary devices Tux
- jellyfish
- ideas in motion
- 28 fps (1. Lord of the Rings)

So, I'm investigating config options on buildroot will let you know
for further update.

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

  reply	other threads:[~2017-03-06 11:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 13:15 [Buildroot] libqeglfs.so not found on imx6 Jagan Teki
2017-03-02 13:35 ` Gary Bisson
     [not found]   ` <CAD6G_RQi8Gwk1hjqxtE=RtZoKpz30aJS1GX59JAGeUu02OP=1g@mail.gmail.com>
2017-03-02 17:01     ` [Buildroot] Fwd: " Jagan Teki
2017-03-02 17:04     ` [Buildroot] " Gary Bisson
2017-03-02 17:15       ` Jagan Teki
2017-03-02 17:22         ` Gary Bisson
2017-03-02 17:57           ` Jagan Teki
2017-03-02 17:22         ` Fabio Estevam
2017-03-02 17:56           ` Jagan Teki
2017-03-02 17:59             ` Fabio Estevam
2017-03-02 18:02               ` Jagan Teki
2017-03-02 18:04                 ` Fabio Estevam
2017-03-02 18:06                   ` Jagan Teki
2017-03-02 18:07                     ` Fabio Estevam
2017-03-02 18:28                       ` Jagan Teki
2017-03-02 18:32                         ` Jagan Teki
2017-03-02 18:36                           ` Fabio Estevam
2017-03-02 18:41                             ` Jagan Teki
2017-03-03  6:52                               ` Jagan Teki
2017-03-03 11:19                                 ` Jagan Teki
2017-03-03 11:47                                   ` Fabio Estevam
2017-03-03 16:20                                     ` Jagan Teki
2017-03-03 17:07                                       ` Gary Bisson
2017-03-03 17:37                                         ` Jagan Teki
2017-03-03 17:38                                           ` Gary Bisson
2017-03-03 23:00                                         ` Fabio Estevam
2017-03-04  1:48                                           ` Fabio Estevam
2017-03-04 12:27                                             ` Gary Bisson
2017-03-04 12:33                                               ` Fabio Estevam
2017-03-04 14:47                                                 ` Fabio Estevam
2017-03-04 19:41                                                   ` Fabio Estevam
2017-03-06 10:19                                                     ` Gary Bisson
2017-03-06 11:03                                                       ` Jagan Teki [this message]
2017-03-06 11:44                                                         ` Jagan Teki
2017-03-06 11:46                                                           ` Fabio Estevam
2017-03-06 12:08                                                             ` Jagan Teki
2017-03-06 12:18                                                               ` Fabio Estevam
2017-03-06 21:05                                                           ` Peter Seiderer
2017-03-06 22:41                                                             ` Fabio Estevam

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='CAD6G_RQ5FB9gJYvfz8Z0cRLhUSrjjXUaG13YdbbGdJJ-8E=BCw@mail.gmail.com' \
    --to=jagannadh.teki@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.