History log of /dragonfly/etc/devd/Makefile (Results 1 – 5 of 5)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
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
# 5a31d992 05-Jan-2019 Sascha Wildner <saw@online.de>

Clean up the USB driver directories, remove unbuilt source.

Remove old source that has not (yet) been ported. If any of these
drivers would get ported in the future, it would be from current
FreeBSD

Clean up the USB driver directories, remove unbuilt source.

Remove old source that has not (yet) been ported. If any of these
drivers would get ported in the future, it would be from current
FreeBSD source anyway. Keeping the old source around just confuses
when grepping in /usr/src.

show more ...


Revision tags: 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, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc
# bfc0d4cd 21-Aug-2015 Sascha Wildner <saw@online.de>

i386 removal, part 37/x: Remove more i386 related small bits and pieces.


Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2
# d917c8d8 04-Dec-2014 Sascha Wildner <saw@online.de>

devd(8): Fix asus.conf installation.


Revision tags: v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, 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
# 7eb536fd 21-May-2014 Sascha Wildner <saw@online.de>

s/NO_OBJ/NOOBJ/ in a few Makefiles.


Revision tags: v3.6.2
# e348c2ad 12-Mar-2014 Sascha Wildner <saw@online.de>

devd(8): Sync with FreeBSD and turn it on by default.

Most important of all, it cares about knowing which USB modules
support which device/vendor IDs and it will load the associated
module upon USB

devd(8): Sync with FreeBSD and turn it on by default.

Most important of all, it cares about knowing which USB modules
support which device/vendor IDs and it will load the associated
module upon USB device plugging if it is not already loaded or
in the kernel config.

Taken-from: FreeBSD

show more ...