search for: nibbles

...This means that the echo canceler will nearly always see a different time offset for the current buffer pair, than for the previous ones. So it seems to me that in order for echo cancellation to work, it has to tolerate nibbling up to roughly 160/8000 or 1/50th of a second. Assuming that 2 nibbles can happen, one on input and one on output, this becomes 1/25th of a second. In other words, feeding the input and output buffers shifted in time +/- 1/25th of a second to the echo canceler should always give roughly the same output, but I think that may not be happening right now. Is thi...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drm/nouveau/nvkm/engine/gr/ctxgk20a.c | 2 +- drm/nouveau/nvkm/subdev/fb/ramgk104.c | 8 ++++---- drm/nouveau/nvkm/subdev/therm/nv40.c | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/drm/nouveau/nvkm/engine/gr/ctxgk20a.c b/drm/nouveau/nvkm/engine/gr/ctxgk20a.c index ddaa16a..ad0a6cf 100644 ---

https://bugzilla.mindrot.org/show_bug.cgi?id=2212 Bug ID: 2212 Summary: openssl version check should ignore status nibble Product: Portable OpenSSH Version: 6.5p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous Assignee:

...9; with 'C' in boot message */ + +use_lba_addressing: + /* convert drive-number to two hex characters and insert them into the boot message */ + movw (drive_number), %dx + pushw %dx /* preserve for use by calculate_geometry */ + movw $msg_drive_number, %di + movb $0x02, %cl /* write two nibbles */ + call write_hex_value + +calculate_geometry: + popw %dx /* retrieve drive number */ + movb $0x08, %ah + int $0x13 /* get drive parameters; returns CH LSB of max cyl., CL(7-6) MSb max cyl., */ + /* CL(5-0) max sector, DH max head, DL drive qty, ES:DI floppy parameter table */ + movb...

Couple of patches to fix an overflow, optimize a bit and support bigger resolutions using Windows 8.

...9; with 'C' in boot message */ +use_lba_addressing: + + /* convert drive-number to two hex characters and insert them into the boot message */ + movw (drive_number), %dx + pushw %dx /* preserve for use by calculate_geometry */ + movw $msg_drive_number, %di + movb $0x02, %cl /* write two nibbles */ + call write_hex_value + +calculate_geometry: + popw %dx /* retrieve drive number */ + movb $0x08, %ah + int $0x13 /* get drive parameters; returns CH LSB of max cyl., CL(7-6) MSb max cyl., */ + /* CL(5-0) max sector, DH max head, DL drive qty, ES:DI floppy parameter table */ + movb...

...9; with 'C' in boot message */ + +use_lba_addressing: + /* convert drive-number to two hex characters and insert them into the boot message */ + movw (drive_number), %dx + pushw %dx /* preserve for use by calculate_geometry */ + movw $msg_drive_number, %di + movb $0x02, %cl /* write two nibbles */ + call write_hex_value + +calculate_geometry: + popw %dx /* retrieve drive number */ + movb $0x08, %ah + int $0x13 /* get drive parameters; returns CH LSB of max cyl., CL(7-6) MSb max cyl., */ + /* CL(5-0) max sector, DH max head, DL drive qty, ES:DI floppy parameter table */ + movb...

...37a8dff5e360927ba10ab2 > > > > The final folder is simpel, as it is: > > > > %{sha256;truncate=96:user} > > > > But how do I get a first level from sha256? Unfortunately, the truncate > > option aligns only full 8bit and does not divide into low and high nibbles. > > How can I express this for sha256? > > > > in MD5 this would be %1Mu > > > > Many thanks in advance > > > > Christian > > Maybe as a workaround you can create a directory named /srv/mail/c and make 16 > symbolic links to it: /srv/mail/c0,...

Hello A 4.4% geomean codesize improvement is really impressive. That stuff is hard to come by, you usually have to nibble away at it bit at a time. I ran some codesize benchmarks we have and they were in the same ballpark. Some of these are quite small so had less opportunity for outlining, but the average was still over 3% with some as high as 9-10%. All the tests I ran were fine, although we

On Jul 2, 2007, at 7:34 PM, Jean-Marc Valin wrote: > Selon "Coffey, Michael" <mcoffey@avistar.com>: >> Believe me; I've "played with" priorities and buffering. > > Then either you haven't played well enough or you're using a > braindead OS. This is sort of what I was talking about with nibbling. Imagine you have a microphone sampling

...le with directory hashing. I want something like this: /srv/mail/c/cf37a8dff5e360927ba10ab2 The final folder is simpel, as it is: %{sha256;truncate=96:user} But how do I get a first level from sha256? Unfortunately, the truncate option aligns only full 8bit and does not divide into low and high nibbles. How can I express this for sha256? in MD5 this would be %1Mu Many thanks in advance Christian -- R??ner-Network-Solutions Karl-Br?ger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF...

On Jul 2, 2007, at 9:48 PM, Jean-Marc Valin wrote: > Selon zmorris@mac.com: >> But if the echo canceler IS using each frame's timestamp when it's >> trying to converge, it's almost guaranteed to fail on most operating >> systems, because the timestamp has such a high variability between >> frames, and can even sometimes be 0 for the output buffer in this

Maintainer: Express Line Date opened: January 17, 2006 Status: Open Value of bounty: $5000.00 Licensing for code: We retain intellectual rights to the underlying source code. We need Asterisk (stable version) to be able to perform a 2B channel transfer for a NI2 B8ZS PRI line. We can't use a channelized T1 at the time for our work. This feature is commonly called a call transfer on analog

...*************** %define IS_PXELINUX 1 %include "macros.inc" @@ -692,22 +697,39 @@ mov si,cfgprefix mov cx,cfgprefix_len rep movsb - mov cx,8 - mov eax,[MyIP] + mov cx,6 ; 6 nibbles in vendor part of MAC + mov eax,[MyMAC1] ; 3 bytes vendor part of MAC + xchg ah,al ; Convert to host byte order + ror eax,16 + xchg ah,al +.hexify_loop1: rol eax,4 + push eax + an...

On Fri, Aug 28, 2015 at 4:22 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > Thanks Derrik; I got your efi-dh.txt > > I've found this: > > 252: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) > 267: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EE,0x1)/IPv4(0.0.0.0)) > 27C: SimpleNetwork PXEBaseCode LoadFile

I have a question regarding the flags for hiding caller ID presentation: My customer has a requirement that they are able to specify if outbound calls (on a T100P) will have the caller ID displayed or not. This could be easily solved, of course, by not setting a caller ID when creating the outbound call. However, the PRI to which this T100P is connected _must_ see a valid caller ID, and the

I've got comments on the code change. The test cases look ok, but I haven't fully checked the math on the half-values. I checked with reference to trunk top-of-tree at revision 156617. I have not compiled the code. lib/AsmParser/LLLexer.cpp Adds support to parse format: 0xH<hexdigits> Tha 0xH format should be described in LangRef.html alongside 0xK<hex> and

From: Marc Carino <marc.ceeeee@gmail.com> Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate MIDR mask to the initialization phase. Further, ensure that the console output properly reports the CPU manufacturer as "Broadcom Corporation". Signed-off-by: Marc Carino <marc.ceeeee@gmail.com> --- xen/arch/arm/arm32/proc-v7.S | 8 ++++++++

Hi, On 25 April 2018 at 14:02, David Green via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hello > > A 4.4% geomean codesize improvement is really impressive. That stuff is hard to come by, you usually have to nibble away at it bit at a time. I ran some codesize benchmarks we have and they were in the same ballpark. Some of these are quite small so had less opportunity for

Hi David, Many thanks for the comments! > Tha 0xH format should be described in LangRef.html alongside > 0xK<hex> and 0xM<hex> Done. > Declaration of "int shiftcount" should be moved to smallest nesting > possible, right after "if ( const ConstantFP ..." at line 710 > > (The code makes a lot more sense with a good comment on the