Announcement

Collapse
No announcement yet.

Enlightenment's Evas Gains A DRM Display Engine

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by curaga View Post
    Chromebooks? I don't think there's any guarantee a Tizen desktop wouldn't be locked down similar to those, and they are already quite mainstream.
    Qt5 can already be used in ChromeOS with Google Native Client... so maybe Samsung can deploy Tizen/EFL apps with their Chromebooks with Google Native Client.

    Comment


    • #17
      Originally posted by dee. View Post
      Tizen is not just for mobile, Tizen is actually three things...

      Tizen mobile
      Tizen IVI
      Tizen desktop (this is the one that uses GNOME, the others don't)

      Personally I'm really hoping that we see some laptops with Tizen desktop preinstalled soon. Linux would really break through to mainstream then. And Intel/Samsung/their other partners certainly have the resources to make this happen better than Canonical etc. could ever dream of.
      That is true. Tizen can run on a lot of devices & hardware sure. I did not mean to say it was Only mobile or Only Desktop I simply meant that the code I pushed was Only tested on Desktop. Using standard /dev/drm stuff it Should work on any hardware which supports that

      Comment


      • #18
        Originally posted by devilhorns View Post
        Framebuffer (such as /dev/fb) is covered by a different Evas engine. There is an actual fb engine to use for that. My commits were for DRM/KMS. Basically similar (in what they do), but this uses /dev/drm/card[0-9]...

        The existing Evas FB engine Does work and you can run pretty much Any EFL app with it (including Terminology) ... but there are some rough edges there...Performance is decent tho

        Check EFL autofoo for --enable-fb

        I meant enlightenment_start with E_WL_FORCE=fb... but I also tried running a normal efl app under fb to test it out. It displays, but it seems there is no mouse input even when run as root

        Comment


        • #19
          Originally posted by nerdopolis View Post
          I meant enlightenment_start with E_WL_FORCE=fb... but I also tried running a normal efl app under fb to test it out. It displays, but it seems there is no mouse input even when run as root
          Ahhh I see what you meant now. Yea, the E_WL_FORCE=fb ... mileage will vary with that as it's not something that has been tested too much. It loads the E composite fb engine ... which (to be honest) is not entirely setup for wayland rendering. It's more for E on FB.... Input support there Could potentially be shakey...Can't really say for sure tho because I've not played with That too much... YMMV

          Comment


          • #20
            Originally posted by dee. View Post
            Tizen desktop (this is the one that uses GNOME, the others don't)

            Personally I'm really hoping that we see some laptops with Tizen desktop preinstalled soon. Linux would really break through to mainstream then. And Intel/Samsung/their other partners certainly have the resources to make this happen better than Canonical etc. could ever dream of.
            That would be totaly stupid. To use gnome i mean. They already have a really good DE that with some love in some areas can be totally kick ass.

            Comment


            • #21
              @devilhorns


              How long will it take until we get WL only E? Approximately.


              This is supposed to be a feature needed for E19 release AFAIK.

              Comment


              • #22
                Originally posted by PeterKraus View Post
                No, this is for Tizen.
                nope - not for tizen only. for general support of kernel kms/drm display. tizen is one target of course.

                Comment


                • #23
                  Originally posted by nerdopolis View Post
                  hi.

                  I'm curious about the fb support in enlightenment, so I can prepare my build scripts, and launch scripts... Is that something that is working now, or unsupported, or in progress? It hangs when aI tested it....
                  fb support is already there in efl - has been for a long time, but its fbcon - which means no hw accel, all updates are copies by the cpu from a backing render buffer to the destination fb, no vsync etc. - this is why terminology already works in the fb (as does any properly written efl app - as long as it uses one window only). you even get a mouse working in the fb because it's handled inside the toolkit and canvas. the drm support now allows for vsync zero-copy swaps and is the basis for actual acceleration.

                  Comment


                  • #24
                    Originally posted by curaga View Post
                    Chromebooks? I don't think there's any guarantee a Tizen desktop wouldn't be locked down similar to those, and they are already quite mainstream.
                    I meant real laptops... with real operating systems that can run local applications and perform actual productivity tasks. Not cloudtoys designed to convert users into resources for google's datamining operations...

                    Comment


                    • #25
                      Excuse my inexperience, but does that mean I can have accelerated EFL apps running from the console after all this is done? E.g. without the need for X/Wayland at all? When a window manager is not a requirement etc.

                      Comment


                      • #26
                        Originally posted by devilhorns View Post
                        Ahhh I see what you meant now. Yea, the E_WL_FORCE=fb ... mileage will vary with that as it's not something that has been tested too much. It loads the E composite fb engine ... which (to be honest) is not entirely setup for wayland rendering. It's more for E on FB.... Input support there Could potentially be shakey...Can't really say for sure tho because I've not played with That too much... YMMV
                        I think I found out the issue with the mouse input. It doesn't see touchpad devices, but it does see mice. I was trying the touchpad on my laptop.

                        Comment


                        • #27
                          Originally posted by oliver View Post
                          Excuse my inexperience, but does that mean I can have accelerated EFL apps running from the console after all this is done? E.g. without the need for X/Wayland at all? When a window manager is not a requirement etc.
                          correct. this allows an app to run with kms/drm etc. support. the same support we use to make e be a direct-to-kms/drm compositor, so it's all the same core. you can use it to build a wayland compositor of your own if you want or even an alternative display system too. though there is likely not a lot of value in duplicating/fighting with wayland as anything it doesn't have, you can extend.

                          Comment


                          • #28
                            Originally posted by nerdopolis View Post
                            I think I found out the issue with the mouse input. It doesn't see touchpad devices, but it does see mice. I was trying the touchpad on my laptop.
                            ecore_fb suppots ps/2 input devices in the core. there is support for tslib for touch panels but nothing sepcifically for touchpads if they don't have ps/2 emulation. simply no one has written any support at this stage,

                            Comment


                            • #29
                              And now it runs native on WL. Even though its "experimental"

                              http://e19releasemanager.wordpress.c...wers-combined/

                              Article by Michael imminent.

                              Comment

                              Working...
                              X