search for: winsys

SUBMISSION DEADLINE 14th International Conference on Wireless Networks and Mobile Systems Submission Deadline: April 18, 2017 http://www.winsys.icete.org/ July 24 - 26, 2017 Madrid, Spain. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services In Cooperation with ITG. Technically Co-sponsored by IEEE Systems Council. With the presence...

SUBMISSION DEADLINE 15th International Conference on Wireless Networks and Mobile Systems Submission Deadline: March 13, 2018 http://www.winsys.icete.org/ July 26 - 28, 2018 Porto, Portugal. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services A short list of presented papers will be selected so that revised and extended versions of t...

SUBMISSION DEADLINE 15th International Conference on Wireless Networks and Mobile Systems Submission Deadline: March 13, 2018 http://www.winsys.icete.org/ July 26 - 28, 2018 Porto, Portugal. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services A short list of presented papers will be selected so that revised and extended versions of t...

SUBMISSION DEADLINE 15th International Conference on Wireless Networks and Mobile Systems Submission Deadline: April 3, 2018 http://www.winsys.icete.org/ July 26 - 28, 2018 Porto, Portugal. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services Technically Co-sponsored by IEEE Systems Council. With the presence of internationally distin...

SUBMISSION DEADLINE International Conference on Wireless Networks and Mobile Systems Submission Deadline: February 28, 2019 http://www.winsys.icete.org/ July 26 - 28, 2019 Prague, Czech Republic. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services In Cooperation with: Photonics21 and EOS. Proceedings will be sub...

SUBMISSION DEADLINE 14th International Conference on Wireless Networks and Mobile Systems Submission Deadline: April 18, 2017 http://www.winsys.icete.org/ July 24 - 26, 2017 Madrid, Spain. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services In Cooperation with ITG. Technically Co-sponsored by IEEE Systems Council. With the presence...

SUBMISSION DEADLINE 15th International Conference on Wireless Networks and Mobile Systems Submission Deadline: March 13, 2018 http://www.winsys.icete.org/ July 26 - 28, 2018 Porto, Portugal. WINSYS is organized in 3 major tracks: - Sensor Networks and Ad Hoc Communications - Wireless and Mobile Technologies - Mobile Software and Services A short list of presented papers will be selected so that revised and extended versions of t...

--- .../winsys/drm/nouveau/common/nouveau_context.c | 6 ++++-- .../winsys/drm/nouveau/common/nouveau_winsys.c | 7 ++++++- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/src/gallium/winsys/drm/nouveau/common/nouveau_context.c b/src/gallium/winsys/drm/nouveau/common/nouveau_context.c...

...ll the nouveau_device that it is the owner of the fd so that it will be closed on destruction. Also make sure to free the nouveau_device in case of any failure. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=79823 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c b/src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c index 1dfdaac..833fb9a 100644 --- a/src/gallium/winsys/nouveau/drm/nouveau_drm_...

...is all seems very roundabout... Can't we do this in a somewhat consistent way with the device being cleaned up in one place or another but not both? On Thu, Nov 26, 2015 at 8:04 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > From: Ben Skeggs <bskeggs at redhat.com> > > The winsys layer would attempt to cleanup the nouveau_device if screen > init failed, however, in most paths the pipe driver would have already > destroyed it, resulting in accesses to freed memory etc. > > This commit fixes the problem by allowing the winsys to detect whether > the pipe driver...

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 4016871..c02ee61 100644 --- a/configure.ac +++ b/configure.ac @@ -73,7 +73,7 @@ LIBDRM_RADEON_REQUIRED=2.4.56 LIBDRM_AMDGPU_REQUIRED=2.4.63 LIBDRM_INTEL_REQUIRED=2.4.61

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 4016871..c02ee61 100644 --- a/configure.ac +++ b/configure.ac @@ -73,7 +73,7 @@ LIBDRM_RADEON_REQUIRED=2.4.56 LIBDRM_AMDGPU_REQUIRED=2.4.63 LIBDRM_INTEL_REQUIRED=2.4.61

...ere contains garbage: (gdb) print *fb->cbufs[0] $4 = {buffer = 0xf7d901a0, format = -136773216, status = 1, clear_value = 0, width = 189, height = 181, block = {size = 4, width = 1, height = 1}, nblocksx = 189, nblocksy = 181, stride = 768, layout = 0, offset = 0, refcount = 0, usage = 12, winsys = 0x0, texture = 0x0, face = 0, level = 0, zslice = 88} I tried to track what writes the insane value to the format field, and always came up with malloc and free, which didn't make any sense. Then I ran it with valgrind: ==5322== Invalid read of size 4 ==5322== at 0x7B6887C: pipe_surf...

I made some changes to the Nouveau drm winsys so it could be shared between Mesa and VL. Mostly this involved moving all the common stuff into common/ and adding dri/. Compiles and runs the stuff in progs/ like before as far as I know, but if anyone actually uses the Mesa driver for anything non-trivial I'd appreciate knowing if this brok...

...ng cleaned up in one place or >> another but not both? > That would be lovely, but not possible. It has to be cleaned up by the > pipe screen destroy() function, as that's the normal exit path. If the > pipe driver creation path fails before it's got a struct, then the > winsys will have to clean up after itself instead. Couldn't you make the pipe_screen_create() function destroy the device in all failure paths? > >> >> On Thu, Nov 26, 2015 at 8:04 PM, Ben Skeggs <skeggsb at gmail.com> wrote: >>> From: Ben Skeggs <bskeggs at redhat.c...

From: Ben Skeggs <bskeggs at redhat.com> v2. forgot bump for non-gallium driver Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index b6680d0..965c6f7 100644 --- a/configure.ac +++ b/configure.ac @@ -72,8 +72,8 @@ LIBDRM_REQUIRED=2.4.60

...ra_resource.c | 219 +++++++ src/gallium/drivers/tegra/tegra_resource.h | 98 +++ src/gallium/drivers/tegra/tegra_screen.c | 311 +++++++++ src/gallium/drivers/tegra/tegra_screen.h | 45 ++ src/gallium/targets/dri/Makefile.am | 2 + src/gallium/winsys/tegra/drm/Makefile.am | 11 + src/gallium/winsys/tegra/drm/Makefile.sources | 2 + src/gallium/winsys/tegra/drm/tegra_drm_public.h | 31 + src/gallium/winsys/tegra/drm/tegra_drm_winsys.c | 33 + 17 files changed, 1609 insertions(+), 1 deletion(-) create mode 100644 src/ga...

...way with the device being cleaned up in one place or > another but not both? That would be lovely, but not possible. It has to be cleaned up by the pipe screen destroy() function, as that's the normal exit path. If the pipe driver creation path fails before it's got a struct, then the winsys will have to clean up after itself instead. > > On Thu, Nov 26, 2015 at 8:04 PM, Ben Skeggs <skeggsb at gmail.com> wrote: >> From: Ben Skeggs <bskeggs at redhat.com> >> >> The winsys layer would attempt to cleanup the nouveau_device if screen >> init fail...

From: Ben Skeggs <bskeggs at redhat.com> The winsys layer would attempt to cleanup the nouveau_device if screen init failed, however, in most paths the pipe driver would have already destroyed it, resulting in accesses to freed memory etc. This commit fixes the problem by allowing the winsys to detect whether the pipe driver's destroy function...

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c | 2 -- src/mesa/drivers/dri/nouveau/nouveau_screen.c | 2 -- 2 files changed, 4 deletions(-) diff --git a/src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c b/src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c index ff017e4..c44424f 100644 --- a/src/galliu...