similar to: Winsys changes in mesa/gallium-0.2

Anyone else getting this when building the latest mesa? make[3]: Entering directory `/usr/local/nouveau/mesa2/mesa/src/gallium/targets/dri-nouveau' gcc -c -I. -I../../../../src/mesa/drivers/dri/common -Iserver -I../../../../include -I../../../../include/GL/internal -I../../../../src/mapi -I../../../../src/gallium/include -I../../../../src/gallium/auxiliary

https://bugs.freedesktop.org/show_bug.cgi?id=45454 Bug #: 45454 Summary: Compilation failure: nouveau_dri.so.tmp: undefined reference to `st_gl_api_create' Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity:

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

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

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

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.

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.

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

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

--- .../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 index 25c9845..d9321ea 100644 ---

Hi, I've been playing with nouveau/mesa branch gallium-0.1, trying to get trivial/tri working on nv20 (with nv10 code). When ever I resize the window, it ends up in an assert failure: #0 0xf790744f in _debug_assert_fail (expr=0xf791908f "0", file=0xf7919050 "nv20_state_emit.c", line=139, function=0xf7919034 "nv20_state_emit_framebuffer") at p_debug.c:335

For a long time the gallium pipe drivers for nvidia fixed function cards (nv0x, nv1x and, to some extent, nv2x) have remained unmaintained and godforsaken -- especially nv0x and nv1x had seen almost no progress since their creation. They've recently grown a classic mesa driver which implements many new features: texturing, hardware-accelerated tnl. However the killer feature is "it

nv30 seems to not support dma objects with offset, so simply extend the query_heap to cover the entire notifier, and use a offset in nv30_context_kick_notify. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_buffer.c | 14 +- src/gallium/drivers/nouveau/nouveau_context.h | 5 +

On Tue, Jun 17, 2014 at 2:34 AM, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > nv30 seems to not support dma objects with offset, so simply extend the query_heap to cover the > entire notifier, and use a offset in nv30_context_kick_notify. It would be great if you could detail the list of transformations that were done in the commit description, as well as what the

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- This is my shot at understanding this whole transfer business. The upshot is that after reading through it and understanding it, the transfer logic does appear correct if potentially less-than-perfectly-efficient (e.g. one could keep track of ranges being read/written, etc). src/gallium/drivers/nouveau/nouveau_buffer.c | 71

nouveau screens are reused for the same device node. However in the scenario where we create screen 1, screen 2, and then delete screen 1, the surrounding code might also close the original device node. To protect against this, dup the fd and use the dup'd fd in the nouveau_device. Also tell the nouveau_device that it is the owner of the fd so that it will be closed on destruction. Also make

This 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

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

On Sun, Dec 6, 2015 at 10:48 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 12/07/2015 01:40 PM, Ilia Mirkin wrote: >> This 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? > That would be lovely, but not possible. It has to be cleaned up by the > pipe