Searched +hist:1.56 +hist:2.10 (Results 1 - 13 of 13) sorted by relevance
| /src/sbin/savecore/ | ||
| H A D | savecore.c | 1.56 Wed Mar 06 13:13:08 GMT 2002 tsutsui Change type of dumpmag and newdumpmag from int to u_int32_t since they hold 32bit unsigned magic numbers. (sync with kernels) 1.50 Thu Jan 11 20:27:12 GMT 2001 martin Make option flag variables static. This avoids a conflict between 'int compress' in savecore.c and the function 'compress' in libz. Gnu ld 2.10 (with BFD 2.10) used on sparc64 warns this conflict (symbol "compress" changed size). 1.50 Thu Jan 11 20:27:12 GMT 2001 martin Make option flag variables static. This avoids a conflict between 'int compress' in savecore.c and the function 'compress' in libz. Gnu ld 2.10 (with BFD 2.10) used on sparc64 warns this conflict (symbol "compress" changed size). |
| /src/distrib/sets/lists/xdebug/ | ||
| H A D | shl.mi | 1.56 Sun Oct 25 16:59:27 GMT 2020 nia Unhook libglut (MesaGLUT) from the build. The GL Utility Library was formerly a core part of most OpenGL distributions. Originally, this version of libglut was developed as part of Mesa (the primary OpenGL implementation used in NetBSD) before it was mostly abandoned and work moved to the freeglut fork. It provides a platform-neutral way of creating OpenGL contexts, something that many other libraries can also do today (e.g. SDL, glfw). All users in pkgsrc have been switched to the freeglut fork and there are no remaining users of this library in src. If having a GLUT implementation in base turns out to be particularly useful outside of compatibility with previous NetBSD versions, we can import freeglut (which, AFAIK, is also ABI compatible with MesaGLUT). 1.52 Sat Jul 20 02:06:12 GMT 2019 mrg updates for freetype 2.10.0 1.8 Mon Jun 03 20:23:40 GMT 2013 mrg updates for fontconfig 2.10.93. |
| /src/distrib/sets/lists/xbase/ | ||
| H A D | mi | 1.118 Mon Jun 03 20:23:40 GMT 2013 mrg updates for fontconfig 2.10.93. 1.117 Mon Jun 03 07:08:20 GMT 2013 mrg add fontconfig 2.10.2 files. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.118 Mon Jun 03 20:23:40 GMT 2013 mrg updates for fontconfig 2.10.93. 1.117 Mon Jun 03 07:08:20 GMT 2013 mrg add fontconfig 2.10.2 files. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. 1.56 Thu Jan 03 20:48:03 GMT 2008 jdc branches: 1.56.2; 1.56.6; 1.56.8; 1.56.10; Add a note about marking entries as "obsolete", instead of deleting them. |
| H A D | shl.mi | 1.87 Sat Jul 20 02:06:12 GMT 2019 mrg updates for freetype 2.10.0 1.56 Wed Oct 01 09:30:58 GMT 2014 skrll Fix SHLIB_MAJOR to match xorg and fix linking against libxcb-sync which broke kwin for me. 1.49 Mon Jun 03 20:23:40 GMT 2013 mrg updates for fontconfig 2.10.93. |
| /src/sys/dev/usb/ | ||
| H A D | umass_quirks.c | 1.56 Wed Sep 17 07:49:11 GMT 2003 mycroft Shuttle products do not need PQUIRK_NOTUR any more. Also removing them for the other two items, since they are presumed unnecessary. 1.52 Wed Sep 10 02:49:19 GMT 2003 mycroft cc -pipe -ffreestanding -O2 -Werror -Wall -Wno-main -Wno-format-zero-length -Fix several problems with CCI handling, and enable it: * We were never calling the callback function when we got a UFI CCI(!). * We were passing a bogus residual count on non-UFI CCIs. * After a REQUEST SENSE, the UFI CCI may include the ASC/ASCQ from the sense information -- don't consider this a failure. In addition, remove a horrible hack that was causing us to drop sense information on the floor and return empty INQUIRY responses, often in the case where there is a UNIT ATTENTION pending during the INQUIRY. (Some drives send the data and then fail, some don't.) This eliminates the need for quirks for the Y-E DATA FlashBuster. These changes work on: umass0: SAMSUNG SFD-321U [FW 0C], rev 1.10/2.10, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus1 drive 0: <SMSC, USB FDC, 2.10> disk removable umass0: TEAC TEAC FD-05PUB, rev 1.10/0.00, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <TEAC, FD-05PUB, 1026> disk removable umass0: Y-E DATA FlashBuster-U, rev 1.00/3.04, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <Y-E DATA, USB-FDU, 3.04> disk removable 1.52 Wed Sep 10 02:49:19 GMT 2003 mycroft cc -pipe -ffreestanding -O2 -Werror -Wall -Wno-main -Wno-format-zero-length -Fix several problems with CCI handling, and enable it: * We were never calling the callback function when we got a UFI CCI(!). * We were passing a bogus residual count on non-UFI CCIs. * After a REQUEST SENSE, the UFI CCI may include the ASC/ASCQ from the sense information -- don't consider this a failure. In addition, remove a horrible hack that was causing us to drop sense information on the floor and return empty INQUIRY responses, often in the case where there is a UNIT ATTENTION pending during the INQUIRY. (Some drives send the data and then fail, some don't.) This eliminates the need for quirks for the Y-E DATA FlashBuster. These changes work on: umass0: SAMSUNG SFD-321U [FW 0C], rev 1.10/2.10, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus1 drive 0: <SMSC, USB FDC, 2.10> disk removable umass0: TEAC TEAC FD-05PUB, rev 1.10/0.00, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <TEAC, FD-05PUB, 1026> disk removable umass0: Y-E DATA FlashBuster-U, rev 1.00/3.04, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <Y-E DATA, USB-FDU, 3.04> disk removable |
| H A D | umass_scsipi.c | 1.56 Tue Nov 13 10:30:57 GMT 2018 mlelstv Handle abort paths gracefully on detach. 1.11 Wed Sep 10 02:49:19 GMT 2003 mycroft cc -pipe -ffreestanding -O2 -Werror -Wall -Wno-main -Wno-format-zero-length -Fix several problems with CCI handling, and enable it: * We were never calling the callback function when we got a UFI CCI(!). * We were passing a bogus residual count on non-UFI CCIs. * After a REQUEST SENSE, the UFI CCI may include the ASC/ASCQ from the sense information -- don't consider this a failure. In addition, remove a horrible hack that was causing us to drop sense information on the floor and return empty INQUIRY responses, often in the case where there is a UNIT ATTENTION pending during the INQUIRY. (Some drives send the data and then fail, some don't.) This eliminates the need for quirks for the Y-E DATA FlashBuster. These changes work on: umass0: SAMSUNG SFD-321U [FW 0C], rev 1.10/2.10, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus1 drive 0: <SMSC, USB FDC, 2.10> disk removable umass0: TEAC TEAC FD-05PUB, rev 1.10/0.00, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <TEAC, FD-05PUB, 1026> disk removable umass0: Y-E DATA FlashBuster-U, rev 1.00/3.04, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <Y-E DATA, USB-FDU, 3.04> disk removable 1.11 Wed Sep 10 02:49:19 GMT 2003 mycroft cc -pipe -ffreestanding -O2 -Werror -Wall -Wno-main -Wno-format-zero-length -Fix several problems with CCI handling, and enable it: * We were never calling the callback function when we got a UFI CCI(!). * We were passing a bogus residual count on non-UFI CCIs. * After a REQUEST SENSE, the UFI CCI may include the ASC/ASCQ from the sense information -- don't consider this a failure. In addition, remove a horrible hack that was causing us to drop sense information on the floor and return empty INQUIRY responses, often in the case where there is a UNIT ATTENTION pending during the INQUIRY. (Some drives send the data and then fail, some don't.) This eliminates the need for quirks for the Y-E DATA FlashBuster. These changes work on: umass0: SAMSUNG SFD-321U [FW 0C], rev 1.10/2.10, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus1 drive 0: <SMSC, USB FDC, 2.10> disk removable umass0: TEAC TEAC FD-05PUB, rev 1.10/0.00, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <TEAC, FD-05PUB, 1026> disk removable umass0: Y-E DATA FlashBuster-U, rev 1.00/3.04, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <Y-E DATA, USB-FDU, 3.04> disk removable |
| H A D | umass.c | 1.100 Wed Sep 10 02:49:18 GMT 2003 mycroft cc -pipe -ffreestanding -O2 -Werror -Wall -Wno-main -Wno-format-zero-length -Fix several problems with CCI handling, and enable it: * We were never calling the callback function when we got a UFI CCI(!). * We were passing a bogus residual count on non-UFI CCIs. * After a REQUEST SENSE, the UFI CCI may include the ASC/ASCQ from the sense information -- don't consider this a failure. In addition, remove a horrible hack that was causing us to drop sense information on the floor and return empty INQUIRY responses, often in the case where there is a UNIT ATTENTION pending during the INQUIRY. (Some drives send the data and then fail, some don't.) This eliminates the need for quirks for the Y-E DATA FlashBuster. These changes work on: umass0: SAMSUNG SFD-321U [FW 0C], rev 1.10/2.10, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus1 drive 0: <SMSC, USB FDC, 2.10> disk removable umass0: TEAC TEAC FD-05PUB, rev 1.10/0.00, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <TEAC, FD-05PUB, 1026> disk removable umass0: Y-E DATA FlashBuster-U, rev 1.00/3.04, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <Y-E DATA, USB-FDU, 3.04> disk removable 1.100 Wed Sep 10 02:49:18 GMT 2003 mycroft cc -pipe -ffreestanding -O2 -Werror -Wall -Wno-main -Wno-format-zero-length -Fix several problems with CCI handling, and enable it: * We were never calling the callback function when we got a UFI CCI(!). * We were passing a bogus residual count on non-UFI CCIs. * After a REQUEST SENSE, the UFI CCI may include the ASC/ASCQ from the sense information -- don't consider this a failure. In addition, remove a horrible hack that was causing us to drop sense information on the floor and return empty INQUIRY responses, often in the case where there is a UNIT ATTENTION pending during the INQUIRY. (Some drives send the data and then fail, some don't.) This eliminates the need for quirks for the Y-E DATA FlashBuster. These changes work on: umass0: SAMSUNG SFD-321U [FW 0C], rev 1.10/2.10, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus1 drive 0: <SMSC, USB FDC, 2.10> disk removable umass0: TEAC TEAC FD-05PUB, rev 1.10/0.00, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <TEAC, FD-05PUB, 1026> disk removable umass0: Y-E DATA FlashBuster-U, rev 1.00/3.04, addr 2 umass0: using UFI over CBI with CCI sd0 at atapibus0 drive 0: <Y-E DATA, USB-FDU, 3.04> disk removable 1.56 Fri Apr 13 00:24:10 GMT 2001 augustss Split the umass driver into the part that handles the X-over-USB protocol (umass.c) and the part that handles scsibus/atapibus (umassbus.c). This way the must port specific stuff can be removed from umass.c. |
| /src/sys/arch/i386/stand/lib/ | ||
| H A D | biosdisk.c | 1.56 Tue Dec 28 00:34:30 GMT 2021 simonb Fix a tyop. 1.14 Fri Jun 01 23:26:31 GMT 2001 jdolecek g/c COMPAT_OLDBOOT from bootblocks, sprinkle some const bump bootblock version to 2.10 |
| H A D | libi386.h | 1.56 Thu Oct 09 16:10:03 GMT 2025 manu Add support for USB-to-serial adapter in UEFI bootstrap. This change lets UEFI bootstrap use any UEFI supported serial port. com0 to com3 remain used for EISA based serial ports. com4 and over are used for serial ports based on something else (USB, PCI or whatever). Support for non-EISA serial ports may be provided by UEFI. An open source UEFI driver exists for FTDI FT232R USB-to-serial adapter. The change also introduce the kconsdev command, to select the kernel console device without altering the bootstrap console device. This useful because the device names can differ in bootstrap and kernel. For instance an USB-to-serial device could be com4 in boostrap and ucom0 for the kernel. An upcoming change will add console suport to ucom(4). 1.14 Fri Jun 01 23:26:31 GMT 2001 jdolecek branches: 1.14.2; g/c COMPAT_OLDBOOT from bootblocks, sprinkle some const bump bootblock version to 2.10 |
| H A D | exec.c | 1.56 Mon Dec 30 21:45:51 GMT 2013 jakllsch Zero out on-stack 'marks' array before first use. This is needed so the MARK_DATA index is properly filled in. 1.17 Fri Jun 01 23:26:31 GMT 2001 jdolecek branches: 1.17.2; g/c COMPAT_OLDBOOT from bootblocks, sprinkle some const bump bootblock version to 2.10 |
| /src/sys/arch/arm/arm/ | ||
| H A D | arm_machdep.c | 1.56 Sat Nov 23 19:40:34 GMT 2019 ad cpu_need_resched(): - Remove all code that should be MI, leaving the bare minimum under arch/. - Make the required actions very explicit. - Pass in LWP pointer for convenience. - When a trap is required on another CPU, have the IPI set it locally. - Expunge cpu_did_resched(). 1.48 Sat May 02 16:18:49 GMT 2015 skrll Move /* A5.2.10 Synchronisation primitives */ block earlier so it matches correctly |
| /src/sys/kern/ | ||
| H A D | kern_sleepq.c | 1.56 Tue Dec 17 18:08:15 GMT 2019 ad branches: 1.56.2; Fix LOCKDEBUG panic on mutex_init(). Reported-by: syzbot+5a77339dc0a55e8d8caa@syzkaller.appspotmail.com 1.56 Tue Dec 17 18:08:15 GMT 2019 ad branches: 1.56.2; Fix LOCKDEBUG panic on mutex_init(). Reported-by: syzbot+5a77339dc0a55e8d8caa@syzkaller.appspotmail.com 1.13 Fri Aug 31 15:27:18 GMT 2007 yamt pull the following change from vmlocking branch. revision 1.7.2.10 date: 2007/08/27 12:51:13; author: yamt; state: Exp; lines: +6 -7 sleepq_block: don't call lwp_unsleep twice. (fix an assertion failure in lwp_unsleep.) 1.56 Tue Dec 17 18:08:15 GMT 2019 ad branches: 1.56.2; Fix LOCKDEBUG panic on mutex_init(). Reported-by: syzbot+5a77339dc0a55e8d8caa@syzkaller.appspotmail.com 1.56 Tue Dec 17 18:08:15 GMT 2019 ad branches: 1.56.2; Fix LOCKDEBUG panic on mutex_init(). Reported-by: syzbot+5a77339dc0a55e8d8caa@syzkaller.appspotmail.com 1.13 Fri Aug 31 15:27:18 GMT 2007 yamt pull the following change from vmlocking branch. revision 1.7.2.10 date: 2007/08/27 12:51:13; author: yamt; state: Exp; lines: +6 -7 sleepq_block: don't call lwp_unsleep twice. (fix an assertion failure in lwp_unsleep.) 1.56 Tue Dec 17 18:08:15 GMT 2019 ad branches: 1.56.2; Fix LOCKDEBUG panic on mutex_init(). Reported-by: syzbot+5a77339dc0a55e8d8caa@syzkaller.appspotmail.com 1.56 Tue Dec 17 18:08:15 GMT 2019 ad branches: 1.56.2; Fix LOCKDEBUG panic on mutex_init(). Reported-by: syzbot+5a77339dc0a55e8d8caa@syzkaller.appspotmail.com 1.13 Fri Aug 31 15:27:18 GMT 2007 yamt pull the following change from vmlocking branch. revision 1.7.2.10 date: 2007/08/27 12:51:13; author: yamt; state: Exp; lines: +6 -7 sleepq_block: don't call lwp_unsleep twice. (fix an assertion failure in lwp_unsleep.) |
| /src/distrib/sets/lists/xcomp/ | ||
| H A D | mi | 1.218 Wed Oct 21 15:12:15 GMT 2020 maya Build fixes for freetype 2.10.4 1.137 Mon Jun 03 07:08:21 GMT 2013 mrg add fontconfig 2.10.2 files. 1.56 Sat Oct 04 18:46:20 GMT 2008 cube Install manual pages for libXv. |
Completed in 152 milliseconds