Searched hist:1.154 (Results 1 - 25 of 406) sorted by relevance

1234567891011>>

/src/sys/arch/x86/x86/
H A Dintr.c1.154 Fri Feb 19 05:34:37 GMT 2021 knakahara Fix x86's pci_intr_disestablish clean up routine. Pointed out by t-kusaba@IIJ, thanks.

Fix panic on x86 by the following code.

/src/sys/dev/pcmcia/
H A Dif_ne_pcmcia.c1.154 Sat Apr 05 21:31:23 GMT 2008 cegger branches: 1.154.2; 1.154.4; 1.154.6;
use aprint_*_dev and device_xname

1.154 Sat Apr 05 21:31:23 GMT 2008 cegger branches: 1.154.2; 1.154.4; 1.154.6;
use aprint_*_dev and device_xname

1.154 Sat Apr 05 21:31:23 GMT 2008 cegger branches: 1.154.2; 1.154.4; 1.154.6;
use aprint_*_dev and device_xname

1.154 Sat Apr 05 21:31:23 GMT 2008 cegger branches: 1.154.2; 1.154.4; 1.154.6;
use aprint_*_dev and device_xname

/src/sys/net/
H A Dif_gif.c1.154 Wed Oct 14 15:22:17 GMT 2020 roy branches: 1.154.6;
gif: Set the link state UP if we have a tunnel, otherwise DOWN.

1.154 Wed Oct 14 15:22:17 GMT 2020 roy branches: 1.154.6;
gif: Set the link state UP if we have a tunnel, otherwise DOWN.

/src/sys/dev/mii/
H A Dmiidevs_data.h1.154 Mon Aug 03 14:00:41 GMT 2020 uwe branches: 1.154.6;
mii_knowndevs[] is de facto const, define it as such.

1.154 Mon Aug 03 14:00:41 GMT 2020 uwe branches: 1.154.6;
mii_knowndevs[] is de facto const, define it as such.

H A Dmiidevs.h1.154 Wed Sep 04 08:57:05 GMT 2019 msaitoh Regen.

/src/sys/arch/amiga/conf/
H A DDRACO1.154 Tue Jan 24 00:19:39 GMT 2012 rkujawa branches: 1.154.2; 1.154.6; 1.154.8;
Add voodoofb support. Allows using 3Dfx Voodoo 3 in G-REX as a console.

1.154 Tue Jan 24 00:19:39 GMT 2012 rkujawa branches: 1.154.2; 1.154.6; 1.154.8;
Add voodoofb support. Allows using 3Dfx Voodoo 3 in G-REX as a console.

1.154 Tue Jan 24 00:19:39 GMT 2012 rkujawa branches: 1.154.2; 1.154.6; 1.154.8;
Add voodoofb support. Allows using 3Dfx Voodoo 3 in G-REX as a console.

1.154 Tue Jan 24 00:19:39 GMT 2012 rkujawa branches: 1.154.2; 1.154.6; 1.154.8;
Add voodoofb support. Allows using 3Dfx Voodoo 3 in G-REX as a console.

/src/sys/miscfs/kernfs/
H A Dkernfs_vnops.c1.154 Fri Jul 25 08:20:52 GMT 2014 dholland branches: 1.154.2; 1.154.4; 1.154.6; 1.154.10;
Add VOP_FALLOCATE and VOP_FDISCARD to every vnode ops table I can
find.

The filesystem ones all call genfs_eopnotsupp - right now I am only
implementing the plumbing and we can implement fallocate and/or
fdiscard for files later.

The device ones call spec_fallocate (which is also genfs_eopnotsupp)
and spec_fdiscard, which dispatches to the device-level op.

The fifo ones all call vn_fifo_bypass, which also ends up being
EOPNOTSUPP.

1.154 Fri Jul 25 08:20:52 GMT 2014 dholland branches: 1.154.2; 1.154.4; 1.154.6; 1.154.10;
Add VOP_FALLOCATE and VOP_FDISCARD to every vnode ops table I can
find.

The filesystem ones all call genfs_eopnotsupp - right now I am only
implementing the plumbing and we can implement fallocate and/or
fdiscard for files later.

The device ones call spec_fallocate (which is also genfs_eopnotsupp)
and spec_fdiscard, which dispatches to the device-level op.

The fifo ones all call vn_fifo_bypass, which also ends up being
EOPNOTSUPP.

1.154 Fri Jul 25 08:20:52 GMT 2014 dholland branches: 1.154.2; 1.154.4; 1.154.6; 1.154.10;
Add VOP_FALLOCATE and VOP_FDISCARD to every vnode ops table I can
find.

The filesystem ones all call genfs_eopnotsupp - right now I am only
implementing the plumbing and we can implement fallocate and/or
fdiscard for files later.

The device ones call spec_fallocate (which is also genfs_eopnotsupp)
and spec_fdiscard, which dispatches to the device-level op.

The fifo ones all call vn_fifo_bypass, which also ends up being
EOPNOTSUPP.

1.154 Fri Jul 25 08:20:52 GMT 2014 dholland branches: 1.154.2; 1.154.4; 1.154.6; 1.154.10;
Add VOP_FALLOCATE and VOP_FDISCARD to every vnode ops table I can
find.

The filesystem ones all call genfs_eopnotsupp - right now I am only
implementing the plumbing and we can implement fallocate and/or
fdiscard for files later.

The device ones call spec_fallocate (which is also genfs_eopnotsupp)
and spec_fdiscard, which dispatches to the device-level op.

The fifo ones all call vn_fifo_bypass, which also ends up being
EOPNOTSUPP.

1.154 Fri Jul 25 08:20:52 GMT 2014 dholland branches: 1.154.2; 1.154.4; 1.154.6; 1.154.10;
Add VOP_FALLOCATE and VOP_FDISCARD to every vnode ops table I can
find.

The filesystem ones all call genfs_eopnotsupp - right now I am only
implementing the plumbing and we can implement fallocate and/or
fdiscard for files later.

The device ones call spec_fallocate (which is also genfs_eopnotsupp)
and spec_fdiscard, which dispatches to the device-level op.

The fifo ones all call vn_fifo_bypass, which also ends up being
EOPNOTSUPP.

/src/sys/arch/sparc64/conf/
H A Dfiles.sparc641.154 Tue Dec 19 14:34:08 GMT 2017 nakayama branches: 1.154.2; 1.154.4;
files.ofw is now mandatory, so use its dependency.

1.154 Tue Dec 19 14:34:08 GMT 2017 nakayama branches: 1.154.2; 1.154.4;
files.ofw is now mandatory, so use its dependency.

1.154 Tue Dec 19 14:34:08 GMT 2017 nakayama branches: 1.154.2; 1.154.4;
files.ofw is now mandatory, so use its dependency.

/src/sys/arch/sun3/conf/
H A DGENERIC1.154 Mon Jan 03 06:07:44 GMT 2011 tsutsui branches: 1.154.2; 1.154.4;
Xref module(7) in comments.

1.154 Mon Jan 03 06:07:44 GMT 2011 tsutsui branches: 1.154.2; 1.154.4;
Xref module(7) in comments.

1.154 Mon Jan 03 06:07:44 GMT 2011 tsutsui branches: 1.154.2; 1.154.4;
Xref module(7) in comments.

/src/sbin/fdisk/
H A Dfdisk.c1.154 Mon Oct 02 22:02:05 GMT 2017 joerg branches: 1.154.2; 1.154.4;
Really don't include ioctl code for tools build.

1.154 Mon Oct 02 22:02:05 GMT 2017 joerg branches: 1.154.2; 1.154.4;
Really don't include ioctl code for tools build.

1.154 Mon Oct 02 22:02:05 GMT 2017 joerg branches: 1.154.2; 1.154.4;
Really don't include ioctl code for tools build.

/src/sbin/route/
H A Droute.c1.154 Mon Apr 04 07:37:07 GMT 2016 ozaki-r branches: 1.154.2; 1.154.4;
Separate nexthop caches from the routing table

By this change, nexthop caches (IP-MAC address pair) are not stored
in the routing table anymore. Instead nexthop caches are stored in
each network interface; we already have lltable/llentry data structure
for this purpose. This change also obsoletes the concept of cloning/cloned
routes. Cloned routes no longer exist while cloning routes still exist
with renamed to connected routes.

Noticeable changes are:
- Nexthop caches aren't listed in route show/netstat -r
- sysctl(NET_RT_DUMP) doesn't return them
- If RTF_LLDATA is specified, it returns nexthop caches
- Several definitions of routing flags and messages are removed
- RTF_CLONING, RTF_XRESOLVE, RTF_LLINFO, RTF_CLONED and RTM_RESOLVE
- RTF_CONNECTED is added
- It has the same value of RTF_CLONING for backward compatibility
- route's -xresolve, -[no]cloned and -llinfo options are removed
- -[no]cloning remains because it seems there are users
- -[no]connected is introduced and recommended
to be used instead of -[no]cloning
- route show/netstat -r drops some flags
- 'L' and 'c' are not seen anymore
- 'C' now indicates a connected route
- Gateway value of a route of an interface address is now not
a L2 address but "link#N" like a connected (cloning) route
- Proxy ARP: "arp -s ... pub" doesn't create a route

You can know details of behavior changes by seeing diffs under tests/.

Proposed on tech-net and tech-kern:
http://mail-index.netbsd.org/tech-net/2016/03/11/msg005701.html

1.154 Mon Apr 04 07:37:07 GMT 2016 ozaki-r branches: 1.154.2; 1.154.4;
Separate nexthop caches from the routing table

By this change, nexthop caches (IP-MAC address pair) are not stored
in the routing table anymore. Instead nexthop caches are stored in
each network interface; we already have lltable/llentry data structure
for this purpose. This change also obsoletes the concept of cloning/cloned
routes. Cloned routes no longer exist while cloning routes still exist
with renamed to connected routes.

Noticeable changes are:
- Nexthop caches aren't listed in route show/netstat -r
- sysctl(NET_RT_DUMP) doesn't return them
- If RTF_LLDATA is specified, it returns nexthop caches
- Several definitions of routing flags and messages are removed
- RTF_CLONING, RTF_XRESOLVE, RTF_LLINFO, RTF_CLONED and RTM_RESOLVE
- RTF_CONNECTED is added
- It has the same value of RTF_CLONING for backward compatibility
- route's -xresolve, -[no]cloned and -llinfo options are removed
- -[no]cloning remains because it seems there are users
- -[no]connected is introduced and recommended
to be used instead of -[no]cloning
- route show/netstat -r drops some flags
- 'L' and 'c' are not seen anymore
- 'C' now indicates a connected route
- Gateway value of a route of an interface address is now not
a L2 address but "link#N" like a connected (cloning) route
- Proxy ARP: "arp -s ... pub" doesn't create a route

You can know details of behavior changes by seeing diffs under tests/.

Proposed on tech-net and tech-kern:
http://mail-index.netbsd.org/tech-net/2016/03/11/msg005701.html

1.154 Mon Apr 04 07:37:07 GMT 2016 ozaki-r branches: 1.154.2; 1.154.4;
Separate nexthop caches from the routing table

By this change, nexthop caches (IP-MAC address pair) are not stored
in the routing table anymore. Instead nexthop caches are stored in
each network interface; we already have lltable/llentry data structure
for this purpose. This change also obsoletes the concept of cloning/cloned
routes. Cloned routes no longer exist while cloning routes still exist
with renamed to connected routes.

Noticeable changes are:
- Nexthop caches aren't listed in route show/netstat -r
- sysctl(NET_RT_DUMP) doesn't return them
- If RTF_LLDATA is specified, it returns nexthop caches
- Several definitions of routing flags and messages are removed
- RTF_CLONING, RTF_XRESOLVE, RTF_LLINFO, RTF_CLONED and RTM_RESOLVE
- RTF_CONNECTED is added
- It has the same value of RTF_CLONING for backward compatibility
- route's -xresolve, -[no]cloned and -llinfo options are removed
- -[no]cloning remains because it seems there are users
- -[no]connected is introduced and recommended
to be used instead of -[no]cloning
- route show/netstat -r drops some flags
- 'L' and 'c' are not seen anymore
- 'C' now indicates a connected route
- Gateway value of a route of an interface address is now not
a L2 address but "link#N" like a connected (cloning) route
- Proxy ARP: "arp -s ... pub" doesn't create a route

You can know details of behavior changes by seeing diffs under tests/.

Proposed on tech-net and tech-kern:
http://mail-index.netbsd.org/tech-net/2016/03/11/msg005701.html

/src/sys/arch/mvme68k/mvme68k/
H A Dmachdep.c1.154 Tue May 31 03:25:46 GMT 2016 dholland branches: 1.154.2; 1.154.8; 1.154.18;
PR 50792 David Binderman: make sure we don't divide by zero.

The loop that picks delay_divisor might conceivably reject all values,
particularly if the hardware is sulking for some reason; in that case
it'll be left zero. Use 1 instead of 0 so we don't then crash.

1.154 Tue May 31 03:25:46 GMT 2016 dholland branches: 1.154.2; 1.154.8; 1.154.18;
PR 50792 David Binderman: make sure we don't divide by zero.

The loop that picks delay_divisor might conceivably reject all values,
particularly if the hardware is sulking for some reason; in that case
it'll be left zero. Use 1 instead of 0 so we don't then crash.

1.154 Tue May 31 03:25:46 GMT 2016 dholland branches: 1.154.2; 1.154.8; 1.154.18;
PR 50792 David Binderman: make sure we don't divide by zero.

The loop that picks delay_divisor might conceivably reject all values,
particularly if the hardware is sulking for some reason; in that case
it'll be left zero. Use 1 instead of 0 so we don't then crash.

1.154 Tue May 31 03:25:46 GMT 2016 dholland branches: 1.154.2; 1.154.8; 1.154.18;
PR 50792 David Binderman: make sure we don't divide by zero.

The loop that picks delay_divisor might conceivably reject all values,
particularly if the hardware is sulking for some reason; in that case
it'll be left zero. Use 1 instead of 0 so we don't then crash.

/src/lib/libc/stdlib/
H A Djemalloc.c1.22 Sat Feb 26 23:27:49 GMT 2011 njoly Switch from floating point to fixed point integer for run sizes maths.
From FreeBSD (part of revision 1.154).

/src/sys/rump/librump/rumpkern/
H A Drump_syscalls.c1.154 Fri Aug 14 00:55:03 GMT 2020 riastradh branches: 1.154.2;
regen

1.154 Fri Aug 14 00:55:03 GMT 2020 riastradh branches: 1.154.2;
regen

/src/sys/miscfs/procfs/
H A Dprocfs_vnops.c1.154 Fri Mar 09 14:11:23 GMT 2007 ad branches: 1.154.2; 1.154.4;
- Make the proclist_lock a mutex. The write:read ratio is unfavourable,
and mutexes are cheaper use than RW locks.
- LOCK_ASSERT -> KASSERT in some places.
- Hold proclist_lock/kernel_lock longer in a couple of places.

1.154 Fri Mar 09 14:11:23 GMT 2007 ad branches: 1.154.2; 1.154.4;
- Make the proclist_lock a mutex. The write:read ratio is unfavourable,
and mutexes are cheaper use than RW locks.
- LOCK_ASSERT -> KASSERT in some places.
- Hold proclist_lock/kernel_lock longer in a couple of places.

1.154 Fri Mar 09 14:11:23 GMT 2007 ad branches: 1.154.2; 1.154.4;
- Make the proclist_lock a mutex. The write:read ratio is unfavourable,
and mutexes are cheaper use than RW locks.
- LOCK_ASSERT -> KASSERT in some places.
- Hold proclist_lock/kernel_lock longer in a couple of places.

/src/sys/arch/pmax/conf/
H A DGENERIC1.154 Sun Nov 04 14:34:25 GMT 2007 xtraeme branches: 1.154.2; 1.154.8;
Remove System V semaphores and share memory options to set the limits:
SEMMNI, SEMMNS, SEMUME and SHMMAXPGS.

They can be tweaked via sysctl now. Ports that were setting values on
them weren't touched, I only removed the ones that were commented out.

1.154 Sun Nov 04 14:34:25 GMT 2007 xtraeme branches: 1.154.2; 1.154.8;
Remove System V semaphores and share memory options to set the limits:
SEMMNI, SEMMNS, SEMUME and SHMMAXPGS.

They can be tweaked via sysctl now. Ports that were setting values on
them weren't touched, I only removed the ones that were commented out.

1.154 Sun Nov 04 14:34:25 GMT 2007 xtraeme branches: 1.154.2; 1.154.8;
Remove System V semaphores and share memory options to set the limits:
SEMMNI, SEMMNS, SEMUME and SHMMAXPGS.

They can be tweaked via sysctl now. Ports that were setting values on
them weren't touched, I only removed the ones that were commented out.

/src/sys/dev/ic/
H A Dtulip.c1.154 Fri Oct 19 00:00:03 GMT 2007 ad branches: 1.154.2; 1.154.8;
machine/{bus,cpu,intr}.h -> sys/{bus,cpu,intr}.h

1.154 Fri Oct 19 00:00:03 GMT 2007 ad branches: 1.154.2; 1.154.8;
machine/{bus,cpu,intr}.h -> sys/{bus,cpu,intr}.h

1.154 Fri Oct 19 00:00:03 GMT 2007 ad branches: 1.154.2; 1.154.8;
machine/{bus,cpu,intr}.h -> sys/{bus,cpu,intr}.h

H A Dncr53c9x.c1.154 Sat Apr 24 23:36:55 GMT 2021 thorpej branches: 1.154.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

1.154 Sat Apr 24 23:36:55 GMT 2021 thorpej branches: 1.154.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

/src/sys/arch/sun3/sun3/
H A Dpmap.c1.154 Fri May 18 10:18:25 GMT 2007 tsutsui branches: 1.154.10;
Adapt sun68k ports to yamt-idlelwp.
Tested on TME (sun2 and sun3) and 3/80 (sun3x).

1.154 Fri May 18 10:18:25 GMT 2007 tsutsui branches: 1.154.10;
Adapt sun68k ports to yamt-idlelwp.
Tested on TME (sun2 and sun3) and 3/80 (sun3x).

/src/sys/arch/powerpc/powerpc/
H A Dtrap.c1.154 Fri Jun 15 22:07:14 GMT 2018 uwe branches: 1.154.2;
In mtmsr emulation ignore PSL_VEC we set in mfmsr emulation just
above, as it freaks out PSL_USEROK_P(). This is also congruent with
how we handle PSL_FP.

PR port-macppc/53360

1.154 Fri Jun 15 22:07:14 GMT 2018 uwe branches: 1.154.2;
In mtmsr emulation ignore PSL_VEC we set in mfmsr emulation just
above, as it freaks out PSL_USEROK_P(). This is also congruent with
how we handle PSL_FP.

PR port-macppc/53360

/src/sys/arch/sparc/conf/
H A Dfiles.sparc1.154 Tue Apr 16 06:57:05 GMT 2013 jdc branches: 1.154.12;
Add PCI fixup for MicroSPARC-IIep.
Unconfigured PCI-PCI bridges and devices behind them are configured.

1.154 Tue Apr 16 06:57:05 GMT 2013 jdc branches: 1.154.12;
Add PCI fixup for MicroSPARC-IIep.
Unconfigured PCI-PCI bridges and devices behind them are configured.

/src/sys/arch/sparc/dev/
H A Dfd.c1.154 Fri Jul 25 08:10:34 GMT 2014 dholland branches: 1.154.2;
Add d_discard to all struct cdevsw instances I could find.

All have been set to "nodiscard"; some should get a real implementation.

1.154 Fri Jul 25 08:10:34 GMT 2014 dholland branches: 1.154.2;
Add d_discard to all struct cdevsw instances I could find.

All have been set to "nodiscard"; some should get a real implementation.

/src/sys/arch/i386/conf/
H A DMakefile.i3861.154 Sun Dec 09 20:27:46 GMT 2007 jmcneill branches: 1.154.2;
Merge jmcneill-pm branch.
1.154 Sun Dec 09 20:27:46 GMT 2007 jmcneill branches: 1.154.2;
Merge jmcneill-pm branch.
/src/sys/dev/pci/
H A Dauich.c1.154 Thu Apr 18 13:01:38 GMT 2019 isaki branches: 1.154.2;
White space and indent fix.

1.154 Thu Apr 18 13:01:38 GMT 2019 isaki branches: 1.154.2;
White space and indent fix.

/src/sys/netinet/
H A Dip_mroute.c1.154 Fri Feb 09 08:03:33 GMT 2018 maxv branches: 1.154.2;
Style (realign everything correctly), and fix a typo.

1.154 Fri Feb 09 08:03:33 GMT 2018 maxv branches: 1.154.2;
Style (realign everything correctly), and fix a typo.

Completed in 171 milliseconds

1234567891011>>