src-test/sys/dev/powermac_nvram, branch mainFreeBSD source treehttps://cgit-dev.freebsd.org/src-test/atom?h=main2020-09-01T21:59:31Zpowermac_nvram: clean up empty lines in .c and .h files2020-09-01T21:59:31ZMateusz Guzikmjg@FreeBSD.org2020-09-01T21:59:31Zurn:sha1:3cfc80b28a5e6f3afa62bd99b8be1ae4f1251141[PowerPC] De-giant powermac_nvram, update documentation2020-06-19T18:36:10ZBrandon Bergrenbdragon@FreeBSD.org2020-06-19T18:36:10Zurn:sha1:37f530582dc5c6ffa83607fdab730a8506c7f466
* Remove the giant lock requirement from powermac_nvram.
* Update manual pages to reflect current state.
Reviewed by: bcr (manpages), jhibbits
Sponsored by: Tag1 Consulting, Inc.
Differential Revision: https://reviews.freebsd.org/D24812
sys/dev: further adoption of SPDX licensing ID tags.2017-11-27T14:52:40ZPedro F. Giffunipfg@FreeBSD.org2017-11-27T14:52:40Zurn:sha1:718cf2ccb9956613756ab15d7a0e28f2c8e91cab
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.
The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
Move Open Firmware device root on PowerPC, ARM, and MIPS systems to2014-02-05T14:44:22ZNathan Whitehornnwhitehorn@FreeBSD.org2014-02-05T14:44:22Zurn:sha1:65d08437ef519124f39f113262a3cc71dadb8569
a sub-node of nexus (ofwbus) rather than direct attach under nexus. This
fixes FDT on x86 and will make coexistence with ACPI on ARM systems easier.
SPARC is unchanged.
Reviewed by: imp, ian
"nvram,flash" may not be the first in the compatible list property of the2012-05-20T02:43:54ZJustin Hibbitsjhibbits@FreeBSD.org2012-05-20T02:43:54Zurn:sha1:c1d93092fd883c77a31388ecc49c496da21d89f8
nvram ofw node, so check all strings in the list.
Approved by: nwhitehorn (mentor)
MFC after: 3 days
Add support for the Sharp/Micron flash chips to powermac_mvram(4).2010-09-05T20:04:02ZAlexander Motinmav@FreeBSD.org2010-09-05T20:04:02Zurn:sha1:af82b9a9ee7ef272097fca919250279370710ddc
Tested on PowerMac G4 AGP.
Reviewed by: nwhitehorn
Use si_drv1 instead of dev2unit() in powermac_nvram.2009-04-14T13:18:39ZEd Schoutened@FreeBSD.org2009-04-14T13:18:39Zurn:sha1:907859721048646fe50d114391a2bbe5a664d97d
Reviewed by: nwhitehorn
Add support for 64-bit PowerPC CPUs operating in the 64-bit bridge mode2009-04-04T00:22:44ZNathan Whitehornnwhitehorn@FreeBSD.org2009-04-04T00:22:44Zurn:sha1:1c96bdd14645b8778bd1ec4e0ddcdda18195a99f
provided, for example, on the PowerPC 970 (G5), as well as on related CPUs
like the POWER3 and POWER4.
This also adds support for various built-in hardware found on Apple G5
hardware (e.g. the IBM CPC925 northbridge).
Reviewed by: grehan
Convert PowerPC AIM PCI and nexus busses to standard OFW bus interface. This2008-10-14T14:54:14ZNathan Whitehornnwhitehorn@FreeBSD.org2008-10-14T14:54:14Zurn:sha1:51d163d3e91cbf4fe782352c88c0dc6f37015b47
simplifies certain device attachments (Kauai ATA, for instance), and makes
possible others on new hardware.
On G5 systems, there are several otherwise standard PCI devices
(Serverworks SATA) that will not allow their interrupt properties to be
written, so this information must be supplied directly from Open Firmware.
Obtained from: sparc64
Replace all calls to minor() with dev2unit().2008-09-27T08:51:18ZEd Schoutened@FreeBSD.org2008-09-27T08:51:18Zurn: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