FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F9.3 2013-08-13T22:05:50Z 2013-08-13T22:05:50Z Scott Long scottl@FreeBSD.org 2013-08-13T22:05:50Z urn:sha1:cffe159b0e61cee6bce082f4bd05a4f06a1d53a9 Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCI command register. The lazy BAR allocation code in FreeBSD sometimes disables this bit when it detects a range conflict, and will re-enable it on demand when a driver allocates the BAR. Thus, the bit is no longer a reliable indication of capability, and should not be checked. This results in the elimination of a lot of code from drivers, and also gives the opportunity to simplify a lot of drivers to use a helper API to set the busmaster enable bit. This changes fixes some recent reports of disk controllers and their associated drives/enclosures disappearing during boot. Candidate for 9.2 Submitted by: jhb Reviewed by: jfv, marius, adrian, achim 2013-04-05T08:22:11Z Alexander Motin mav@FreeBSD.org 2013-04-05T08:22:11Z urn:sha1:1139d398ea93668ee65ae02b8ceab630ca9e5487 Mark MALLOC_DEFINEs static that have no corresponding MALLOC_DECLAREs. This means that their use is restricted to a single C file. 2011-08-11T12:30:23Z Robert Watson rwatson@FreeBSD.org 2011-08-11T12:30:23Z urn:sha1:a9d2f8d84f69e98100b5746816b35666bcf992ac kernel for FreeBSD 9.0: Add a new capability mask argument to fget(9) and friends, allowing system call code to declare what capabilities are required when an integer file descriptor is converted into an in-kernel struct file *. With options CAPABILITIES compiled into the kernel, this enforces capability protection; without, this change is effectively a no-op. Some cases require special handling, such as mmap(2), which must preserve information about the maximum rights at the time of mapping in the memory map so that they can later be enforced in mprotect(2) -- this is done by narrowing the rights in the existing max_protection field used for similar purposes with file permissions. In namei(9), we assert that the code is not reached from within capability mode, as we're not yet ready to enforce namespace capabilities there. This will follow in a later commit. Update two capability names: CAP_EVENT and CAP_KEVENT become CAP_POST_KEVENT and CAP_POLL_KEVENT to more accurately indicate what they represent. Approved by: re (bz) Submitted by: jonathan Sponsored by: Google Inc 2011-06-28T08:36:48Z Kevin Lo kevlo@FreeBSD.org 2011-06-28T08:36:48Z urn:sha1:ee6eac62f7525e948d3b693e4eef182f84625852 2010-11-15T05:25:51Z Doug Barton dougb@FreeBSD.org 2010-11-15T05:25:51Z urn:sha1:eb581844e4339a481b679f315bd1cc8da837555e 2009-12-29T21:51:28Z Robert Noland rnoland@FreeBSD.org 2009-12-29T21:51:28Z urn:sha1:cfd7bacef28efb62a65a679e3e879078e7932b36 This replaces d_mmap() with the d_mmap2() implementation and also changes the type of offset to vm_ooffset_t. Purge d_mmap2(). All driver modules will need to be rebuilt since D_VERSION is also bumped. Reviewed by: jhb@ MFC after: Not in this lifetime... 2009-04-14T11:57:26Z Ed Schouten ed@FreeBSD.org 2009-04-14T11:57:26Z urn:sha1:9555aafab29fa9dcc26056209b90677bd0821e8c 2008-09-27T08:51:18Z Ed Schouten ed@FreeBSD.org 2008-09-27T08:51:18Z urn:sha1:6bfa9a2d66dd0e00182017d6741d44e54d0b2cca After I removed all the unit2minor()/minor2unit() calls from the kernel yesterday, I realised calling minor() everywhere is quite confusing. Character devices now only have the ability to store a unit number, not a minor number. Remove the confusion by using dev2unit() everywhere. This commit could also be considered as a bug fix. A lot of drivers call minor(), while they should actually be calling dev2unit(). In -CURRENT this isn't a problem, but it turns out we never had any problem reports related to that issue in the past. I suspect not many people connect more than 256 pieces of the same hardware. Reviewed by: kib 2008-03-13T14:08:41Z Coleman Kane cokane@FreeBSD.org 2008-03-13T14:08:41Z urn:sha1:e42e0b86696d87a2d9ffe6e76c4b2423464cbef0 failing to load on a kernel that has "nodevice mem" in the config. It will now properly bring in the mem(4) module. Submitted by: antoine Reviewed by: imp MFC after: 1 week 2006-03-03T21:37:38Z Yaroslav Tykhiy ytykhiy@gmail.com 2006-03-03T21:37:38Z urn:sha1:375ce6798ff677713636505c46fd0dba827341fd into a separate module. Accordingly, convert the option into a device named similarly. Note for MFC: Perhaps the option should stay in RELENG_6 for POLA reasons. Suggested by: scottl Reviewed by: cokane MFC after: 5 days