search for: demag

...ws up in the usermanager of XP and win2k. In XP 'Domain Users' is replaced by Unix.group.nnnnnnnn, in win2k it is completely missing. On the console 'Domain Users' becomes some cryptic chars: X:\>net group /DOMAIN The request will be processed at a domain controller for domain DEMAG Group Accounts for \\PDC --------------------------------------------------------------------- *?? *Domain Admins The command completed successfully. An equal search from a linux box brings the expected result: $>rpcclient //pdc -U martink -c "enumdomgroups" Domain=[DOMAIN] OS=[Unix...

...= nv84_video_buffer_sampler_view_planes; > + buffer->base.get_sampler_view_components = nv84_video_buffer_sampler_view_components; > + buffer->base.get_surfaces = nv84_video_buffer_surfaces; > + buffer->base.interlaced = true; By storing the number of planes, will be able to demagic some constants later on buffer->num_planes = 2; > + > + memset(&templ, 0, sizeof(templ)); > + templ.target = PIPE_TEXTURE_2D_ARRAY; > + templ.depth0 = 1; > + templ.bind = PIPE_BIND_SAMPLER_VIEW | PIPE_BIND_RENDER_TARGET; > + templ.format = PIPE_FORMAT_R8_UNO...

...er_sampler_view_planes; >> + buffer->base.get_sampler_view_components = nv84_video_buffer_sampler_view_components; >> + buffer->base.get_surfaces = nv84_video_buffer_surfaces; >> + buffer->base.interlaced = true; > By storing the number of planes, will be able to demagic some constants > later on > buffer->num_planes = 2; nvc0_video does that. I find that incredibly confusing. It's always 2, and they are of diff size. I prefer my bike-shed color :) > >> + >> + memset(&templ, 0, sizeof(templ)); >> + templ.target = PIP...

...planes; >>> + buffer->base.get_sampler_view_components = nv84_video_buffer_sampler_view_components; >>> + buffer->base.get_surfaces = nv84_video_buffer_surfaces; >>> + buffer->base.interlaced = true; >> By storing the number of planes, will be able to demagic some constants >> later on >> buffer->num_planes = 2; > > nvc0_video does that. I find that incredibly confusing. It's always 2, > and they are of diff size. I prefer my bike-shed color :) > >> >>> + >>> + memset(&templ, 0, sizeof(...

[ REPOST: Apologies to anyone who has seen this before. It didn't make it onto any of the lists it should have. -J ] Hi Andrew, This series of patches lays the basic ground work for the paravirtualized kernel patches coming later on. I think this lot is ready for the rough-and-tumble world of the -mm tree. For the most part, these patches do nothing or very little. The patches should

[ REPOST: Apologies to anyone who has seen this before. It didn't make it onto any of the lists it should have. -J ] Hi Andrew, This series of patches lays the basic ground work for the paravirtualized kernel patches coming later on. I think this lot is ready for the rough-and-tumble world of the -mm tree. For the most part, these patches do nothing or very little. The patches should

...} + + ctx->ctxvals_pos = offset + size * 8; + ctx->ctxvals_pos = (ctx->ctxvals_pos+0x3f)&~0x3f; + cp_lsr (ctx, offset); + cp_out (ctx, CP_SET_XFER_POINTER); + cp_lsr (ctx, size); + cp_out (ctx, CP_SEEK_1); + cp_out (ctx, CP_XFER_1); + cp_wait(ctx, XFER, BUSY); +} + +/* + * non-trivial demagiced parts of ctx init go here + */ + +static void +nv50_graph_construct_gene_m2mf(struct nouveau_grctx *ctx) +{ + /* m2mf state */ + xf_emit (ctx, 1, 0); /* DMA_NOTIFY instance >> 4 */ + xf_emit (ctx, 1, 0); /* DMA_BUFFER_IN instance >> 4 */ + xf_emit (ctx, 1, 0); /* DMA_BUFFER_OUT i...

Adds H.264 and MPEG2 codec support via VP2, using firmware from the blob. Acceleration is supported at the bitstream level for H.264 and IDCT level for MPEG2. Known issues: - H.264 interlaced doesn't render properly - H.264 shows very occasional artifacts on a small fraction of videos - MPEG2 + VDPAU shows frequent but small artifacts, which aren't there when using XvMC on the same