It has been observed in the wild that some individual instances of
ISP10[24]0 controllers don't seem to like getting a 64-bit DMA address
from our driver (at least, there seems to be some sort of incorrect
handling vis a vis the RQSTYPE_A64 message in isp_intr()).
Upon inspection, it was noted that in isp_pci_dmasetup(), the decision
to use RQSTYPE_T3RQS vs RQSTYPE_T2RQS was conditional on sizeof(bus_addr_t)
being larger than sizeof(uint32_t).
However, this isn't the correct predicate; instead, the choice should
be dependent on what the largest value that bus_addr_t will have. As
it happans, the PCI layer makes a distinction between 32-bit and 64-bit
DMA windows, and isp_pci's use of the regular "pa->pa_dmat" would ensure
that the DMA address always fits within 32-bits. Therefore, there was
never a reason to use RQSTYPE_T3RQS, regardless of the size of bus_addr_t.
As such, we tweak the code to depend explicitly on a new isp_use_dma64
flag, which is initialized by the bus front-end according to the DMA
window selection that's been made.
[4 lines not shown]
rust197: complete the transition to the "new fix" for the memchr crate.
Apply the vector.rs patch consistently also to the 2.7.4 memchr crate,
so that we do not get checksum conflicts for files in newer crates
which are un-changed from 2.7.4 with the older set of patches.
Should complete the fix of https://github.com/rust-lang/rust/issues/159919.
Support for the 21142/21143 internal NWay block is structured like a
PHY driver, but it was overlooked when the ifmedia/mii layer gained a
locking protocol. Update it to avoid a recursive mutex acquisition
that can occur if the autonegotiation completes (very) quickly.
PR kern/60494
Update to nabud-1.4.3.
Upstream changes: New --with-pak=no and --with-ssl=no which, when combined,
will elide any crypto library references from nabud.
p5-Module-Pluggable: update to 6.4.
2026-07-25 - 6.4
Add a CI/CD pipeline for the first time in 26 years
Add the ability to make search search "strict" and only walk the given search_dirs (thanks @rjbs)
Add much more documentation to Module::Pluggable::Object (thanks Dave Rolsky)
Make it so that you can give each search_path its own custom options
Finally fix spurious test failure because of already installed modules I hope (thanks @SZREZIC, Andreas Koenig and @ZEFRAM)
Remove optional_features from Makefile.PL META_MERGE which caused installation confusion sometimes
Add the ability to have different sorting algorithms (thanks @CHOHAG)
Fix the issues with OSX extended-attributes on files (thanks pgoyette99)
Clean up old stale core-lib (thanks @dolmen and @haarg)
Always use snprintf for MPI_EVENT_INTEGRATED_RAID output. Keep better
track of the amount that we've already printed and increase the max
length to handle all string combinations (even if they shouldn't happen).
From a suggestion by kre.
p5-HTTP-Message: update to 7.04.
7.04 2026-07-24 00:01:56Z
- add RFC 10008 HTTP QUERY method (GH#225) (Daniel Böhmer),
see https://datatracker.ietf.org/doc/rfc10008/
7.03 2026-07-21 20:45:16Z
- Fix max_body_size for Content-Encoding: br, which made every brotli
response fail to decode whenever a limit was set (GH#229)
p5-HTTP-Cookies: update to 6.12.
6.12 2026-07-26 02:34:52Z
- Honour Max-Age when extracting cookies; it had been silently ignored
since 6.10, so Max-Age=0 no longer deleted a cookie and a Max-Age
lifetime was never applied (GH#69) (reported by Robert Mueller)
- When both Max-Age and Expires are present, let Max-Age take precedence
regardless of order, and let a repeated attribute's last value win, per
RFC 6265 5.3 (GH#69)
groff: rename ghostscript option back to groff-docs
It pulls in more than ghostscript, and there was no backwards
compatibility provided for the old option.
Move the text noting the 4Gb boot restriction from the BUGS section
to the main text and expand it, as it not restricted to UltraSPARC 1
and 2 machines.
Minor grammar fix whilst here.
