mn: report that this driver is removed in 14, not 13
Fix compilation after r368397.MFC after: 3 daysSponsored by: Mellanox Technologies // NVIDIA Networking
Add deprecation notice to mn(4)Sync serial (T1/E1) interfaces are largely irrelevant today and phkconfirms this driver is unnecessary in review D23928.This leaves ce(4) and cp(4) in the tree. T
Add deprecation notice to mn(4)Sync serial (T1/E1) interfaces are largely irrelevant today and phkconfirms this driver is unnecessary in review D23928.This leaves ce(4) and cp(4) in the tree. They're likely not relevanteither, but glebius contacted the manufacturer and those devices arestill available for purchase. At glebius' suggestion leave them inthe tree as long as they do not impose a maintenace burden.Approved by: phkMFC after: 3 daysSponsored by: The FreeBSD Foundation
show more ...
Followup on r364922. Old comment said that the only reason to putthe hook at queue mode was that mn_rx_intr() doesn't run at splnetlevel. In today's netgraph the only legitimate reason for queue mo
Followup on r364922. Old comment said that the only reason to putthe hook at queue mode was that mn_rx_intr() doesn't run at splnetlevel. In today's netgraph the only legitimate reason for queue modeis recursion avoidance. So I see no reason for queue mode here.Not tested!
Update outdated commentThere is no splnet anymore, so update the comment to drop referencesto it.
Remove unused 'struct rtentry' definition.
SPDX: use the Beerware identifier.
sys/dev: minor spelling fixes.Most affect comments, very few have user-visible effects.
Replace 0 with NULL for pointers in misc. device drivers.Found with devel/coccinelle.
In order to reduce use of M_EXT outside of the mbuf allocator andsocket-buffer implementations, introduce a return value for MCLGET()(and m_cljget() that underlies it) to allow the caller to avoid
In order to reduce use of M_EXT outside of the mbuf allocator andsocket-buffer implementations, introduce a return value for MCLGET()(and m_cljget() that underlies it) to allow the caller to avoid testingM_EXT itself. Update all callers to use the return value.With this change, very few network device drivers remain aware ofM_EXT; the primary exceptions lie in mbuf-chain pretty printers fordebugging, and in a few cases, custom mbuf and cluster allocationimplementations.NB: This is a difficult-to-test change as it touches many drivers forwhich I don't have physical devices. Instead we've gone for intensivereview, but further post-commit review would definitely be appreciatedto spot errors where changes could not easily be made mechanically,but were largely mechanical in nature.Differential Revision: https://reviews.freebsd.org/D1440Reviewed by: adrian, bz, gnnSponsored by: EMC / Isilon Storage Division
Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCIcommand register. The lazy BAR allocation code in FreeBSD sometimesdisables this bit when it detects a range conflict, and w
Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCIcommand register. The lazy BAR allocation code in FreeBSD sometimesdisables this bit when it detects a range conflict, and will re-enableit on demand when a driver allocates the BAR. Thus, the bit is no longera reliable indication of capability, and should not be checked. Thisresults in the elimination of a lot of code from drivers, and also givesthe opportunity to simplify a lot of drivers to use a helper API to setthe busmaster enable bit.This changes fixes some recent reports of disk controllers and theirassociated drives/enclosures disappearing during boot.Submitted by: jhbReviewed by: jfv, marius, achadd, achimMFC after: 1 day
Use DEVMETHOD_END macro defined in sys/bus.h instead of {0, 0} sentinel on device_method_t arraysReviewed by: cognetApproved by: cognet
Mechanically substitute flags from historic mbuf allocator withmalloc(9) flags in sys/dev.
Remove unused static mn_timeout.
Move mn over. One of the last stragglers in sys/pci. There's nomodule built for this hardware, so no changes needed.