Re: CVS commit: [matt-nb5-mips64] src/sys/arch/mips/mips
> O64 kernel? why should we worry about O64? For "completeness". :) Masao
Re: CVS commit: [matt-nb5-mips64] src/sys/arch/mips/mips
On Sep 2, 2009, at 4:41 PM, Masao Uebayashi wrote: @@ -876,10 +876,17 @@ moves2, t2 # stash most of temporary regs REG_S t3, FRAME_T3(k1)# syscall saved gp for fork mfc0a1, MIPS_COP_0_STATUS # 2nd arg is STATUS +#if defined(__mips_n32) || defined(__mips_n64) + REG_S a4, FRAME_A4(k1) + REG_S a5, FRAME_A5(k1) + REG_S a6, FRAME_A6(k1) + REG_S a7, FRAME_A7(k1) +#else moves4, ta0 moves5, ta1 moves6, ta2 moves7, ta3 +#endif #REG_S t8, FRAME_T8(k1) #REG_S t9, FRAME_T9(k1) REG_S gp, FRAME_GP(k1) This should be #if !defined(__mips_o32) ... #else ... #endif. Otherwise O64 kernel + N32/N64 userland won't work. O64 kernel? why should we worry about O64?
Re: CVS commit: [matt-nb5-mips64] src/sys/arch/mips/mips
> @@ -876,10 +876,17 @@ > moves2, t2 # stash most of temporary regs > REG_S t3, FRAME_T3(k1)# syscall saved gp for fork > mfc0a1, MIPS_COP_0_STATUS # 2nd arg is STATUS > +#if defined(__mips_n32) || defined(__mips_n64) > + REG_S a4, FRAME_A4(k1) > + REG_S a5, FRAME_A5(k1) > + REG_S a6, FRAME_A6(k1) > + REG_S a7, FRAME_A7(k1) > +#else > moves4, ta0 > moves5, ta1 > moves6, ta2 > moves7, ta3 > +#endif > #REG_S t8, FRAME_T8(k1) > #REG_S t9, FRAME_T9(k1) > REG_S gp, FRAME_GP(k1) This should be #if !defined(__mips_o32) ... #else ... #endif. Otherwise O64 kernel + N32/N64 userland won't work. Masao
Re: CVS commit: src/sys/arch/x86/acpi
On Wed, Sep 02, 2009 at 02:42:58PM -0500, David Young wrote: > You could leave it out of the sysctl tree. Setting it to 0 or 1 still makes sense w/o VGA_POST. Martin
Re: CVS commit: src/sys/arch/x86/acpi
On Wed, Sep 02, 2009 at 03:42:31PM +, Joerg Sonnenberger wrote: > Module Name: src > Committed By: joerg > Date: Wed Sep 2 15:42:31 UTC 2009 > > Modified Files: > src/sys/arch/x86/acpi: acpi_wakeup.c > > Log Message: > Be a bit more noisy by telling the user VGA_POST is missing in the > kernel config when trying machdep.acpi_vbios_reset=2. You could leave it out of the sysctl tree. Dave -- David Young OJC Technologies dyo...@ojctech.com Urbana, IL * (217) 278-3933
Re: CVS commit: src/sys
On Wed, Sep 02, 2009 at 02:22:38PM -0400, Thor Lancelot Simon wrote: > On Wed, Sep 02, 2009 at 08:11:35PM +0200, Thomas Klausner wrote: > > > > > Log Message: > > > Add a direction argument to socket upcalls, so they can tell why they've > > > been called when, for example, they're waiting for space to write. From > > > Ritesh Agrawal at Coyote Point. > > > > Do you think this might be related to: > > --- dependall-nfsserver --- > > /archive/build/tools/bin/x86_64--netbsd-gcc -O2 -mcmodel=kernel -Wall > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare > > -Wno-traditional -Wa,--fatal-warnings -Werror -ffreestanding > > -fno-strict-aliasing -Wno-pointer-sign -I/archive/cvs/src/common/include > > -DNFS -DNFSSERVER -I/archive/cvs/src/common/include -nostdinc -I. > > -I/archive/cvs/src/sys/modules/nfsserver -isystem /archive/cvs/src/sys > > -isystem /archive/cvs/src/sys/arch -isystem > > /archive/cvs/src/sys/../common/include -D_KERNEL -D_LKM -D_MODULE -c > > /archive/cvs/src/sys/nfs/nfs_syscalls.c > > cc1: warnings being treated as errors > > /archive/cvs/src/sys/nfs/nfs_syscalls.c: In function 'nfssvc_addsock': > > /archive/cvs/src/sys/nfs/nfs_syscalls.c:410: warning: assignment from > > incompatible pointer type > > Not really -- I did a full build of GENERIC with this change in... let me > check I didn't miss anything in the NFS code. That's not a kernel build, that's from a 'build.sh distribution' Thomas
Re: CVS commit: src/sys
On Wed, Sep 02, 2009 at 08:11:35PM +0200, Thomas Klausner wrote: > > > Log Message: > > Add a direction argument to socket upcalls, so they can tell why they've > > been called when, for example, they're waiting for space to write. From > > Ritesh Agrawal at Coyote Point. > > Do you think this might be related to: > --- dependall-nfsserver --- > /archive/build/tools/bin/x86_64--netbsd-gcc -O2 -mcmodel=kernel -Wall > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare > -Wno-traditional -Wa,--fatal-warnings -Werror -ffreestanding > -fno-strict-aliasing -Wno-pointer-sign -I/archive/cvs/src/common/include > -DNFS -DNFSSERVER -I/archive/cvs/src/common/include -nostdinc -I. > -I/archive/cvs/src/sys/modules/nfsserver -isystem /archive/cvs/src/sys > -isystem /archive/cvs/src/sys/arch -isystem > /archive/cvs/src/sys/../common/include -D_KERNEL -D_LKM -D_MODULE -c > /archive/cvs/src/sys/nfs/nfs_syscalls.c > cc1: warnings being treated as errors > /archive/cvs/src/sys/nfs/nfs_syscalls.c: In function 'nfssvc_addsock': > /archive/cvs/src/sys/nfs/nfs_syscalls.c:410: warning: assignment from > incompatible pointer type Not really -- I did a full build of GENERIC with this change in... let me check I didn't miss anything in the NFS code. Thor
Re: CVS commit: src/sys
On Wed, Sep 02, 2009 at 02:56:57PM +, Thor Lancelot Simon wrote: > Module Name: src > Committed By: tls > Date: Wed Sep 2 14:56:57 UTC 2009 > > Modified Files: > src/sys/kern: uipc_socket2.c > src/sys/net: if_gre.c > src/sys/netinet: accf_data.c accf_http.c > src/sys/sys: socketvar.h > > Log Message: > Add a direction argument to socket upcalls, so they can tell why they've > been called when, for example, they're waiting for space to write. From > Ritesh Agrawal at Coyote Point. Do you think this might be related to: --- dependall-nfsserver --- /archive/build/tools/bin/x86_64--netbsd-gcc -O2 -mcmodel=kernel -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wno-traditional -Wa,--fatal-warnings -Werror -ffreestanding -fno-strict-aliasing -Wno-pointer-sign -I/archive/cvs/src/common/include -DNFS -DNFSSERVER -I/archive/cvs/src/common/include -nostdinc -I. -I/archive/cvs/src/sys/modules/nfsserver -isystem /archive/cvs/src/sys -isystem /archive/cvs/src/sys/arch -isystem /archive/cvs/src/sys/../common/include -D_KERNEL -D_LKM -D_MODULE -c/archive/cvs/src/sys/nfs/nfs_syscalls.c cc1: warnings being treated as errors /archive/cvs/src/sys/nfs/nfs_syscalls.c: In function 'nfssvc_addsock': /archive/cvs/src/sys/nfs/nfs_syscalls.c:410: warning: assignment from incompatible pointer type Thomas
Re: CVS commit: src/sys/sys
On Wed, Sep 02, 2009 at 03:45:10PM +, Thor Lancelot Simon wrote: > Module Name: src > Committed By: tls > Date: Wed Sep 2 15:45:10 UTC 2009 > > Modified Files: > src/sys/sys: param.h > > Log Message: > Bump __NetBSD_Version__ for previous, per ad@ -- welcome to 5.99.16. For which previous? There is no way to tell it from cvs log. Bernd
Re: CVS commit: src/share/man/man9
On Wed, 2 Sep 2009, Thomas Klausner wrote: Date: Wed, 2 Sep 2009 13:32:54 +0200 From: Thomas Klausner Reply-To: source-changes-d@netbsd.org To: source-changes-d@netbsd.org Subject: Re: CVS commit: src/share/man/man9 On Wed, Sep 02, 2009 at 10:54:20AM +, Adam Hoka wrote: Module Name:src Committed By: ahoka Date: Wed Sep 2 10:54:20 UTC 2009 Modified Files: src/share/man/man9: csf.9 Log Message: Mention sched_m4. # man sched_m2 man: no entry for sched_m2 in the manual. # man sched_m4 man: no entry for sched_m4 in the manual. Thomas I meant m2, of course. I will put together something for sched_m2 manpage to give the users at least a little clue. Well don't expect any verbose documentation. :-)
Re: CVS commit: src/share/man/man9
On Wed, Sep 02, 2009 at 10:54:20AM +, Adam Hoka wrote: > Module Name: src > Committed By: ahoka > Date: Wed Sep 2 10:54:20 UTC 2009 > > Modified Files: > src/share/man/man9: csf.9 > > Log Message: > Mention sched_m4. # man sched_m2 man: no entry for sched_m2 in the manual. # man sched_m4 man: no entry for sched_m4 in the manual. Thomas
