search for: _random_

...ild environment. And then the > the third attempt to build kernels rpm succeeded! I assumed a hardware > failure (see outdated above) and made a mental note to investigate that > one of these days. > > But your report makes me think it's not my hardware. Could there be some > _random_ failure with this driver in the build? Very odd... A theory based on Mark's message in https://lkml.org/lkml/2014/12/8/602 : My two failed builds somehow used previous version of class.h, that didn't yet have commit 1f89b4756fb8 ("drm/gm204/disp: initial support") applied. It...

CHK kernel/config_data.h CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function ‘nvd0_dmaobj_bind’: drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error: ‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function) case GM204_DISP_CORE_CHANNEL_DMA: ^

...ally, well, scrubbed the rpmbuild environment. And then the the third attempt to build kernels rpm succeeded! I assumed a hardware failure (see outdated above) and made a mental note to investigate that one of these days. But your report makes me think it's not my hardware. Could there be some _random_ failure with this driver in the build? Very odd... Paul Bolle

...;complete" (in the sense that the headers were not already sent, i.e. client->pos == 0) and that is not a a pre_data. OTH, it seems logic and without that property icecast wouldn't work: when a new client connects, icecast sends it a pre_data and then start with the first available _random_ refbuf. What's the problem with "restarting" the stream with a "new", out of sequence, refbuf? But I could be missing something, sorry if so. <p> -- ricardo galli GPG id C8114D34 --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project...

...en the >> the third attempt to build kernels rpm succeeded! I assumed a hardware >> failure (see outdated above) and made a mental note to investigate that >> one of these days. >> >> But your report makes me think it's not my hardware. Could there be some >> _random_ failure with this driver in the build? Very odd... > A theory based on Mark's message in > https://lkml.org/lkml/2014/12/8/602 : > > My two failed builds somehow used previous version of class.h, that > didn't yet have commit 1f89b4756fb8 ("drm/gm204/disp: initial suppor...

On Saturday 18 January 2003 03:37, Michael Smith shaped the electrons to shout: > We can't just drop packets, the transmission model assumed by the > format handlers (and required by at least one of them) will not permit It's not vorbis. Does it? > us to drop any data. It'd be possible, in theory at least, to tag > buffers with a flag to say that they can be dropped, but

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of