Searched hist:1.746 (Results 1 - 21 of 21) sorted by relevance

/src/sys/dev/pci/
H A Dif_wm.c1.746 Fri Jul 22 05:23:50 GMT 2022 msaitoh Add more statistics countes.

- Add many statics counters that the chip has.
- Attach event counters only if available.
H A Dpcidevs.h1.748 Sun Dec 11 20:01:48 GMT 2005 jonathan Regen after pcidevs rev 1.746, 1.747 (Add device IDs for LSI Megaraid,
and Intel IDs for software-compatible Intel RAID products).
1.746 Fri Dec 09 10:46:00 GMT 2005 xtraeme regen
H A Dpcidevs_data.h1.746 Sun Dec 11 20:01:49 GMT 2005 jonathan Regen after pcidevs rev 1.746, 1.747 (Add device IDs for LSI Megaraid,
and Intel IDs for software-compatible Intel RAID products).
1.746 Sun Dec 11 20:01:49 GMT 2005 jonathan Regen after pcidevs rev 1.746, 1.747 (Add device IDs for LSI Megaraid,
and Intel IDs for software-compatible Intel RAID products).
H A Dpcidevs1.746 Sun Dec 11 19:34:47 GMT 2005 jonathan Add pcidevs entries and support to amr(4) for newer LSI MegaRAID devices,
including the LSI MegaRAID SCSI 320-0x, 320-2x, 320-4x, 320-1E, 320-2E,
the LSI MegaRAID SATA 300-6x and 300-8x.

Tested on an LSI MegaRAID SATA 300-8x, which confirms private advice
that after PCI-IDs to our amr(4) driver, the newer LSI MegaRAID cards
will Just Work

The Linux megaraid2 driver accepts various Intel cards with the same
pci-device IDs as the LSI MegaRAID cards, treating them exaclty as the
above-listed LSI cards. Rework our amr(4) driver to also match and
attach those device-ID if seen with an Intel vendor-ID. Add the
Intel-vendor PCI decice-ids to pcidevs, so that PCI_VERBOSE will
correctly identify the Intel cards.

Update src/share/man/man4/amr.4 to list the newly-supported cards.

(NB: I don't have the LSI SCSI or any Intel cards to test, just the
LSI SATA, which works fine for me.)
/src/sys/dev/usb/
H A Dusbdevs1.746 Sat Mar 17 19:37:11 GMT 2018 jdolecek add LAN78xx family (Raspberry Pi 3B+) entries - PR kern/53105
H A Dusbdevs.h1.746 Fri Jul 20 16:37:32 GMT 2018 martin Regen
H A Dusbdevs_data.h1.746 Fri Jul 20 16:37:32 GMT 2018 martin Regen
/src/share/man/man4/
H A DMakefile1.746 Tue Apr 15 22:33:38 GMT 2025 nia Add a man page for r128fb(4)

/src/sys/arch/i386/i386/
H A Dmachdep.c1.746 Tue Feb 04 22:48:26 GMT 2014 dsl Now that the sv_xmm and sv_87 fields in the pcb are the same size as the
hardware ones, and those in the mcontext, ptrace and core files we
can really safely cast and copy between the types.
Remove a couple of temporary buffers and add CTASSERT()s that the sizes
do actually match.
/src/distrib/sets/lists/base/
H A Dshl.mi1.746 Mon Aug 10 03:21:44 GMT 2015 mrg now that we only support gcc 4.8, make all the gcc tags just "gcc".
this should help with next-gcc, when we can add back gcc=48 and
gcc=5x tags, as necessary.
H A Dmi1.746 Sun May 11 18:01:46 GMT 2008 joerg Add nbsvtool to the sets.
/src/doc/
H A D3RDPARTY1.746 Tue Jan 26 16:59:27 GMT 2010 drochner note current isc-dhcp versions
(our branch is not listed as supported anymore)
H A DCHANGES1.746 Thu Nov 02 21:46:41 GMT 2006 pavel mention the default shell change.
/src/usr.bin/make/
H A Dparse.c1.746 Thu May 29 03:41:21 GMT 2025 sjg Ensure StackTrace is flushed
H A Dvar.c1.746 Sun Dec 20 15:04:29 GMT 2020 rillig make(1): fix memory leak in Var_Delete (since yesterday)

The memory leak had been introduced in var.c 1.736 from 2020-12-19
20:47:24.
/src/sys/arch/i386/conf/
H A DGENERIC1.746 Wed Apr 19 10:31:44 GMT 2006 drochner adjust comments for the new location of wskbdmap_mfii.c,
addresses PR kern/33290 by henry nelson
/src/distrib/sets/lists/man/
H A Dmi1.746 Sat Jan 08 22:29:38 GMT 2005 cube Add and install a manual page for tap(4).
/src/distrib/sets/lists/tests/
H A Dmi1.746 Sun May 21 15:28:38 GMT 2017 riastradh Remove MKCRYPTO option.

Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed fifteen years ago, and are
essentially irrelevant for software with published source code.

In the intervening time, nobody bothered to remove the option after
its motivation -- the US export restriction -- was eliminated. I'm
not aware of any other operating system that has a similar option; I
expect it is mainly out of apathy for churn that we still have it.
Today, cryptography is an essential part of modern computing -- you
can't use the internet responsibly without cryptography.

The position of the TNF board of directors is that TNF makes no
representation that MKCRYPTO=no satisfies any country's cryptography
regulations.

My personal position is that the availability of cryptography is a
basic human right; that any local laws restricting it to a privileged
few are fundamentally immoral; and that it is wrong for developers to
spend effort crippling cryptography to work around such laws.

As proposed on tech-crypto, tech-security, and tech-userlevel to no
objections:

https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html
https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html
https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html

P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of
*bad* crypto that was conditional on it, e.g. DES in telnet... That
should probably be removed too, but on the grounds that it is bad,
not on the grounds that it is (nominally) crypto.
/src/share/mk/
H A Dbsd.own.mk1.746 Mon Aug 12 16:39:28 GMT 2013 joerg Only ia64 defaults to USE_COMPILERCRTSTUFF=no now, so simplify
conditional.
/src/sys/conf/
H A Dfiles1.746 Wed Dec 07 00:42:03 GMT 2005 thorpej Remove the VNODE_OP_NOINLINE option. We now NEVER inline vnode ops.
Briefly discussed on tech-kern not too long ago.
/src/distrib/sets/lists/comp/
H A Dmi1.746 Mon Dec 20 03:50:04 GMT 2004 itojun RFC cannot be used as manpage regarding to the ISOC copyright boilerplate.
remove it until someone writes it up from scratch/freely-redistributable
text is found.

Completed in 1580 milliseconds