Re: Upcoming release
Hi, On Fri, 25 Jan 2019 at 16:05, Derek Foreman wrote: > On 1/18/19 4:20 PM, Derek Foreman wrote: > > Does anyone have objections to an early February freeze and a March > > release? Anyone with large series near completion? > > > > Also, I'd like to float the idea of removing the fbdev backend for this > > release (or the next). The bulk of the interesting features target the > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > update when changes are required elsewhere. Any strong opinions either way? > > Ok, I've heard no complaints, and we really are overdue... Yeah, quite. > There's been some reasonable pushback against dropping fbdev > immediately, so let's leave that in for this release. > > As to the release schedule, maybe: > February 1, Alpha > February 15, Beta > March 1, RC1 > March 8 as a first potential final release date. > > Is this too soon to enter freeze? It's not a lot of warning. So, Weston is in good shape - we now have both xdg-shell stable as well as xdg-shell clients on ivi-shell compositors. I've had a scrub through the MR and don't see anything major we would want to land in the release that we can't do after freeze anyway. Given that, and the complete absence of any objections - how about alpha and freeze today? Cheers, Daniel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
RE: Upcoming release
Hi all, Thanks for reviewing, Daniel. I plan to update the MR with all changes after testing tomorrow. I hope that's fine. Cheers, Michael Michael Teyfel Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6932 > -Original Message- > From: wayland-devel On > Behalf Of Daniel Stone > Sent: Donnerstag, 31. Januar 2019 01:56 > To: Ucan, Emre (ADITG/ESB) > Cc: Pekka Paalanen ; Derek Foreman > ; wayland- > de...@lists.freedesktop.org > Subject: Re: Upcoming release > > Hi Emre, > > On Sat, 19 Jan 2019 at 20:39, Ucan, Emre (ADITG/ESB) jv.com> wrote: > > I would like to push XDG shell support for ivi-shell: > > https://gitlab.freedesktop.org/wayland/weston/merge_requests/86 > > > > It would be great if you and other maintainers can ack and/or review this > merge request till beginning of February. If they are no major concerns, it > would be great to have it in this release. > > I've reviewed this now, and there are only some minor changes I can see > need making. If Michael agrees with the suggested changes, I'm fine with > either him making the changes and updating the MR, or if he has no time this > week, I could just do it myself. I'd be really really glad to make > ivi_application > very deprecated. > > Cheers, > Daniel > ___ > wayland-devel mailing list > wayland-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Wed, 30 Jan 2019 08:55:53 -0600 Derek Foreman wrote: > On 1/30/19 6:58 AM, Alexandros Frantzis wrote: > > On Fri, Jan 25, 2019 at 10:05:47AM -0600, Derek Foreman wrote: > >> As to the release schedule, maybe: > >> February 1, Alpha > >> February 15, Beta > >> March 1, RC1 > >> March 8 as a first potential final release date. > >> > > Hi Derek, > > > > it would be nice if we could also try to get the weston support for the > > zwp_linux_explicit_synchronization_unstable_v1 protocol in the next > > release, given that the protocol itself has landed since some time now > > (wayland-protocols 1.17). > > > > The MR for the explicit sync implementation is at: > > > > https://gitlab.freedesktop.org/wayland/weston/merge_requests/32 > > At this point I'm thinking at least a one week push on the proposed > release schedule. Is that enough to get this one in? I suppose that's a question for me. It could be enough, yeah. Thanks, pq pgpm6_geGRn3p.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
Hi Emre, On Sat, 19 Jan 2019 at 20:39, Ucan, Emre (ADITG/ESB) wrote: > I would like to push XDG shell support for ivi-shell: > https://gitlab.freedesktop.org/wayland/weston/merge_requests/86 > > It would be great if you and other maintainers can ack and/or review this > merge request till beginning of February. If they are no major concerns, it > would be great to have it in this release. I've reviewed this now, and there are only some minor changes I can see need making. If Michael agrees with the suggested changes, I'm fine with either him making the changes and updating the MR, or if he has no time this week, I could just do it myself. I'd be really really glad to make ivi_application very deprecated. Cheers, Daniel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On 1/30/19 6:58 AM, Alexandros Frantzis wrote: > On Fri, Jan 25, 2019 at 10:05:47AM -0600, Derek Foreman wrote: >> On 1/18/19 4:20 PM, Derek Foreman wrote: >>> Hi all, >>> >>> It's been quite some time since our last weston release, and there's >>> been some discussion of getting the next one out in the January to March >>> timeframe (this would be the last release to have an autotools build, btw). >>> >>> Does anyone have objections to an early February freeze and a March >>> release? Anyone with large series near completion? >>> >>> Also, I'd like to float the idea of removing the fbdev backend for this >>> release (or the next). The bulk of the interesting features target the >>> drm backend, and it feels like fbdev can sometimes be a bit of a pain to >>> update when changes are required elsewhere. Any strong opinions either way? >> >> Ok, I've heard no complaints, and we really are overdue... >> >> There's been some reasonable pushback against dropping fbdev >> immediately, so let's leave that in for this release. >> >> As to the release schedule, maybe: >> February 1, Alpha >> February 15, Beta >> March 1, RC1 >> March 8 as a first potential final release date. >> >> Is this too soon to enter freeze? It's not a lot of warning. >> >> Wayland has had enough changes that I think another joint release makes >> sense. >> >> Thanks, >> Derek > > Hi Derek, > > it would be nice if we could also try to get the weston support for the > zwp_linux_explicit_synchronization_unstable_v1 protocol in the next > release, given that the protocol itself has landed since some time now > (wayland-protocols 1.17). > > The MR for the explicit sync implementation is at: > > https://gitlab.freedesktop.org/wayland/weston/merge_requests/32 At this point I'm thinking at least a one week push on the proposed release schedule. Is that enough to get this one in? Thanks, Derek > Thanks, > Alexandros > ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On 1/30/19 6:19 AM, Pekka Paalanen wrote: > On Mon, 28 Jan 2019 12:13:12 +0200 > Pekka Paalanen wrote: > >> On Fri, 25 Jan 2019 10:05:47 -0600 >> Derek Foreman wrote: >> >>> On 1/18/19 4:20 PM, Derek Foreman wrote: Hi all, It's been quite some time since our last weston release, and there's been some discussion of getting the next one out in the January to March timeframe (this would be the last release to have an autotools build, btw). Does anyone have objections to an early February freeze and a March release? Anyone with large series near completion? Also, I'd like to float the idea of removing the fbdev backend for this release (or the next). The bulk of the interesting features target the drm backend, and it feels like fbdev can sometimes be a bit of a pain to update when changes are required elsewhere. Any strong opinions either way? >>> >>> Ok, I've heard no complaints, and we really are overdue... >>> >>> There's been some reasonable pushback against dropping fbdev >>> immediately, so let's leave that in for this release. >>> >>> As to the release schedule, maybe: >>> February 1, Alpha >>> February 15, Beta >>> March 1, RC1 >>> March 8 as a first potential final release date. >>> >>> Is this too soon to enter freeze? It's not a lot of warning. >>> >>> Wayland has had enough changes that I think another joint release makes >>> sense. >> >> Hi, >> >> here are my picks from the pending reviews. I don't mean that we should >> wait on them unless noted explicitly below. Thanks for putting this list together. >> Wayland: >> >> I reviewed https://patchwork.freedesktop.org/series/49379/ and it needs >> work. >> >> https://patchwork.freedesktop.org/series/38564/ is probably something I >> should look into to have in the alpha. > > That one landed. > >> >> Weston: >> >> https://gitlab.freedesktop.org/wayland/weston/merge_requests/66 is >> something I'd like to land, but it needs a small touch. >> >> https://gitlab.freedesktop.org/wayland/weston/merge_requests/62 is >> probably important enough, that I'd be willing to postpone the release >> until we get that in. Looks like it is very close. Jonas mentioned this one on IRC too. Looks like it's close enough to delay the release for, and I think everyone would really like to see it landed. >> Since Meson is a new thing, >> https://gitlab.freedesktop.org/wayland/weston/merge_requests/85 would >> probably be nice to decide on. >> >> Getting NEWS files would be cool too. This was just the first attempt >> that got useful feedback but I never had the time to take it further: >> https://patchwork.freedesktop.org/series/16218/ >> > > I took a look at the Weston changes since 5.0.0 release: > > - the exported symbols from weston executable have changed, backwards > incompatible, but this probably shouldn't count against libweston > major > > - struct weston_head gained a new member > > - struct weston_compositor gained new members > > - struct weston_surface gained a new member > > I guess these are reasons enough to bump the major to 6, right? > > Would have been interesting to release a 5.1.0, too bad. :-) Thanks for looking into this, as I wasn't sure yet what the new release would be called. :) Sounds like a 6 to me. We'll definitely be in a holding pattern until the xdg-shell (MR 62) stuff lands. Thanks, Derek > > Thanks, > pq > ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Fri, Jan 25, 2019 at 10:05:47AM -0600, Derek Foreman wrote: > On 1/18/19 4:20 PM, Derek Foreman wrote: > > Hi all, > > > > It's been quite some time since our last weston release, and there's > > been some discussion of getting the next one out in the January to March > > timeframe (this would be the last release to have an autotools build, btw). > > > > Does anyone have objections to an early February freeze and a March > > release? Anyone with large series near completion? > > > > Also, I'd like to float the idea of removing the fbdev backend for this > > release (or the next). The bulk of the interesting features target the > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > update when changes are required elsewhere. Any strong opinions either way? > > Ok, I've heard no complaints, and we really are overdue... > > There's been some reasonable pushback against dropping fbdev > immediately, so let's leave that in for this release. > > As to the release schedule, maybe: > February 1, Alpha > February 15, Beta > March 1, RC1 > March 8 as a first potential final release date. > > Is this too soon to enter freeze? It's not a lot of warning. > > Wayland has had enough changes that I think another joint release makes > sense. > > Thanks, > Derek Hi Derek, it would be nice if we could also try to get the weston support for the zwp_linux_explicit_synchronization_unstable_v1 protocol in the next release, given that the protocol itself has landed since some time now (wayland-protocols 1.17). The MR for the explicit sync implementation is at: https://gitlab.freedesktop.org/wayland/weston/merge_requests/32 Thanks, Alexandros ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Mon, 28 Jan 2019 12:13:12 +0200 Pekka Paalanen wrote: > On Fri, 25 Jan 2019 10:05:47 -0600 > Derek Foreman wrote: > > > On 1/18/19 4:20 PM, Derek Foreman wrote: > > > Hi all, > > > > > > It's been quite some time since our last weston release, and there's > > > been some discussion of getting the next one out in the January to March > > > timeframe (this would be the last release to have an autotools build, > > > btw). > > > > > > Does anyone have objections to an early February freeze and a March > > > release? Anyone with large series near completion? > > > > > > Also, I'd like to float the idea of removing the fbdev backend for this > > > release (or the next). The bulk of the interesting features target the > > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > > update when changes are required elsewhere. Any strong opinions either > > > way? > > > > Ok, I've heard no complaints, and we really are overdue... > > > > There's been some reasonable pushback against dropping fbdev > > immediately, so let's leave that in for this release. > > > > As to the release schedule, maybe: > > February 1, Alpha > > February 15, Beta > > March 1, RC1 > > March 8 as a first potential final release date. > > > > Is this too soon to enter freeze? It's not a lot of warning. > > > > Wayland has had enough changes that I think another joint release makes > > sense. > > Hi, > > here are my picks from the pending reviews. I don't mean that we should > wait on them unless noted explicitly below. > > Wayland: > > I reviewed https://patchwork.freedesktop.org/series/49379/ and it needs > work. > > https://patchwork.freedesktop.org/series/38564/ is probably something I > should look into to have in the alpha. That one landed. > > Weston: > > https://gitlab.freedesktop.org/wayland/weston/merge_requests/66 is > something I'd like to land, but it needs a small touch. > > https://gitlab.freedesktop.org/wayland/weston/merge_requests/62 is > probably important enough, that I'd be willing to postpone the release > until we get that in. Looks like it is very close. > > Since Meson is a new thing, > https://gitlab.freedesktop.org/wayland/weston/merge_requests/85 would > probably be nice to decide on. > > Getting NEWS files would be cool too. This was just the first attempt > that got useful feedback but I never had the time to take it further: > https://patchwork.freedesktop.org/series/16218/ > I took a look at the Weston changes since 5.0.0 release: - the exported symbols from weston executable have changed, backwards incompatible, but this probably shouldn't count against libweston major - struct weston_head gained a new member - struct weston_compositor gained new members - struct weston_surface gained a new member I guess these are reasons enough to bump the major to 6, right? Would have been interesting to release a 5.1.0, too bad. :-) Thanks, pq pgphnvDTqiWDv.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Fri, 25 Jan 2019 10:05:47 -0600 Derek Foreman wrote: > On 1/18/19 4:20 PM, Derek Foreman wrote: > > Hi all, > > > > It's been quite some time since our last weston release, and there's > > been some discussion of getting the next one out in the January to March > > timeframe (this would be the last release to have an autotools build, btw). > > > > Does anyone have objections to an early February freeze and a March > > release? Anyone with large series near completion? > > > > Also, I'd like to float the idea of removing the fbdev backend for this > > release (or the next). The bulk of the interesting features target the > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > update when changes are required elsewhere. Any strong opinions either > > way? > > Ok, I've heard no complaints, and we really are overdue... > > There's been some reasonable pushback against dropping fbdev > immediately, so let's leave that in for this release. > > As to the release schedule, maybe: > February 1, Alpha > February 15, Beta > March 1, RC1 > March 8 as a first potential final release date. > > Is this too soon to enter freeze? It's not a lot of warning. > > Wayland has had enough changes that I think another joint release makes > sense. Hi, here are my picks from the pending reviews. I don't mean that we should wait on them unless noted explicitly below. Wayland: I reviewed https://patchwork.freedesktop.org/series/49379/ and it needs work. https://patchwork.freedesktop.org/series/38564/ is probably something I should look into to have in the alpha. Weston: https://gitlab.freedesktop.org/wayland/weston/merge_requests/66 is something I'd like to land, but it needs a small touch. https://gitlab.freedesktop.org/wayland/weston/merge_requests/62 is probably important enough, that I'd be willing to postpone the release until we get that in. Looks like it is very close. Since Meson is a new thing, https://gitlab.freedesktop.org/wayland/weston/merge_requests/85 would probably be nice to decide on. Getting NEWS files would be cool too. This was just the first attempt that got useful feedback but I never had the time to take it further: https://patchwork.freedesktop.org/series/16218/ Thanks, pq pgpO2BwZIvaXZ.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On 1/18/19 4:20 PM, Derek Foreman wrote: > Hi all, > > It's been quite some time since our last weston release, and there's > been some discussion of getting the next one out in the January to March > timeframe (this would be the last release to have an autotools build, btw). > > Does anyone have objections to an early February freeze and a March > release? Anyone with large series near completion? > > Also, I'd like to float the idea of removing the fbdev backend for this > release (or the next). The bulk of the interesting features target the > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > update when changes are required elsewhere. Any strong opinions either way? Ok, I've heard no complaints, and we really are overdue... There's been some reasonable pushback against dropping fbdev immediately, so let's leave that in for this release. As to the release schedule, maybe: February 1, Alpha February 15, Beta March 1, RC1 March 8 as a first potential final release date. Is this too soon to enter freeze? It's not a lot of warning. Wayland has had enough changes that I think another joint release makes sense. Thanks, Derek ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Fbdev-backend removal from Weston (Re: Upcoming release)
On Wednesday, January 23, 2019 4:09:44 AM EST Pekka Paalanen wrote: > On Tue, 22 Jan 2019 22:46:02 -0500 > nerdopolis wrote: > > > On Tuesday, January 22, 2019 9:55:15 AM EST Pekka Paalanen wrote: > > > > > > > On Tue, 22 Jan 2019 10:17:32 +0200 > > > Pekka Paalanen wrote: > > > > > > > Hi, > > > > > > > > do you actually have a use case for that? It's ok if you do, we can > > > > keep it around for some more, but the simple fact that some hardware > > > > exists that does not have a working DRM driver is not enough. There > > > > should be users too. > > > > > > > > The fbdev-backend certainly has its shortcomings, and I don't mean just > > > > the lack of multi-output or monitor hotplug or GPU acceleration or > > > > tearing or timings based on nothing but timers; I recall VT-switching > > > > being broken for years now, and it doesn't (cannot?) use logind to open > > > > the FB devices. Did I forget some? > > > > > Hi > > > > Well, TBH, It's just my quazi-distribution Live CD that I still maintain... > > It falls back to the Framebuffer on systems (or seats) that don't have > > Kernel Mode Setting. The number of users now probably is low... > > Right. Would you be able to do a test? Disable fbdev on your distro and > see if anyone complains? > TBH, the user base is likely not as high as it was in 2012. It's prime focus was to allow users to test anything Wayland live. So I don't think that would be a good way to tell, since now there are other more popular ways people have been using it now. > In fact, would be nice if all distributions did that test. I'm not in > that much hurry to delete the backend yet. > > > VT switching works great. It works without weston-launch, and I can switch > > away > > to a second instance of Weston using the Framebuffer, without them stepping > > on > > each other, and I can switch back to the original one, and it continues > > working > > > > I do have to create a udev file that sets > > SUBSYSTEM=="graphics", KERNEL=="fb*", TAG+="uaccess" > > though... > > Yes, that rule or similar is required because logind does not deal fb > devices IIRC and Weston certainly doesn't ask. > > Are you relying on logind or running Weston privileged to have VT > switching working? > I am making no changes to logind. I am not running Weston as root. I am not even granting the plugdev group access to the /dev/fbX devices (It's a "hidden" boot option, disabled by default). Just systemd-run that starts it as a User account. > It's been a long time since I tried VT-switching with fbdev, but it > didn't work with logind back then: > https://gitlab.freedesktop.org/wayland/weston/issues/78 > Could it have been fixed in logind instead? > Yeah, I wasnt even aware of that one. It was probably logind. Weston is working fine. I can switch between the framebuffer backed login greeter, and a frame buffer backed login session, and they don't draw on each other. Weston even logs when the session becomes active and inactive, so it is aware. It even works on seats that do NOT have TTYs, since my login manager is multiseat aware now, I can test that :) > > Thanks, > pq ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Fbdev-backend removal from Weston (Re: Upcoming release)
On Tue, 22 Jan 2019 10:17:32 +0200 Pekka Paalanen wrote: keep it around for some more, but the simple fact that some hardware exists that does not have a working DRM driver is not enough Fbdev worked out of the box on my Bay Trail system, but DRM kept freezing where only SysRq helped. It seems an issue in Mesa, downgrade to 18.1.9 and exporting WESTON_DISABLE_ATOMIC=y works, but I haven't been able to track and report, because nothing weird got in the logs. By all means delete this backend if it's tech debt, though some users are there yet. Looking forward to new releases so I can unmask >=media-video/mpv-0.29, which wants xdg_wm_base. ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Fbdev-backend removal from Weston (Re: Upcoming release)
On Tue, 2019-01-22 at 22:46 -0500, nerdopolis wrote: > Well, TBH, It's just my quazi-distribution Live CD that I still maintain... > It falls back to the Framebuffer on systems (or seats) that don't have > Kernel Mode Setting. The number of users now probably is low... I think the biggest class of fbdev users on reasonably modern hardware are people who've said nomodeset to avoid a drm driver bug and so fall down to efifb. I wonder if it's worth making a trivial efikms driver for that case. - ajax ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Fbdev-backend removal from Weston (Re: Upcoming release)
On Tue, 22 Jan 2019 22:46:02 -0500 nerdopolis wrote: > On Tuesday, January 22, 2019 9:55:15 AM EST Pekka Paalanen wrote: > > > > On Tue, 22 Jan 2019 10:17:32 +0200 > > Pekka Paalanen wrote: > > > > > Hi, > > > > > > do you actually have a use case for that? It's ok if you do, we can > > > keep it around for some more, but the simple fact that some hardware > > > exists that does not have a working DRM driver is not enough. There > > > should be users too. > > > > > > The fbdev-backend certainly has its shortcomings, and I don't mean just > > > the lack of multi-output or monitor hotplug or GPU acceleration or > > > tearing or timings based on nothing but timers; I recall VT-switching > > > being broken for years now, and it doesn't (cannot?) use logind to open > > > the FB devices. Did I forget some? > > Hi > > Well, TBH, It's just my quazi-distribution Live CD that I still maintain... > It falls back to the Framebuffer on systems (or seats) that don't have > Kernel Mode Setting. The number of users now probably is low... Right. Would you be able to do a test? Disable fbdev on your distro and see if anyone complains? In fact, would be nice if all distributions did that test. I'm not in that much hurry to delete the backend yet. > VT switching works great. It works without weston-launch, and I can switch > away > to a second instance of Weston using the Framebuffer, without them stepping on > each other, and I can switch back to the original one, and it continues > working > > I do have to create a udev file that sets > SUBSYSTEM=="graphics", KERNEL=="fb*", TAG+="uaccess" > though... Yes, that rule or similar is required because logind does not deal fb devices IIRC and Weston certainly doesn't ask. Are you relying on logind or running Weston privileged to have VT switching working? It's been a long time since I tried VT-switching with fbdev, but it didn't work with logind back then: https://gitlab.freedesktop.org/wayland/weston/issues/78 Could it have been fixed in logind instead? Thanks, pq pgpofY2eJYo8X.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Fbdev-backend removal from Weston (Re: Upcoming release)
On Tuesday, January 22, 2019 9:55:15 AM EST Pekka Paalanen wrote: > Let's make the title more catchy, so that people who care about fbdev > would notice. > > > On Tue, 22 Jan 2019 10:17:32 +0200 > Pekka Paalanen wrote: > > > On Mon, 21 Jan 2019 20:30:52 -0500 > > nerdopolis wrote: > > > > > On Friday, January 18, 2019 5:20:40 PM EST Derek Foreman wrote: > > > > Also, I'd like to float the idea of removing the fbdev backend for this > > > > release (or the next). The bulk of the interesting features target the > > > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > > > update when changes are required elsewhere. Any strong opinions either > > > > way? > > > > > I feel like the fbdev backend is a good fallback still. Maybe not for > > > Virtual > > > Box anymore, since there is now a driver for it in Mainline (I haven't > > > tested > > > it personally though) ...Currently the Framebuffer backend is the only > > > way to > > > get Weston working on some obscure hardware such as UDL/DisplayLink2 > > > devices. > > > > Hi, > > > > do you actually have a use case for that? It's ok if you do, we can > > keep it around for some more, but the simple fact that some hardware > > exists that does not have a working DRM driver is not enough. There > > should be users too. > > > > The fbdev-backend certainly has its shortcomings, and I don't mean just > > the lack of multi-output or monitor hotplug or GPU acceleration or > > tearing or timings based on nothing but timers; I recall VT-switching > > being broken for years now, and it doesn't (cannot?) use logind to open > > the FB devices. Did I forget some? > > > > > > Thanks, > > pq > Hi Well, TBH, It's just my quazi-distribution Live CD that I still maintain... It falls back to the Framebuffer on systems (or seats) that don't have Kernel Mode Setting. The number of users now probably is low... VT switching works great. It works without weston-launch, and I can switch away to a second instance of Weston using the Framebuffer, without them stepping on each other, and I can switch back to the original one, and it continues working I do have to create a udev file that sets SUBSYSTEM=="graphics", KERNEL=="fb*", TAG+="uaccess" though... Thanks ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Fbdev-backend removal from Weston (Re: Upcoming release)
Let's make the title more catchy, so that people who care about fbdev would notice. On Tue, 22 Jan 2019 10:17:32 +0200 Pekka Paalanen wrote: > On Mon, 21 Jan 2019 20:30:52 -0500 > nerdopolis wrote: > > > On Friday, January 18, 2019 5:20:40 PM EST Derek Foreman wrote: > > > Also, I'd like to float the idea of removing the fbdev backend for this > > > release (or the next). The bulk of the interesting features target the > > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > > update when changes are required elsewhere. Any strong opinions either > > > way? > > > I feel like the fbdev backend is a good fallback still. Maybe not for > > Virtual > > Box anymore, since there is now a driver for it in Mainline (I haven't > > tested > > it personally though) ...Currently the Framebuffer backend is the only way > > to > > get Weston working on some obscure hardware such as UDL/DisplayLink2 > > devices. > > Hi, > > do you actually have a use case for that? It's ok if you do, we can > keep it around for some more, but the simple fact that some hardware > exists that does not have a working DRM driver is not enough. There > should be users too. > > The fbdev-backend certainly has its shortcomings, and I don't mean just > the lack of multi-output or monitor hotplug or GPU acceleration or > tearing or timings based on nothing but timers; I recall VT-switching > being broken for years now, and it doesn't (cannot?) use logind to open > the FB devices. Did I forget some? > > > Thanks, > pq pgp6Onkuf6qm9.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Mon, 21 Jan 2019 20:30:52 -0500 nerdopolis wrote: > On Friday, January 18, 2019 5:20:40 PM EST Derek Foreman wrote: > > Also, I'd like to float the idea of removing the fbdev backend for this > > release (or the next). The bulk of the interesting features target the > > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > > update when changes are required elsewhere. Any strong opinions either way? > I feel like the fbdev backend is a good fallback still. Maybe not for Virtual > Box anymore, since there is now a driver for it in Mainline (I haven't tested > it personally though) ...Currently the Framebuffer backend is the only way to > get Weston working on some obscure hardware such as UDL/DisplayLink2 devices. Hi, do you actually have a use case for that? It's ok if you do, we can keep it around for some more, but the simple fact that some hardware exists that does not have a working DRM driver is not enough. There should be users too. The fbdev-backend certainly has its shortcomings, and I don't mean just the lack of multi-output or monitor hotplug or GPU acceleration or tearing or timings based on nothing but timers; I recall VT-switching being broken for years now, and it doesn't (cannot?) use logind to open the FB devices. Did I forget some? Thanks, pq pgpuKn4ox0aP7.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Friday, January 18, 2019 5:20:40 PM EST Derek Foreman wrote: > Hi all, > > It's been quite some time since our last weston release, and there's > been some discussion of getting the next one out in the January to March > timeframe (this would be the last release to have an autotools build, btw). > > Does anyone have objections to an early February freeze and a March > release? Anyone with large series near completion? > > Also, I'd like to float the idea of removing the fbdev backend for this > release (or the next). The bulk of the interesting features target the > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > update when changes are required elsewhere. Any strong opinions either way? > > Thanks, > Derek > ___ > wayland-devel mailing list > wayland-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/wayland-devel > I feel like the fbdev backend is a good fallback still. Maybe not for Virtual Box anymore, since there is now a driver for it in Mainline (I haven't tested it personally though) ...Currently the Framebuffer backend is the only way to get Weston working on some obscure hardware such as UDL/DisplayLink2 devices. ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
RE: Upcoming release
Hi Derek, I would like to push XDG shell support for ivi-shell: https://gitlab.freedesktop.org/wayland/weston/merge_requests/86 It would be great if you and other maintainers can ack and/or review this merge request till beginning of February. If they are no major concerns, it would be great to have it in this release. Automotive Grade Linux project is already using this feature. Here is the list of patches they are applying on top of weston 2.0: https://git.automotivelinux.org/AGL/meta-agl/tree/meta-agl-profile-graphical/recipes-graphics/wayland/weston_2.0.0.bbappend Best regards Emre Ucan Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6937 -Original Message- From: wayland-devel On Behalf Of Derek Foreman Sent: Freitag, 18. Januar 2019 23:21 To: wayland-devel@lists.freedesktop.org Subject: Upcoming release Hi all, It's been quite some time since our last weston release, and there's been some discussion of getting the next one out in the January to March timeframe (this would be the last release to have an autotools build, btw). Does anyone have objections to an early February freeze and a March release? Anyone with large series near completion? Also, I'd like to float the idea of removing the fbdev backend for this release (or the next). The bulk of the interesting features target the drm backend, and it feels like fbdev can sometimes be a bit of a pain to update when changes are required elsewhere. Any strong opinions either way? Thanks, Derek ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release
On Fri, 18 Jan 2019 16:20:40 -0600 Derek Foreman wrote: > Hi all, > > It's been quite some time since our last weston release, and there's > been some discussion of getting the next one out in the January to March > timeframe (this would be the last release to have an autotools build, btw). > > Does anyone have objections to an early February freeze and a March > release? Anyone with large series near completion? Hi, sounds good to me. I will propose removing the autotools build right after the release has been completed and the next development cycle begins. > Also, I'd like to float the idea of removing the fbdev backend for this > release (or the next). The bulk of the interesting features target the > drm backend, and it feels like fbdev can sometimes be a bit of a pain to > update when changes are required elsewhere. Any strong opinions either way? I would be happy to see the fbdev backend go. It's dead tech, and anything new relying on it is a false start. However, to be fair, it hasn't been that much of a burden yet, to me anyway. There have even been an occasional patch or two proposed from the community. Thanks, pq pgpqwH9Q334ny.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Upcoming release
Hi all, It's been quite some time since our last weston release, and there's been some discussion of getting the next one out in the January to March timeframe (this would be the last release to have an autotools build, btw). Does anyone have objections to an early February freeze and a March release? Anyone with large series near completion? Also, I'd like to float the idea of removing the fbdev backend for this release (or the next). The bulk of the interesting features target the drm backend, and it feels like fbdev can sometimes be a bit of a pain to update when changes are required elsewhere. Any strong opinions either way? Thanks, Derek ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Upcoming release reminder
On 2018-07-03 04:33 PM, Derek Foreman wrote: > Hi all, > > Just a quick reminder that we're due for alpha shortly, with the > following intended release schedule: I'd like to push this back to Friday, it looks like some atomic patches are just about ready to land, and it seems a shame to block that with a release schedule that was fairly arbitrarily advanced in the first place. Let's just add 3 to every number in the original release plan, and do it all on Fridays this time around. Thanks, Derek > Alpha - July 10th > Beta - July 24th > RC1 - August 7th > First possible release August 14th. > > Thanks, > Derek ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Upcoming release reminder
Hi all, Just a quick reminder that we're due for alpha shortly, with the following intended release schedule: Alpha - July 10th Beta - July 24th RC1 - August 7th First possible release August 14th. Thanks, Derek ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
