|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3 |
|
| #
bca7db71 |
| 27-Mar-2016 |
Imre Vadász <imre@vdsz.com> |
gpio_intel: Support integrated GPIO controllers of the Cherry Trail SoC.
* The gpio_acpi module takes care of probing and setting up the ACPI
GPIO-signaled events and the ACPI address space handle
gpio_intel: Support integrated GPIO controllers of the Cherry Trail SoC.
* The gpio_acpi module takes care of probing and setting up the ACPI
GPIO-signaled events and the ACPI address space handler, utilizing the
gpio interface provided by gpio_intel for the actual GPIO accesses.
* So far gpio_intel can only be used for the ACPI-5.0 GPIO features.
* This makes ACPI gpio events (which replace GPE interrupts on many
current x86 SoC devices) work, and provides a handler for the
GeneralPurposeIo Opregions of each GPIO controller.
* With this the HP x2 210 detachable correctly recognizes unplugging
of the power supply, and opening/closing of the lid.
* Further work is still needed to refactor gpio_intel to make adding
support for other SoC/CPU versions easier.
* The gpio_if.m interface is still a prototype that only provides a
minimum of functionality that is needed to get gpio_acpi working.
show more ...
|
|
Revision tags: v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc |
|
| #
b0d289c2 |
| 09-Jun-2015 |
Matthew Dillon <dillon@apollo.backplane.com> |
build - Parallelize kernel module build
* Parallelize the module build portion of a full buildkernel.
* Decreases full kernel build times significantly. The build
is up to 3 times faster now.
*
build - Parallelize kernel module build
* Parallelize the module build portion of a full buildkernel.
* Decreases full kernel build times significantly. The build
is up to 3 times faster now.
* On monster full kernel build time goes from 10:48 to 3:04.
show more ...
|
|
Revision tags: v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2 |
|
| #
2a617999 |
| 10-Nov-2014 |
Sascha Wildner <saw@online.de> |
Remove the old USB stack and related userland, etc.
As detailed in UPDATING, users with a custom configuration file which
was derived from a *GENERIC file before we made usb4bsd default (this
happen
Remove the old USB stack and related userland, etc.
As detailed in UPDATING, users with a custom configuration file which
was derived from a *GENERIC file before we made usb4bsd default (this
happened in 3.6) might need to remove or comment out a couple of
devices which are now unknown.
show more ...
|
|
Revision tags: v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2 |
|
| #
f0478b8b |
| 10-Mar-2014 |
Sascha Wildner <saw@online.de> |
Make usb4bsd the default USB stack.
To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
replace "device usb" with "device oldusb" in the kernel configuration.
Requested-by: di
Make usb4bsd the default USB stack.
To get back to the old stack, put "WANT_OLDUSB=yes" in /etc/make.conf and
replace "device usb" with "device oldusb" in the kernel configuration.
Requested-by: dillon, profmakx, marino etc.
show more ...
|
|
Revision tags: v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0 |
|
| #
8b9caf33 |
| 27-Sep-2012 |
Sascha Wildner <saw@online.de> |
usb4bsd: Hook usb, ehci, ohci, uhci, xhci, umass, and usfs into the build.
Adds some missing Makefiles and adjusts others.
With this commit, the corresponding modules all build when WANT_USB4BSD
is
usb4bsd: Hook usb, ehci, ohci, uhci, xhci, umass, and usfs into the build.
Adds some missing Makefiles and adjusts others.
With this commit, the corresponding modules all build when WANT_USB4BSD
is set, but they are not guaranteed to work. More bugs will be fixed in
subsequent commits.
The new USB code can't yet be built into the kernel.
Submitted-by: Markus Pfeiffer <markus.pfeiffer@morphism.de>
show more ...
|
|
Revision tags: v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
| #
f8e80553 |
| 22-Apr-2005 |
Sascha Wildner <swildner@dragonflybsd.org> |
Remove support for canbus (which is PC98 specific).
|
| #
62621166 |
| 15-Mar-2004 |
Matthew Dillon <dillon@dragonflybsd.org> |
Add a Makefile stub to build pccard as a module.
Submitted-by: Dheeraj Reddy <dheerajs@comcast.net>
Taken-From: FreeBSD-5
|
| #
0141a2b1 |
| 22-Aug-2003 |
Matthew Dillon <dillon@dragonflybsd.org> |
Reintegrate the module build for usb.ko
|
| #
d8113615 |
| 15-Aug-2003 |
Matthew Dillon <dillon@dragonflybsd.org> |
Make modules work again part 1: wire up the module build for bus/
|
| #
a9656fbc |
| 16-Aug-2010 |
Sascha Wildner <saw@online.de> |
iicbus: Bring us closer to FreeBSD.
This is work in progress and I commit it so Dave Shao's Summer of Code
project can proceed.
Further commits will follow.
Taken-from: FreeBSD
|
| #
d6644679 |
| 16-Apr-2010 |
Sascha Wildner <saw@online.de> |
Bring in FreeBSD's MMC (MultiMediaCard) stack.
mmc(4) - The MMC bus
sdhci(4) - Host controller driver
mmcsd(4) - Memory card disk device driver
SD, SDHC and MMC cards should be supported (tested
Bring in FreeBSD's MMC (MultiMediaCard) stack.
mmc(4) - The MMC bus
sdhci(4) - Host controller driver
mmcsd(4) - Memory card disk device driver
SD, SDHC and MMC cards should be supported (tested with an SDHC card).
show more ...
|