search for: sempahor

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list! While converting my config to modules, I''m applying puppet''s mechanisms to interact with and between modules. Here I''ll try to collect a few patterns to create awareness of fundamental module patterns. After feedback/discussion I will add this to the wiki. The Puppet Semaphor ===================

...rf, &color, 0, 0, 1024, 1); > + > + PUSH_SPACE(screen->pushbuf, 5); > + fence_ref[0].bo = dec->fence; > + nouveau_pushbuf_refn(screen->pushbuf, fence_ref, 1); > + /* The clear_render_target is done via 3D engine, so use it to write to a > + * sempahore to indicate that it's done. > + */ > + BEGIN_NV04(screen->pushbuf, SUBC_3D(0x1b00), 4); > + PUSH_DATAh(screen->pushbuf, dec->fence->offset); > + PUSH_DATA (screen->pushbuf, dec->fence->offset); > + PUSH_DATA (screen->pushbuf, 1);...

...24, 1); >> + >> + PUSH_SPACE(screen->pushbuf, 5); >> + fence_ref[0].bo = dec->fence; >> + nouveau_pushbuf_refn(screen->pushbuf, fence_ref, 1); >> + /* The clear_render_target is done via 3D engine, so use it to write to a >> + * sempahore to indicate that it's done. >> + */ >> + BEGIN_NV04(screen->pushbuf, SUBC_3D(0x1b00), 4); >> + PUSH_DATAh(screen->pushbuf, dec->fence->offset); >> + PUSH_DATA (screen->pushbuf, dec->fence->offset); >> + PUSH_DATA (scr...

...gt;>> + PUSH_SPACE(screen->pushbuf, 5); >>> + fence_ref[0].bo = dec->fence; >>> + nouveau_pushbuf_refn(screen->pushbuf, fence_ref, 1); >>> + /* The clear_render_target is done via 3D engine, so use it to write to a >>> + * sempahore to indicate that it's done. >>> + */ >>> + BEGIN_NV04(screen->pushbuf, SUBC_3D(0x1b00), 4); >>> + PUSH_DATAh(screen->pushbuf, dec->fence->offset); >>> + PUSH_DATA (screen->pushbuf, dec->fence->offset); >>> +...

...(struct pipe_surface *)&surf, &color, 0, 0, 1024, 1); + + PUSH_SPACE(screen->pushbuf, 5); + fence_ref[0].bo = dec->fence; + nouveau_pushbuf_refn(screen->pushbuf, fence_ref, 1); + /* The clear_render_target is done via 3D engine, so use it to write to a + * sempahore to indicate that it's done. + */ + BEGIN_NV04(screen->pushbuf, SUBC_3D(0x1b00), 4); + PUSH_DATAh(screen->pushbuf, dec->fence->offset); + PUSH_DATA (screen->pushbuf, dec->fence->offset); + PUSH_DATA (screen->pushbuf, 1); + PUSH_DATA (screen...

...>clear_render_target(context, &surf.base, &color, 0, 0, 1024, 1); + + PUSH_SPACE(screen->pushbuf, 5); + PUSH_REFN(screen->pushbuf, dec->fence, NOUVEAU_BO_VRAM | NOUVEAU_BO_RDWR); + /* The clear_render_target is done via 3D engine, so use it to write to a + * sempahore to indicate that it's done. + */ + BEGIN_NV04(screen->pushbuf, NV50_3D(QUERY_ADDRESS_HIGH), 4); + PUSH_DATAh(screen->pushbuf, dec->fence->offset); + PUSH_DATA (screen->pushbuf, dec->fence->offset); + PUSH_DATA (screen->pushbuf, 1); + PUSH_...

...N(screen->pushbuf, dec->fence, NOUVEAU_BO_VRAM | NOUVEAU_BO_RDWR); + PUSH_SPACE(nv50->base.pushbuf, 5); + PUSH_REFN(nv50->base.pushbuf, dec->fence, NOUVEAU_BO_VRAM | NOUVEAU_BO_RDWR); /* The clear_render_target is done via 3D engine, so use it to write to a * sempahore to indicate that it's done. */ - BEGIN_NV04(screen->pushbuf, NV50_3D(QUERY_ADDRESS_HIGH), 4); - PUSH_DATAh(screen->pushbuf, dec->fence->offset); - PUSH_DATA (screen->pushbuf, dec->fence->offset); - PUSH_DATA (screen->pushbuf, 1); - PUSH_...

Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_fence.c | 76 ++++++++++++------------- src/gallium/drivers/nouveau/nouveau_fence.h | 22 +++++-- src/gallium/drivers/nouveau/nouveau_screen.c | 9 +++ src/gallium/drivers/nouveau/nouveau_screen.h | 14 ++--- src/gallium/drivers/nouveau/nv30/nv30_context.c | 4 +-

..., dec->fence, NOUVEAU_BO_VRAM | NOUVEAU_BO_RDWR); > + PUSH_SPACE(nv50->base.pushbuf, 5); > + PUSH_REFN(nv50->base.pushbuf, dec->fence, NOUVEAU_BO_VRAM | NOUVEAU_BO_RDWR); > /* The clear_render_target is done via 3D engine, so use it to write to a > * sempahore to indicate that it's done. > */ > - BEGIN_NV04(screen->pushbuf, NV50_3D(QUERY_ADDRESS_HIGH), 4); > - PUSH_DATAh(screen->pushbuf, dec->fence->offset); > - PUSH_DATA (screen->pushbuf, dec->fence->offset); > - PUSH_DATA (screen->...

Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_fence.c | 76 ++++++++++++------------- src/gallium/drivers/nouveau/nouveau_fence.h | 22 +++++-- src/gallium/drivers/nouveau/nouveau_screen.c | 9 +++ src/gallium/drivers/nouveau/nouveau_screen.h | 14 ++--- src/gallium/drivers/nouveau/nv30/nv30_context.c | 4

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is

This series of patches provides an ability to add VLANs to the bridge ports. This is similar to what can be found in most switches. The bridge port may have any number of VLANs added to it including vlan 0 priority tagged traffic. When vlans are added to the port, only traffic tagged with particular vlan will forwarded over this port. Additionally, vlan ids are added to FDB entries and become