Re: SCHED_ASSERT_UNLOCKED is considered harmful in the _kernel_lock()

On Mon, Nov 8, 2010 at 1:01 AM, Philip Guenther guent...@gmail.com wrote: On Sunday, November 7, 2010, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Fri, 5 Nov 2010 17:52:23 +0100 From: Mike Belopuhov m...@crypt.org.ru Mike, you might want to take a look at PR 6508. I think the

Re: SCHED_ASSERT_UNLOCKED is considered harmful in the _kernel_lock()

Date: Sun, 7 Nov 2010 16:01:05 -0800 From: Philip Guenther guent...@gmail.com On Sunday, November 7, 2010, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Fri, 5 Nov 2010 17:52:23 +0100 From: Mike Belopuhov m...@crypt.org.ru Mike, you might want to take a look at PR 6508. I think

aesni_ctr_enc: accept a complete ICB rather than IV

hi, i need to change aesni_ctr_enc a bit to pass an already constructed initial counter block (ICB) rather than do it in the function itself. this will allow me to share the code with aes-gcm. if i won't hear any objections, i'll commit this on wednesday. works for me without issues. Index:

MID_AMD64 is missing in the byte order check code in nm(1)

we didn't hit it before because it's used only in the unusual situation. ok to commit? Index: byte.c === RCS file: /home/cvs/src/usr.bin/nm/byte.c,v retrieving revision 1.6 diff -u -p -U5 -r1.6 byte.c --- byte.c 9 Oct 2004

Re: MID_AMD64 is missing in the byte order check code in nm(1)

Date: Mon, 8 Nov 2010 14:57:03 +0100 From: Mike Belopuhov m...@crypt.org.ru we didn't hit it before because it's used only in the unusual situation. Which unusual situation? There really shouldn't be any a.out amd64 binaries or object modules out there.

Re: MID_AMD64 is missing in the byte order check code in nm(1)

On Mon, Nov 8, 2010 at 3:07 PM, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Mon, 8 Nov 2010 14:57:03 +0100 From: Mike Belopuhov m...@crypt.org.ru we didn't hit it before because it's used only in the unusual situation. Which unusual situation? There really shouldn't be any a.out

Add Xbox 360 Controller USB support

This is taken pretty much straight from FreeBSD ( see http://marc.info/?l=freebsd-commits-allm=113600388101707w=2 ). It is tested and working on my amd64 box. Some usbhidctl output: Generic_Desktop:Game_Pad.Generic_Desktop:Pointer.Generic_Desktop:D-pad_Up=0

Re: Add Xbox 360 Controller USB support

On Mon, Nov 8, 2010 at 3:38 PM, Joe Gidi j...@entropicblur.com wrote: This is taken pretty much straight from FreeBSD ( see http://marc.info/?l=freebsd-commits-allm=113600388101707w=2 ). It is tested and working on my amd64 box. Some usbhidctl output: At a minimum, should probably be inside

waitpid not returning 0 when WNOHANG specified ?

Hi, I must be doing something really silly but it seems waitpid ends up returning -1 if WNOHANG is specified and there are no children to reap. Am I doing something wrong ? #include sys/types.h #include sys/wait.h #include err.h #include signal.h #include stdio.h #include stdlib.h #include

Re: waitpid not returning 0 when WNOHANG specified ?

On Mon, Nov 8, 2010 at 4:10 PM, Christiano F. Haesbaert haesba...@haesbaert.org wrote: I must be doing something really silly but it seems waitpid ends up returning -1 if WNOHANG is specified and there are no children to reap. Umm, that's what the standard specifies. Philip Guenther

Todo para Soldar

$498 PesosSoldadora Turbo 270 Bifasica Soldadora Electrica Turbo Ventilada 270 Amper Monosica y Trifasica / Con Protector Teacute;rmico / Amperaje regulable 50 a

Re: waitpid not returning 0 when WNOHANG specified ?

On 11/09/10 03:27, Philip Guenther wrote: On Mon, Nov 8, 2010 at 4:10 PM, Christiano F. Haesbaert haesba...@haesbaert.org wrote: I must be doing something really silly but it seems waitpid ends up returning -1 if WNOHANG is specified and there are no children to reap. Umm, that's what the