search for: nibble

...her than normal background anyway, and it sounds clear enough when I just do playthrough for testing. The problem is, this uses nibbling, which means the input jitters in time in relation to the output. I also don't know what Apple does under the hood for playback, they almost certainly nibble as well. 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. Assu...

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: unassigned-bugs at mindrot.org Reporter: vapi...

...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 */ + mov...

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 */ + mov...

...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 */ + mov...

...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 don't have a lot of...

...ayed 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 at 128 samples at a time, filling a 256 byte buffer, and you have a player that writes 256 samples at a time, or 512 bytes. You have to nibble a frame every 160 samples, so you get this, where each digit represents 32 samples, so 00000 is 160 samples: 0 1 2 3 4 5 6 7 <- timestamp when each speex frame is read 0000111122223333444455556666777788889999 <- input frame 000001111122222333334444455555666667...

...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 2DD...

...can't ship a soundcard that records and plays at the > same rate? I > have a hard time believing that. It is actually very likely that input and output are on the same card at 44100 Hz. What's problematic is getting the right sized hardware buffers. I wrote a whole library to nibble and give me the 160 I need, but I have no idea what is happening under the hood, or if I can even ask apple for the same size input and output buffers, because I am using their classic sound engine which is archaic by today's standards. I could probably switch to using core audio or...

...the call transfer. This frees up the analog phone line to process another call and the central office handles the transfered call. This transfer feature can be done with a channelized winkstart T1, and is possible on a PRI. On a PRI, this feature is called a 2B Channel Transfer. Contact us at voip3@nibble.net.

...*************** %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 + a...

...ng protocols, > but this does not happen in what I consider your faulty FW. > i.e. > if we consider > PXEBaseCode handle 267 -> MAC 0065F36E00EE More importantly: look at the actual captured text. It does NOT specify a valid MAC in its entirety and leaves off the leading nibble (11 characters, not 12). Handle 267 shows "065F36E00EE" not "0065F36E00EE". > UDPv4ServiceBinding handle 23E -> MAC 5065F36E00EE > > You can see the MACs are "almost" identical but there's not match! > While 5065F36E00EE is a valid HP MAC, 0065F36...

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

...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 definition of shiftcount. I prefer to add this comment: int shiftcount; // bit position, in the current word, of the next nibble to print. This is a problem with the original code, not the patch.) The patch removes half case from the code for single and double. So you should remove the "bool isHalf" variable in that spot. (line 720) Line 762. Update the comment // Some form of long double. Th...

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 outlining, but the average was still over 3% with some as high as 9-10%. > > All the tests I ran were fine, although we don't have...

...possible, right after "if ( const ConstantFP ..." at line 710 > > (The code makes a lot more sense with a good comment on the > definition > of shiftcount. I prefer to add this comment: > int shiftcount; // bit position, in the current word, of the > next nibble to print. > This is a problem with the original code, not the patch.) Done. > The patch removes half case from the code for single and double. > So you should remove the "bool isHalf" variable in that spot. (line > 720) I'm not sure I get it. This variable is st...