Searched hist:1.221 (Results 1 - 25 of 220) sorted by relevance

123456789

/src/sys/ufs/lfs/
H A Dulfs_quota1.c1.10 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_dirhash.c1.16 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_extattr.c1.9 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dlfs_rename.c1.18 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_lookup.c1.38 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_quota2.c1.23 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_vnops.c1.40 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

/src/sys/dev/pcmcia/
H A Dpcmciadevs1.221 Sat Feb 10 03:14:03 GMT 2007 ichiro branches: 1.221.6; 1.221.14; 1.221.18;
add AirH pcmcia modem.
NEC Infrontia AX420N

1.221 Sat Feb 10 03:14:03 GMT 2007 ichiro branches: 1.221.6; 1.221.14; 1.221.18;
add AirH pcmcia modem.
NEC Infrontia AX420N

1.221 Sat Feb 10 03:14:03 GMT 2007 ichiro branches: 1.221.6; 1.221.14; 1.221.18;
add AirH pcmcia modem.
NEC Infrontia AX420N

1.221 Sat Feb 10 03:14:03 GMT 2007 ichiro branches: 1.221.6; 1.221.14; 1.221.18;
add AirH pcmcia modem.
NEC Infrontia AX420N

H A Dpcmciadevs.h1.221 Sat Sep 23 13:21:29 GMT 2006 jmcneill Regen for PR# 27840.

H A Dpcmciadevs_data.h1.221 Sat Sep 23 13:21:29 GMT 2006 jmcneill Regen for PR# 27840.

/src/sys/sys/
H A Dsyscallargs.h1.221 Tue Jan 18 17:34:28 GMT 2011 pooka branches: 1.221.2;
regen: include sys/sched.h in syscallargs.h

1.221 Tue Jan 18 17:34:28 GMT 2011 pooka branches: 1.221.2;
regen: include sys/sched.h in syscallargs.h

H A Dsysctl.h1.221 Mon Apr 04 23:31:46 GMT 2016 christos branches: 1.221.2; 1.221.4;
remove sys/wait.h just added, put it in the file that needed it (kvm_proc.c)

1.221 Mon Apr 04 23:31:46 GMT 2016 christos branches: 1.221.2; 1.221.4;
remove sys/wait.h just added, put it in the file that needed it (kvm_proc.c)

1.221 Mon Apr 04 23:31:46 GMT 2016 christos branches: 1.221.2; 1.221.4;
remove sys/wait.h just added, put it in the file that needed it (kvm_proc.c)

H A Dsystm.h1.221 Sun Apr 27 11:37:48 GMT 2008 ad branches: 1.221.2;
- Rename crit_enter/crit_exit to kpreempt_disable/kpreempt_enable.
DragonflyBSD uses the crit names for something quite different.
- Add a kpreempt_disabled function for diagnostic assertions.
- Add inline versions of kpreempt_enable/kpreempt_disable for primitives.
- Make some more changes for preemption safety to the x86 pmap.

1.221 Sun Apr 27 11:37:48 GMT 2008 ad branches: 1.221.2;
- Rename crit_enter/crit_exit to kpreempt_disable/kpreempt_enable.
DragonflyBSD uses the crit names for something quite different.
- Add a kpreempt_disabled function for diagnostic assertions.
- Add inline versions of kpreempt_enable/kpreempt_disable for primitives.
- Make some more changes for preemption safety to the x86 pmap.

/src/sys/arch/sparc/sparc/
H A Dcpu.c1.221 Sat Jan 23 16:06:57 GMT 2010 mrg branches: 1.221.2; 1.221.4;
rename cpu_info{}::cpu_name member to cpu_longname, to avoid a potential conflict
with <sys/cpu.h>.

1.221 Sat Jan 23 16:06:57 GMT 2010 mrg branches: 1.221.2; 1.221.4;
rename cpu_info{}::cpu_name member to cpu_longname, to avoid a potential conflict
with <sys/cpu.h>.

1.221 Sat Jan 23 16:06:57 GMT 2010 mrg branches: 1.221.2; 1.221.4;
rename cpu_info{}::cpu_name member to cpu_longname, to avoid a potential conflict
with <sys/cpu.h>.

H A Dautoconf.c1.221 Wed Mar 29 04:16:47 GMT 2006 thorpej branches: 1.221.14;
Use device_cfdata().

1.221 Wed Mar 29 04:16:47 GMT 2006 thorpej branches: 1.221.14;
Use device_cfdata().

/src/sys/arch/mips/mips/
H A Dtrap.c1.221 Mon Dec 14 00:46:07 GMT 2009 matt branches: 1.221.2; 1.221.4;
Merge from matt-nb5-mips64
Merge mips-specific arch files.

1.221 Mon Dec 14 00:46:07 GMT 2009 matt branches: 1.221.2; 1.221.4;
Merge from matt-nb5-mips64
Merge mips-specific arch files.

1.221 Mon Dec 14 00:46:07 GMT 2009 matt branches: 1.221.2; 1.221.4;
Merge from matt-nb5-mips64
Merge mips-specific arch files.

/src/sys/arch/pmax/pmax/
H A Dmachdep.c1.221 Wed Oct 17 19:56:15 GMT 2007 garbled branches: 1.221.2; 1.221.8;
Merge the ppcoea-renovation branch to HEAD.

This branch was a major cleanup and rototill of many of the various OEA
cpu based PPC ports that focused on sharing as much code as possible
between the various ports to eliminate near-identical copies of files in
every tree. Additionally there is a new PIC system that unifies the
interface to interrupt code for all different OEA ppc arches. The work
for this branch was done by a variety of people, too long to list here.

TODO:
bebox still needs work to complete the transition to -renovation.
ofppc still needs a bunch of work, which I will be looking at.
ev64260 still needs to be renovated
amigappc was not attempted.

NOTES:
pmppc was removed as an arch, and moved to a evbppc target.

1.221 Wed Oct 17 19:56:15 GMT 2007 garbled branches: 1.221.2; 1.221.8;
Merge the ppcoea-renovation branch to HEAD.

This branch was a major cleanup and rototill of many of the various OEA
cpu based PPC ports that focused on sharing as much code as possible
between the various ports to eliminate near-identical copies of files in
every tree. Additionally there is a new PIC system that unifies the
interface to interrupt code for all different OEA ppc arches. The work
for this branch was done by a variety of people, too long to list here.

TODO:
bebox still needs work to complete the transition to -renovation.
ofppc still needs a bunch of work, which I will be looking at.
ev64260 still needs to be renovated
amigappc was not attempted.

NOTES:
pmppc was removed as an arch, and moved to a evbppc target.

1.221 Wed Oct 17 19:56:15 GMT 2007 garbled branches: 1.221.2; 1.221.8;
Merge the ppcoea-renovation branch to HEAD.

This branch was a major cleanup and rototill of many of the various OEA
cpu based PPC ports that focused on sharing as much code as possible
between the various ports to eliminate near-identical copies of files in
every tree. Additionally there is a new PIC system that unifies the
interface to interrupt code for all different OEA ppc arches. The work
for this branch was done by a variety of people, too long to list here.

TODO:
bebox still needs work to complete the transition to -renovation.
ofppc still needs a bunch of work, which I will be looking at.
ev64260 still needs to be renovated
amigappc was not attempted.

NOTES:
pmppc was removed as an arch, and moved to a evbppc target.

/src/share/mk/
H A Dbsd.prog.mk1.221 Sun Jul 29 17:06:02 GMT 2007 joerg branches: 1.221.4; 1.221.6;
Add build glue for libarchive and update the various sets.

1.221 Sun Jul 29 17:06:02 GMT 2007 joerg branches: 1.221.4; 1.221.6;
Add build glue for libarchive and update the various sets.

1.221 Sun Jul 29 17:06:02 GMT 2007 joerg branches: 1.221.4; 1.221.6;
Add build glue for libarchive and update the various sets.

/src/sys/dev/scsipi/
H A Dst.c1.221 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.221.2; 1.221.4;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.221 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.221.2; 1.221.4;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.221 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.221.2; 1.221.4;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

/src/sys/arch/mac68k/conf/
H A DGENERIC1.221 Sat Aug 08 06:36:25 GMT 2015 maxv branches: 1.221.10;
Remove KMEMSTATS.

1.221 Sat Aug 08 06:36:25 GMT 2015 maxv branches: 1.221.10;
Remove KMEMSTATS.

/src/usr.sbin/
H A DMakefile1.221 Fri Sep 29 19:03:11 GMT 2006 macallan branches: 1.221.2;
Add gimpy's OF device tree dumping tool.
Tested on macppc and sparc64

1.221 Fri Sep 29 19:03:11 GMT 2006 macallan branches: 1.221.2;
Add gimpy's OF device tree dumping tool.
Tested on macppc and sparc64

/src/sys/dev/pci/
H A Dif_bgereg.h1.50 Thu Apr 16 01:38:34 GMT 2009 msaitoh Take some code from FreeBSD and OpenBSD:

Fix some bugs that the driver unable to detect link loss (OpenBSD 1.135,
FreeBSD 1.102)

bge_tick(): fix some extra input error (OpenBSD 1.221 FreeBSD 1.212)

Acknowledge link change interrupts by setting the 'link changed' bit
in the status register (used to have no effect). FreeBSD 1.44 (OpenBSD 1.21)

Add some fiber support (OpenBSD 1.220)

Set BGE_MISCCFG_KEEP_GPHY_POWER as {Open,Free}BSD and linux.

Add special case code to fix a problem with the BCM5704 in TBI mode
(FreeBSD rev. 1.71, OpenBSD rev. 1.35)

Force an interrupt in bge_ifmedia_upd (FreeBSD rev. 1.205, OpenBSD rev.
1.242)

Add missing workaround for 5705 (FreeBSD rev. 1.44, OpenBSD rev. 1.21)

Add some known CHIPID entries.

/src/sys/ufs/ext2fs/
H A Dext2fs_vfsops.c1.221 Sun May 22 11:27:36 GMT 2022 andvar branches: 1.221.4;
fix various small typos, mainly in comments.

1.221 Sun May 22 11:27:36 GMT 2022 andvar branches: 1.221.4;
fix various small typos, mainly in comments.

/src/sys/ufs/ufs/
H A Dufs_vnops.c1.221 Sun May 25 13:46:16 GMT 2014 hannken branches: 1.221.2;
ufs_mknod: use vcache_get() to reload the new node.

1.221 Sun May 25 13:46:16 GMT 2014 hannken branches: 1.221.2;
ufs_mknod: use vcache_get() to reload the new node.

/src/sys/uvm/
H A Duvm_page.c1.221 Sun Jan 05 22:01:09 GMT 2020 ad branches: 1.221.2;
Page allocator:

The method for assigning pages to buckets in the non-NUMA case sucks. It
can defeat memory interleaving in the hardware, and not distribute pages
fairly by colour. To fix this and make things more deterministic, take the
physical PFN and colour into account.

Then when freeing pages, in the non-NUMA case don't change the page's bucket
either. Keeping the bucket number stable will also permit partitioning page
replacement state by CPU package / NUMA node.

1.221 Sun Jan 05 22:01:09 GMT 2020 ad branches: 1.221.2;
Page allocator:

The method for assigning pages to buckets in the non-NUMA case sucks. It
can defeat memory interleaving in the hardware, and not distribute pages
fairly by colour. To fix this and make things more deterministic, take the
physical PFN and colour into account.

Then when freeing pages, in the non-NUMA case don't change the page's bucket
either. Keeping the bucket number stable will also permit partitioning page
replacement state by CPU package / NUMA node.

Completed in 211 milliseconds

123456789