Searched hist:1.124 (Results 1 - 25 of 620) sorted by relevance

1234567891011>>

/src/tests/usr.bin/xlint/lint1/
H A Dmsg_067.c1.4 Tue Jul 13 22:01:34 GMT 2021 rillig lint: fix wording of message for incomplete struct (2021-07-04)

A struct member is not an argument. In err.c 1.124 from 2021-07-04, the
wording had been changed, without noticing that the message was used
twice: once for an argument, once for a struct member.

H A Dmsg_031.c1.6 Tue Jul 13 22:01:34 GMT 2021 rillig lint: fix wording of message for incomplete struct (2021-07-04)

A struct member is not an argument. In err.c 1.124 from 2021-07-04, the
wording had been changed, without noticing that the message was used
twice: once for an argument, once for a struct member.

/src/sys/arch/hpcmips/hpcmips/
H A Dmachdep.c1.124 Mon Nov 06 03:47:46 GMT 2017 christos branches: 1.124.2; 1.124.4;
Cleanup and clarify the ELFSIZE mess:

We now have 2 variables automatically set in elf_machdep.h:

ARCH_ELFSIZE: the size for userland binaries
KERN_ELFSIZE: the size for the kernel binaries

DB_ELFSIZE has been deleted and KERN_ELFSIZE should have always the
same values DB_ELFSIZE used to have.

In sys/exec_elf.h, if ELFSIZE is not set, it is set to KERN_ELFSIZE
for the kernel and ARCH_ELFSIZE for userland. These defaults should
eliminate the need for most manual ELFSIZE setting.
1.124 Mon Nov 06 03:47:46 GMT 2017 christos branches: 1.124.2; 1.124.4;
Cleanup and clarify the ELFSIZE mess:

We now have 2 variables automatically set in elf_machdep.h:

ARCH_ELFSIZE: the size for userland binaries
KERN_ELFSIZE: the size for the kernel binaries

DB_ELFSIZE has been deleted and KERN_ELFSIZE should have always the
same values DB_ELFSIZE used to have.

In sys/exec_elf.h, if ELFSIZE is not set, it is set to KERN_ELFSIZE
for the kernel and ARCH_ELFSIZE for userland. These defaults should
eliminate the need for most manual ELFSIZE setting.
1.124 Mon Nov 06 03:47:46 GMT 2017 christos branches: 1.124.2; 1.124.4;
Cleanup and clarify the ELFSIZE mess:

We now have 2 variables automatically set in elf_machdep.h:

ARCH_ELFSIZE: the size for userland binaries
KERN_ELFSIZE: the size for the kernel binaries

DB_ELFSIZE has been deleted and KERN_ELFSIZE should have always the
same values DB_ELFSIZE used to have.

In sys/exec_elf.h, if ELFSIZE is not set, it is set to KERN_ELFSIZE
for the kernel and ARCH_ELFSIZE for userland. These defaults should
eliminate the need for most manual ELFSIZE setting.
/src/sys/arch/amiga/conf/
H A DDRACO1.174 Sat Jul 05 09:55:42 GMT 2014 tsutsui Regen to reflect GENERIC.in rev 1.121-1.124:

rev 1.121:
> dd preliminary support for the Individual Computers ACA500 in the form of acahf
> driver. If ACA500 is equipped with supported accelerator with MMU, it allows
> running NetBSD on an Amiga 500.
>
> Since ACA is not autoconf-aware, and the probe procedure does not exist yet, the
> driver is activated with the ACA500_SUPPORT kernel option. The acahf driver
> is commented out in the GENERIC kernel for now (at least until it stops being
> very experimental and hackish).
>
> When it comes to ACA-specific hardware, for now the boot CF slot works. Support for everything else is incoming...

rev 1.122:
> Changes to ACA500 support:
> - Add support for second (aux) CF slot.
> - Rework wdc attachment to be more sane.
> - Add support for clockport on ACA500.
> - Fix style where appropriate.

rev 1.123:
> Implement the probe procedure for ACA500. Now the user just needs acafh0
> compiled in his kernel and it all should(tm) work.
>
> Due to lack of obio in amiga port, the probe is called directly from mbattach().
> This is going to change with the introduction of obio for all non-autoconfig
> expansions.

rev 1.124:
> Disable X-Surf devices for DRACO's configuration.
>
> - ne at xsh requires ax88190 and ax88190 requires mii(4),
> but all mii devices are declared only inside AMIGA_CONFIGURATION
> - X-Surf also add wdc(4) but all children devices like atabus and
> atapibus are declared only for AMIGA_CONFIGURATION
>
> XXX: DRACO kernel is not built during build.sh release.

1.174 Sat Jul 05 09:55:42 GMT 2014 tsutsui Regen to reflect GENERIC.in rev 1.121-1.124:

rev 1.121:
> dd preliminary support for the Individual Computers ACA500 in the form of acahf
> driver. If ACA500 is equipped with supported accelerator with MMU, it allows
> running NetBSD on an Amiga 500.
>
> Since ACA is not autoconf-aware, and the probe procedure does not exist yet, the
> driver is activated with the ACA500_SUPPORT kernel option. The acahf driver
> is commented out in the GENERIC kernel for now (at least until it stops being
> very experimental and hackish).
>
> When it comes to ACA-specific hardware, for now the boot CF slot works. Support for everything else is incoming...

rev 1.122:
> Changes to ACA500 support:
> - Add support for second (aux) CF slot.
> - Rework wdc attachment to be more sane.
> - Add support for clockport on ACA500.
> - Fix style where appropriate.

rev 1.123:
> Implement the probe procedure for ACA500. Now the user just needs acafh0
> compiled in his kernel and it all should(tm) work.
>
> Due to lack of obio in amiga port, the probe is called directly from mbattach().
> This is going to change with the introduction of obio for all non-autoconfig
> expansions.

rev 1.124:
> Disable X-Surf devices for DRACO's configuration.
>
> - ne at xsh requires ax88190 and ax88190 requires mii(4),
> but all mii devices are declared only inside AMIGA_CONFIGURATION
> - X-Surf also add wdc(4) but all children devices like atabus and
> atapibus are declared only for AMIGA_CONFIGURATION
>
> XXX: DRACO kernel is not built during build.sh release.

1.124 Mon Dec 31 15:31:47 GMT 2007 ad branches: 1.124.6; 1.124.10; 1.124.12; 1.124.16;
Remove systrace. Ok core@.

1.124 Mon Dec 31 15:31:47 GMT 2007 ad branches: 1.124.6; 1.124.10; 1.124.12; 1.124.16;
Remove systrace. Ok core@.

1.124 Mon Dec 31 15:31:47 GMT 2007 ad branches: 1.124.6; 1.124.10; 1.124.12; 1.124.16;
Remove systrace. Ok core@.

1.124 Mon Dec 31 15:31:47 GMT 2007 ad branches: 1.124.6; 1.124.10; 1.124.12; 1.124.16;
Remove systrace. Ok core@.

1.124 Mon Dec 31 15:31:47 GMT 2007 ad branches: 1.124.6; 1.124.10; 1.124.12; 1.124.16;
Remove systrace. Ok core@.

H A DINSTALL1.124 Sat Jul 05 09:55:42 GMT 2014 tsutsui Regen to reflect GENERIC.in rev 1.121-1.124:

rev 1.121:
> dd preliminary support for the Individual Computers ACA500 in the form of acahf
> driver. If ACA500 is equipped with supported accelerator with MMU, it allows
> running NetBSD on an Amiga 500.
>
> Since ACA is not autoconf-aware, and the probe procedure does not exist yet, the
> driver is activated with the ACA500_SUPPORT kernel option. The acahf driver
> is commented out in the GENERIC kernel for now (at least until it stops being
> very experimental and hackish).
>
> When it comes to ACA-specific hardware, for now the boot CF slot works. Support for everything else is incoming...

rev 1.122:
> Changes to ACA500 support:
> - Add support for second (aux) CF slot.
> - Rework wdc attachment to be more sane.
> - Add support for clockport on ACA500.
> - Fix style where appropriate.

rev 1.123:
> Implement the probe procedure for ACA500. Now the user just needs acafh0
> compiled in his kernel and it all should(tm) work.
>
> Due to lack of obio in amiga port, the probe is called directly from mbattach().
> This is going to change with the introduction of obio for all non-autoconfig
> expansions.

rev 1.124:
> Disable X-Surf devices for DRACO's configuration.
>
> - ne at xsh requires ax88190 and ax88190 requires mii(4),
> but all mii devices are declared only inside AMIGA_CONFIGURATION
> - X-Surf also add wdc(4) but all children devices like atabus and
> atapibus are declared only for AMIGA_CONFIGURATION
>
> XXX: DRACO kernel is not built during build.sh release.

1.124 Sat Jul 05 09:55:42 GMT 2014 tsutsui Regen to reflect GENERIC.in rev 1.121-1.124:

rev 1.121:
> dd preliminary support for the Individual Computers ACA500 in the form of acahf
> driver. If ACA500 is equipped with supported accelerator with MMU, it allows
> running NetBSD on an Amiga 500.
>
> Since ACA is not autoconf-aware, and the probe procedure does not exist yet, the
> driver is activated with the ACA500_SUPPORT kernel option. The acahf driver
> is commented out in the GENERIC kernel for now (at least until it stops being
> very experimental and hackish).
>
> When it comes to ACA-specific hardware, for now the boot CF slot works. Support for everything else is incoming...

rev 1.122:
> Changes to ACA500 support:
> - Add support for second (aux) CF slot.
> - Rework wdc attachment to be more sane.
> - Add support for clockport on ACA500.
> - Fix style where appropriate.

rev 1.123:
> Implement the probe procedure for ACA500. Now the user just needs acafh0
> compiled in his kernel and it all should(tm) work.
>
> Due to lack of obio in amiga port, the probe is called directly from mbattach().
> This is going to change with the introduction of obio for all non-autoconfig
> expansions.

rev 1.124:
> Disable X-Surf devices for DRACO's configuration.
>
> - ne at xsh requires ax88190 and ax88190 requires mii(4),
> but all mii devices are declared only inside AMIGA_CONFIGURATION
> - X-Surf also add wdc(4) but all children devices like atabus and
> atapibus are declared only for AMIGA_CONFIGURATION
>
> XXX: DRACO kernel is not built during build.sh release.

1.124 Sat Jul 05 09:55:42 GMT 2014 tsutsui Regen to reflect GENERIC.in rev 1.121-1.124:

rev 1.121:
> dd preliminary support for the Individual Computers ACA500 in the form of acahf
> driver. If ACA500 is equipped with supported accelerator with MMU, it allows
> running NetBSD on an Amiga 500.
>
> Since ACA is not autoconf-aware, and the probe procedure does not exist yet, the
> driver is activated with the ACA500_SUPPORT kernel option. The acahf driver
> is commented out in the GENERIC kernel for now (at least until it stops being
> very experimental and hackish).
>
> When it comes to ACA-specific hardware, for now the boot CF slot works. Support for everything else is incoming...

rev 1.122:
> Changes to ACA500 support:
> - Add support for second (aux) CF slot.
> - Rework wdc attachment to be more sane.
> - Add support for clockport on ACA500.
> - Fix style where appropriate.

rev 1.123:
> Implement the probe procedure for ACA500. Now the user just needs acafh0
> compiled in his kernel and it all should(tm) work.
>
> Due to lack of obio in amiga port, the probe is called directly from mbattach().
> This is going to change with the introduction of obio for all non-autoconfig
> expansions.

rev 1.124:
> Disable X-Surf devices for DRACO's configuration.
>
> - ne at xsh requires ax88190 and ax88190 requires mii(4),
> but all mii devices are declared only inside AMIGA_CONFIGURATION
> - X-Surf also add wdc(4) but all children devices like atabus and
> atapibus are declared only for AMIGA_CONFIGURATION
>
> XXX: DRACO kernel is not built during build.sh release.

/src/sys/compat/linux32/common/
H A Dlinux32_dirent.c1.10 Wed Mar 03 08:20:38 GMT 2010 he branches: 1.10.2;
When implementing "read directory", when there are too many empty entries
in a row, and we need to try to read the next block, and have passed a
non-NULL cookie pointer to VOP_READDIR, ensure that we free the cookie
buffer before re-doing VOP_READDIR, so that we don't leak memory.
This fix is similar to nfs_serv.c revisions 1.115 + 1.124.

This should fix the long-standing problem observed by e.g. using Linux-
emulated programs to take backup of servers, which is one of the problems
which were reported in PR#42661.

Thanks to pooka@ for the hints for traversing the VOP* layer.

/src/sys/kern/
H A Dexec_elf32.c1.124 Sun Jun 24 20:35:37 GMT 2007 christos branches: 1.124.2; 1.124.8; 1.124.10; 1.124.14;
Use an elf note to handle pax arguments. This is a temporary solution to
avoid wasting OS flag bits. In the future we'll probably use fileassoc to
achieve this (once there is a way to make fileassoc persistent) or in the
shorter term libelf, so that we can add and remove the note on demand instead
of burning bits on each binary. Of course since this is a tool, this means
that we'll need to think about how to handle libelf...

1.124 Sun Jun 24 20:35:37 GMT 2007 christos branches: 1.124.2; 1.124.8; 1.124.10; 1.124.14;
Use an elf note to handle pax arguments. This is a temporary solution to
avoid wasting OS flag bits. In the future we'll probably use fileassoc to
achieve this (once there is a way to make fileassoc persistent) or in the
shorter term libelf, so that we can add and remove the note on demand instead
of burning bits on each binary. Of course since this is a tool, this means
that we'll need to think about how to handle libelf...

1.124 Sun Jun 24 20:35:37 GMT 2007 christos branches: 1.124.2; 1.124.8; 1.124.10; 1.124.14;
Use an elf note to handle pax arguments. This is a temporary solution to
avoid wasting OS flag bits. In the future we'll probably use fileassoc to
achieve this (once there is a way to make fileassoc persistent) or in the
shorter term libelf, so that we can add and remove the note on demand instead
of burning bits on each binary. Of course since this is a tool, this means
that we'll need to think about how to handle libelf...

1.124 Sun Jun 24 20:35:37 GMT 2007 christos branches: 1.124.2; 1.124.8; 1.124.10; 1.124.14;
Use an elf note to handle pax arguments. This is a temporary solution to
avoid wasting OS flag bits. In the future we'll probably use fileassoc to
achieve this (once there is a way to make fileassoc persistent) or in the
shorter term libelf, so that we can add and remove the note on demand instead
of burning bits on each binary. Of course since this is a tool, this means
that we'll need to think about how to handle libelf...

1.124 Sun Jun 24 20:35:37 GMT 2007 christos branches: 1.124.2; 1.124.8; 1.124.10; 1.124.14;
Use an elf note to handle pax arguments. This is a temporary solution to
avoid wasting OS flag bits. In the future we'll probably use fileassoc to
achieve this (once there is a way to make fileassoc persistent) or in the
shorter term libelf, so that we can add and remove the note on demand instead
of burning bits on each binary. Of course since this is a tool, this means
that we'll need to think about how to handle libelf...

H A Dsys_generic.c1.124 Thu Aug 13 08:57:43 GMT 2009 haad branches: 1.124.4; 1.124.6;
Allow undescribed, direct ioctls as used by Unix. This capability was removed in BSD, presumably because nothing used it any more.
Third party system software written for Unix (like ZFS) requires this to work without significant modifications.

Ok supremeleader@

1.124 Thu Aug 13 08:57:43 GMT 2009 haad branches: 1.124.4; 1.124.6;
Allow undescribed, direct ioctls as used by Unix. This capability was removed in BSD, presumably because nothing used it any more.
Third party system software written for Unix (like ZFS) requires this to work without significant modifications.

Ok supremeleader@

1.124 Thu Aug 13 08:57:43 GMT 2009 haad branches: 1.124.4; 1.124.6;
Allow undescribed, direct ioctls as used by Unix. This capability was removed in BSD, presumably because nothing used it any more.
Third party system software written for Unix (like ZFS) requires this to work without significant modifications.

Ok supremeleader@

/src/sys/dev/usb/
H A Dumass.c1.124 Tue Mar 13 13:51:56 GMT 2007 drochner branches: 1.124.10; 1.124.12; 1.124.18; 1.124.20; 1.124.22;
Introduce different autoconf interface attributes for USB drivers
matching (and handling) a whole device and those which match an
interface only. This will allow to enforce some rules, eg that
the former don't use interface information for matching or that the
latter don't modify global device state.
The previous way left too much freedom do the drivers which led to
inconsistencies and abuse.
For now, I've not changed locators and submatch rules, this will
happen later.
There should not be any change in behaviour, except in the case of
some drivers which did behave inconsistently:
if_atu, if_axe, uep: matched the configured device in the interface
stage, but did configuration again. I've converted them to match
in the device stage.
ustir, utoppy: matched in the interface stage, but only against
vendor/device information, and used any configuration/interface
without checking. Changed to match in device stage, and added
some simple code to configure and use the first interface.
If you have one of those devices, please test!

1.124 Tue Mar 13 13:51:56 GMT 2007 drochner branches: 1.124.10; 1.124.12; 1.124.18; 1.124.20; 1.124.22;
Introduce different autoconf interface attributes for USB drivers
matching (and handling) a whole device and those which match an
interface only. This will allow to enforce some rules, eg that
the former don't use interface information for matching or that the
latter don't modify global device state.
The previous way left too much freedom do the drivers which led to
inconsistencies and abuse.
For now, I've not changed locators and submatch rules, this will
happen later.
There should not be any change in behaviour, except in the case of
some drivers which did behave inconsistently:
if_atu, if_axe, uep: matched the configured device in the interface
stage, but did configuration again. I've converted them to match
in the device stage.
ustir, utoppy: matched in the interface stage, but only against
vendor/device information, and used any configuration/interface
without checking. Changed to match in device stage, and added
some simple code to configure and use the first interface.
If you have one of those devices, please test!

1.124 Tue Mar 13 13:51:56 GMT 2007 drochner branches: 1.124.10; 1.124.12; 1.124.18; 1.124.20; 1.124.22;
Introduce different autoconf interface attributes for USB drivers
matching (and handling) a whole device and those which match an
interface only. This will allow to enforce some rules, eg that
the former don't use interface information for matching or that the
latter don't modify global device state.
The previous way left too much freedom do the drivers which led to
inconsistencies and abuse.
For now, I've not changed locators and submatch rules, this will
happen later.
There should not be any change in behaviour, except in the case of
some drivers which did behave inconsistently:
if_atu, if_axe, uep: matched the configured device in the interface
stage, but did configuration again. I've converted them to match
in the device stage.
ustir, utoppy: matched in the interface stage, but only against
vendor/device information, and used any configuration/interface
without checking. Changed to match in device stage, and added
some simple code to configure and use the first interface.
If you have one of those devices, please test!

1.124 Tue Mar 13 13:51:56 GMT 2007 drochner branches: 1.124.10; 1.124.12; 1.124.18; 1.124.20; 1.124.22;
Introduce different autoconf interface attributes for USB drivers
matching (and handling) a whole device and those which match an
interface only. This will allow to enforce some rules, eg that
the former don't use interface information for matching or that the
latter don't modify global device state.
The previous way left too much freedom do the drivers which led to
inconsistencies and abuse.
For now, I've not changed locators and submatch rules, this will
happen later.
There should not be any change in behaviour, except in the case of
some drivers which did behave inconsistently:
if_atu, if_axe, uep: matched the configured device in the interface
stage, but did configuration again. I've converted them to match
in the device stage.
ustir, utoppy: matched in the interface stage, but only against
vendor/device information, and used any configuration/interface
without checking. Changed to match in device stage, and added
some simple code to configure and use the first interface.
If you have one of those devices, please test!

1.124 Tue Mar 13 13:51:56 GMT 2007 drochner branches: 1.124.10; 1.124.12; 1.124.18; 1.124.20; 1.124.22;
Introduce different autoconf interface attributes for USB drivers
matching (and handling) a whole device and those which match an
interface only. This will allow to enforce some rules, eg that
the former don't use interface information for matching or that the
latter don't modify global device state.
The previous way left too much freedom do the drivers which led to
inconsistencies and abuse.
For now, I've not changed locators and submatch rules, this will
happen later.
There should not be any change in behaviour, except in the case of
some drivers which did behave inconsistently:
if_atu, if_axe, uep: matched the configured device in the interface
stage, but did configuration again. I've converted them to match
in the device stage.
ustir, utoppy: matched in the interface stage, but only against
vendor/device information, and used any configuration/interface
without checking. Changed to match in device stage, and added
some simple code to configure and use the first interface.
If you have one of those devices, please test!

1.124 Tue Mar 13 13:51:56 GMT 2007 drochner branches: 1.124.10; 1.124.12; 1.124.18; 1.124.20; 1.124.22;
Introduce different autoconf interface attributes for USB drivers
matching (and handling) a whole device and those which match an
interface only. This will allow to enforce some rules, eg that
the former don't use interface information for matching or that the
latter don't modify global device state.
The previous way left too much freedom do the drivers which led to
inconsistencies and abuse.
For now, I've not changed locators and submatch rules, this will
happen later.
There should not be any change in behaviour, except in the case of
some drivers which did behave inconsistently:
if_atu, if_axe, uep: matched the configured device in the interface
stage, but did configuration again. I've converted them to match
in the device stage.
ustir, utoppy: matched in the interface stage, but only against
vendor/device information, and used any configuration/interface
without checking. Changed to match in device stage, and added
some simple code to configure and use the first interface.
If you have one of those devices, please test!

/src/sys/net/
H A Dif_gif.c1.124 Wed Dec 14 11:19:15 GMT 2016 knakahara branches: 1.124.2;
fix race of gif_softc->gif_ro when we send multiple flows over gif on NET_MPSAFE enabled kernel.

make gif_softc->gif_ro percpu as well as ipforward_rt to resolve this race.
and add future TODO comment for etherip(4).

1.124 Wed Dec 14 11:19:15 GMT 2016 knakahara branches: 1.124.2;
fix race of gif_softc->gif_ro when we send multiple flows over gif on NET_MPSAFE enabled kernel.

make gif_softc->gif_ro percpu as well as ipforward_rt to resolve this race.
and add future TODO comment for etherip(4).

/src/distrib/notes/i386/
H A Dhardware1.124 Sat Sep 27 23:15:21 GMT 2008 tsutsui branches: 1.124.2;
Use `\*[Am]' rather than `\*&' for ampersand.

1.124 Sat Sep 27 23:15:21 GMT 2008 tsutsui branches: 1.124.2;
Use `\*[Am]' rather than `\*&' for ampersand.

/src/share/man/man4/
H A Dpci.41.124 Wed Mar 06 22:18:56 GMT 2024 cnst branches: 1.124.2;
wwanc(4): amend Nd; Xr from pci(4)

1.124 Wed Mar 06 22:18:56 GMT 2024 cnst branches: 1.124.2;
wwanc(4): amend Nd; Xr from pci(4)

/src/sys/uvm/
H A Duvm_io.c1.29 Mon Sep 21 18:41:59 GMT 2020 chs the previous fix for PR 55366 in uvm_amap.c 1.124 was incomplete:
- amap_adjref_anons() must also ignore AMAP_REFALL when updating
the ppref, not just when deciding whether or not to initialize ppref.
- UVM_EXTRACT_QREF relies on AMAP_REFALL to work properly,
and since we can't use AMAP_REFALL then we can't use QREF either.

/src/sys/sys/
H A Dexec.h1.124 Wed Jul 02 17:28:57 GMT 2008 ad branches: 1.124.2; 1.124.4; 1.124.10;
Replce exec_map with a pool. Proposed on tech-kern@, reviewed by chs@.

1.124 Wed Jul 02 17:28:57 GMT 2008 ad branches: 1.124.2; 1.124.4; 1.124.10;
Replce exec_map with a pool. Proposed on tech-kern@, reviewed by chs@.

1.124 Wed Jul 02 17:28:57 GMT 2008 ad branches: 1.124.2; 1.124.4; 1.124.10;
Replce exec_map with a pool. Proposed on tech-kern@, reviewed by chs@.

1.124 Wed Jul 02 17:28:57 GMT 2008 ad branches: 1.124.2; 1.124.4; 1.124.10;
Replce exec_map with a pool. Proposed on tech-kern@, reviewed by chs@.

H A Ddisklabel.h1.124 Mon Mar 30 09:32:46 GMT 2020 wiz branches: 1.124.8; 1.124.10;
Match indentation of previous entries.

1.124 Mon Mar 30 09:32:46 GMT 2020 wiz branches: 1.124.8; 1.124.10;
Match indentation of previous entries.

1.124 Mon Mar 30 09:32:46 GMT 2020 wiz branches: 1.124.8; 1.124.10;
Match indentation of previous entries.

/src/sys/arch/mmeye/conf/
H A DGENERIC1.124 Thu Sep 14 07:58:42 GMT 2017 mrg branches: 1.124.2; 1.124.4;
clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

1.124 Thu Sep 14 07:58:42 GMT 2017 mrg branches: 1.124.2; 1.124.4;
clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

1.124 Thu Sep 14 07:58:42 GMT 2017 mrg branches: 1.124.2; 1.124.4;
clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

/src/sys/dev/isa/
H A Disa.c1.124 Sun Dec 11 00:22:02 GMT 2005 christos branches: 1.124.20; 1.124.22;
merge ktrace-lwp.

1.124 Sun Dec 11 00:22:02 GMT 2005 christos branches: 1.124.20; 1.124.22;
merge ktrace-lwp.

1.124 Sun Dec 11 00:22:02 GMT 2005 christos branches: 1.124.20; 1.124.22;
merge ktrace-lwp.

/src/sys/dev/ic/
H A Daic7xxx.c1.124 Sun Mar 04 06:01:48 GMT 2007 christos branches: 1.124.16; 1.124.22;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

1.124 Sun Mar 04 06:01:48 GMT 2007 christos branches: 1.124.16; 1.124.22;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

1.124 Sun Mar 04 06:01:48 GMT 2007 christos branches: 1.124.16; 1.124.22;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

/src/sys/dev/pci/
H A Dif_tlp_pci.c1.124 Thu Jul 07 06:55:41 GMT 2016 msaitoh branches: 1.124.16; 1.124.18;
KNF. Remove extra spaces. No functional change.

1.124 Thu Jul 07 06:55:41 GMT 2016 msaitoh branches: 1.124.16; 1.124.18;
KNF. Remove extra spaces. No functional change.

1.124 Thu Jul 07 06:55:41 GMT 2016 msaitoh branches: 1.124.16; 1.124.18;
KNF. Remove extra spaces. No functional change.

/src/sys/dev/mii/
H A Dmiidevs1.124 Fri Aug 14 01:23:17 GMT 2015 knakahara branches: 1.124.2; 1.124.4;
Add Marvell 88E1512.

1.124 Fri Aug 14 01:23:17 GMT 2015 knakahara branches: 1.124.2; 1.124.4;
Add Marvell 88E1512.

1.124 Fri Aug 14 01:23:17 GMT 2015 knakahara branches: 1.124.2; 1.124.4;
Add Marvell 88E1512.

/src/sys/rump/
H A DMakefile.rump1.124 Sat Mar 03 22:46:30 GMT 2018 christos branches: 1.124.4; 1.124.10;
Disable NULL pointer check deletion like we do for the kernel in
src/sys/conf/Makefile.kern.inc. This is the same code we are compiling after
all and it has the same issues.

1.124 Sat Mar 03 22:46:30 GMT 2018 christos branches: 1.124.4; 1.124.10;
Disable NULL pointer check deletion like we do for the kernel in
src/sys/conf/Makefile.kern.inc. This is the same code we are compiling after
all and it has the same issues.

1.124 Sat Mar 03 22:46:30 GMT 2018 christos branches: 1.124.4; 1.124.10;
Disable NULL pointer check deletion like we do for the kernel in
src/sys/conf/Makefile.kern.inc. This is the same code we are compiling after
all and it has the same issues.

/src/sys/ufs/ffs/
H A Dffs_inode.c1.124 Sat Mar 18 05:26:40 GMT 2017 riastradh branches: 1.124.12; 1.124.14;
#if DIAGNOSTIC panic ---> KASSERT

1.124 Sat Mar 18 05:26:40 GMT 2017 riastradh branches: 1.124.12; 1.124.14;
#if DIAGNOSTIC panic ---> KASSERT

1.124 Sat Mar 18 05:26:40 GMT 2017 riastradh branches: 1.124.12; 1.124.14;
#if DIAGNOSTIC panic ---> KASSERT

/src/sys/arch/sparc64/dev/
H A Dpsycho.c1.124 Tue May 10 19:23:59 GMT 2016 palle branches: 1.124.2; 1.124.4;
sun4v: make device interrupts work. Introduce a new intrhand_alloc() function for allocation of interrupt handlers and adapt to this. Parts from OpenBSD. ok martin@

1.124 Tue May 10 19:23:59 GMT 2016 palle branches: 1.124.2; 1.124.4;
sun4v: make device interrupts work. Introduce a new intrhand_alloc() function for allocation of interrupt handlers and adapt to this. Parts from OpenBSD. ok martin@

1.124 Tue May 10 19:23:59 GMT 2016 palle branches: 1.124.2; 1.124.4;
sun4v: make device interrupts work. Introduce a new intrhand_alloc() function for allocation of interrupt handlers and adapt to this. Parts from OpenBSD. ok martin@

/src/sys/arch/sparc64/include/
H A Dcpu.h1.124 Tue Jan 16 08:23:17 GMT 2018 mrg branches: 1.124.2; 1.124.4;
implement cpuctl identify for sparc and sparc64.

sparc:
- move enum vactype and struct cacheinfo into cpu.h
- move the cache flags from cpuinfo.flags into CACHEINFO.c_flags
(this allows the new cache_printf_backend() to see them.)
remove unused CPUFLG_CACHEIOMMUTABLES and CPUFLG_CACHEDVMA.
- align xmpsg to 64 bytes
- move cache_print() into cache_print.h so it can be shared with
cpuctl. it only depends upon a working printf().
- if found, store the CPU node's "name" into cpu_longname. this
changes the default output to show the local CPU not the
generic CPU family. eg:
cpu0 at mainbus0: mid 8: Ross,RT625 @ 90 MHz, on-chip FPU
vs the generic "RT620/625" previously shown.
- for each CPU export these things:
- name
- fpuname
- mid
- cloc
- freq
- psr impl and version
- mmu impl, version, and number of contexts
- cacheinfo structure (which changed for the first time ever
with this commit.)

sparc64:
- add a minimal "cacheinfo" structure to export the i/d/e-cache
size and linesize.
- store %ver, cpu node "name" and cacheinfo in cpu_info.
- set cpu_info ver, name and cacheinfo in cpu_attach(), and
export them via sysctl, as well as CPU ID and clock freq

cpuctl:
- add identifycpu_bind() that returns false on !x86 as their
identify routines do not need to run on a particular CPU to
obtain its information, and use it to avoid trying to set
affinity when not needed.
- add sparc and sparc64 cpu identify support using the newly
exported values.

1.124 Tue Jan 16 08:23:17 GMT 2018 mrg branches: 1.124.2; 1.124.4;
implement cpuctl identify for sparc and sparc64.

sparc:
- move enum vactype and struct cacheinfo into cpu.h
- move the cache flags from cpuinfo.flags into CACHEINFO.c_flags
(this allows the new cache_printf_backend() to see them.)
remove unused CPUFLG_CACHEIOMMUTABLES and CPUFLG_CACHEDVMA.
- align xmpsg to 64 bytes
- move cache_print() into cache_print.h so it can be shared with
cpuctl. it only depends upon a working printf().
- if found, store the CPU node's "name" into cpu_longname. this
changes the default output to show the local CPU not the
generic CPU family. eg:
cpu0 at mainbus0: mid 8: Ross,RT625 @ 90 MHz, on-chip FPU
vs the generic "RT620/625" previously shown.
- for each CPU export these things:
- name
- fpuname
- mid
- cloc
- freq
- psr impl and version
- mmu impl, version, and number of contexts
- cacheinfo structure (which changed for the first time ever
with this commit.)

sparc64:
- add a minimal "cacheinfo" structure to export the i/d/e-cache
size and linesize.
- store %ver, cpu node "name" and cacheinfo in cpu_info.
- set cpu_info ver, name and cacheinfo in cpu_attach(), and
export them via sysctl, as well as CPU ID and clock freq

cpuctl:
- add identifycpu_bind() that returns false on !x86 as their
identify routines do not need to run on a particular CPU to
obtain its information, and use it to avoid trying to set
affinity when not needed.
- add sparc and sparc64 cpu identify support using the newly
exported values.

1.124 Tue Jan 16 08:23:17 GMT 2018 mrg branches: 1.124.2; 1.124.4;
implement cpuctl identify for sparc and sparc64.

sparc:
- move enum vactype and struct cacheinfo into cpu.h
- move the cache flags from cpuinfo.flags into CACHEINFO.c_flags
(this allows the new cache_printf_backend() to see them.)
remove unused CPUFLG_CACHEIOMMUTABLES and CPUFLG_CACHEDVMA.
- align xmpsg to 64 bytes
- move cache_print() into cache_print.h so it can be shared with
cpuctl. it only depends upon a working printf().
- if found, store the CPU node's "name" into cpu_longname. this
changes the default output to show the local CPU not the
generic CPU family. eg:
cpu0 at mainbus0: mid 8: Ross,RT625 @ 90 MHz, on-chip FPU
vs the generic "RT620/625" previously shown.
- for each CPU export these things:
- name
- fpuname
- mid
- cloc
- freq
- psr impl and version
- mmu impl, version, and number of contexts
- cacheinfo structure (which changed for the first time ever
with this commit.)

sparc64:
- add a minimal "cacheinfo" structure to export the i/d/e-cache
size and linesize.
- store %ver, cpu node "name" and cacheinfo in cpu_info.
- set cpu_info ver, name and cacheinfo in cpu_attach(), and
export them via sysctl, as well as CPU ID and clock freq

cpuctl:
- add identifycpu_bind() that returns false on !x86 as their
identify routines do not need to run on a particular CPU to
obtain its information, and use it to avoid trying to set
affinity when not needed.
- add sparc and sparc64 cpu identify support using the newly
exported values.

/src/sys/compat/sunos/
H A Dsunos_misc.c1.166 Wed Mar 03 08:20:39 GMT 2010 he When implementing "read directory", when there are too many empty entries
in a row, and we need to try to read the next block, and have passed a
non-NULL cookie pointer to VOP_READDIR, ensure that we free the cookie
buffer before re-doing VOP_READDIR, so that we don't leak memory.
This fix is similar to nfs_serv.c revisions 1.115 + 1.124.

This should fix the long-standing problem observed by e.g. using Linux-
emulated programs to take backup of servers, which is one of the problems
which were reported in PR#42661.

Thanks to pooka@ for the hints for traversing the VOP* layer.

1.124 Sun Jun 29 22:29:44 GMT 2003 fvdl branches: 1.124.2;
Back out the lwp/ktrace changes. They contained a lot of colateral damage,
and need to be examined and discussed more.

1.124 Sun Jun 29 22:29:44 GMT 2003 fvdl branches: 1.124.2;
Back out the lwp/ktrace changes. They contained a lot of colateral damage,
and need to be examined and discussed more.

Completed in 158 milliseconds

1234567891011>>