#
43a62df0 |
| 10-Jul-2024 |
Emmanuel Vadot <manu@FreeBSD.org> |
conf: powerpc: Add evdev to some kernel configs
Fixes: 13d00a43cba4 ("conf: Add usbhid and hidbus to GENERIC* kernel configs") Sponsored by: Beckhoff Automation GmbH & Co. KG
|
#
13d00a43 |
| 20-Jun-2024 |
Emmanuel Vadot <manu@FreeBSD.org> |
conf: Add usbhid and hidbus to GENERIC* kernel configs
Include the new unified HID stack by default in generic. This will allow us to migrate to the multi-stack hkbd and hms instead of relying on th
conf: Add usbhid and hidbus to GENERIC* kernel configs
Include the new unified HID stack by default in generic. This will allow us to migrate to the multi-stack hkbd and hms instead of relying on the older ukbd and ums which only work with USB. To test those drivers just add hw.usb.usbhid.enable=1 in loader.conf
Differential Revision: https://reviews.freebsd.org/D45658 Reviewed by: emaste, imp, wulf (all older version) Sponsored by: Beckhoff Automation GmbH & Co. KG
show more ...
|
Revision tags: release/14.1.0, release/13.3.0, release/14.0.0 |
|
#
031beb4e |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
Revision tags: release/13.2.0, release/12.4.0 |
|
#
35ce7d40 |
| 06-Aug-2022 |
Justin Hibbits <jhibbits@FreeBSD.org> |
powerpc/booke: Clamp MAXCPU to 32 for Book-E platforms
Since the likelihood of new Book-E PowerPC SoCs being produced is near zero clamp MAXCPU to around the highest number of cores/threads availabl
powerpc/booke: Clamp MAXCPU to 32 for Book-E platforms
Since the likelihood of new Book-E PowerPC SoCs being produced is near zero clamp MAXCPU to around the highest number of cores/threads available currently, for both 64-bit and 32-bit. Even though the current highest core/thread count is 24, the cap is set at 32 in case there is code that assumes power of 2.
show more ...
|
Revision tags: release/13.1.0 |
|
#
c227269e |
| 07-Feb-2022 |
John Baldwin <jhb@FreeBSD.org> |
Stop adding -Wredundant-decls to CWARNFLAGS.
clang doesn't implement it, and Linux doesn't enforce it. As a result, new instances keep cropping up both in FreeBSD's code and in upstream sources fro
Stop adding -Wredundant-decls to CWARNFLAGS.
clang doesn't implement it, and Linux doesn't enforce it. As a result, new instances keep cropping up both in FreeBSD's code and in upstream sources from vendors.
Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D34144
show more ...
|
Revision tags: release/12.3.0, release/13.0.0, release/12.2.0 |
|
#
19758786 |
| 05-Oct-2020 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
hid: Import functions and constants required by new subsystem
This does an import of quirk stubs, debugging macros from USB code and numerous usage constants used by dependent drivers.
Besides, thi
hid: Import functions and constants required by new subsystem
This does an import of quirk stubs, debugging macros from USB code and numerous usage constants used by dependent drivers.
Besides, this change renames some functions to get a better matching with userland library and NetBSD/OpenBSD HID code. Namely:
- Old hid_report_size() renamed to hid_report_size_max() - New hid_report_size() calculates size of given report rather than maximum size of all reports. - hid_get_data_unsigned() renamed to hid_get_udata() - hid_put_data_unsigned() renamed to hid_put_udata()
Compat shim functions are provided in usbhid.h to make possible compile of legacy code unmodified after this change.
Reviewed by: manu, hselasky Differential revision: https://reviews.freebsd.org/D27887
show more ...
|
#
67de2db2 |
| 05-Oct-2020 |
Vladimir Kondratyev <wulf@FreeBSD.org> |
Factor-out hardware-independent part of USB HID support to new module
It will be used by the upcoming HID-over-i2C implementation. Should be no-op, except hid.ko module dependency is to be added to
Factor-out hardware-independent part of USB HID support to new module
It will be used by the upcoming HID-over-i2C implementation. Should be no-op, except hid.ko module dependency is to be added to affected drivers.
Reviewed by: hselasky, manu Differential revision: https://reviews.freebsd.org/D27867
show more ...
|
Revision tags: release/11.4.0 |
|
#
26644b01 |
| 16-May-2020 |
Justin Hibbits <jhibbits@FreeBSD.org> |
powerpc/qoriq: Add more devices to config for desktop usage
The most likely users of the QORIQ64 config nowadays are users of AmigaOne X5000 systems, which are desktops. They need a framebuffer and
powerpc/qoriq: Add more devices to config for desktop usage
The most likely users of the QORIQ64 config nowadays are users of AmigaOne X5000 systems, which are desktops. They need a framebuffer and keyboard/mouse, so add these to the config so it works by default once drm-current-kmod is installed.
show more ...
|
#
24e87ffa |
| 04-Jan-2020 |
Justin Hibbits <jhibbits@FreeBSD.org> |
powerpc: Remove 'sec' device from QORIQ64 config
The SEC crypto engine, as implemented in this driver, does not exist on any 64-bit SoC, so don't bother compiling it in.
|
Revision tags: release/12.1.0 |
|
#
c5c3ba6b |
| 03-Sep-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r351317 through r351731.
|
#
7d65d420 |
| 25-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Fix bogusly declared WERRORs in kernel build
Many arm kernel configs bogusly specified WERROR=-Werror. There's no reason for this because the default is that and there's no reason to override. These
Fix bogusly declared WERRORs in kernel build
Many arm kernel configs bogusly specified WERROR=-Werror. There's no reason for this because the default is that and there's no reason to override. These date from a time when we needed to add additional warning->error suppression. They are obsolete and were cut and paste propagated from file to file.
Comment out all the WERROR=.... lines in powerpc. They aren't bogus, but were appropriate for the old defaults for gcc4.2.1. Now that we've made the policy decision to suppress -Werror by default on these platforms, it is appropriate to comment these out. People wishing to fix these errors can still un-comment them out, or say WERROR=-Werror on the command line.
Fix two instances (cut and paste propagation) of hard-coded -Werror in x86 code. Replace with ${WERROR} instead. This is a no-op change except for people who build WERROR=-Wno-error :).
This should fix tinderbox / CI breakage.
show more ...
|
Revision tags: release/11.3.0 |
|
#
7f49ce7a |
| 28-Jun-2019 |
Alan Somers <asomers@FreeBSD.org> |
MFHead @349476
Sponsored by: The FreeBSD Foundation
|
#
c363b16c |
| 21-Jun-2019 |
Conrad Meyer <cem@FreeBSD.org> |
sys: Remove DEV_RANDOM device option
Remove 'device random' from kernel configurations that reference it (most). Replace perhaps mistaken 'nodevice random' in two MIPS configs with 'options RANDOM_L
sys: Remove DEV_RANDOM device option
Remove 'device random' from kernel configurations that reference it (most). Replace perhaps mistaken 'nodevice random' in two MIPS configs with 'options RANDOM_LOADABLE' instead. Document removal in UPDATING; update NOTES and random.4.
Reviewed by: delphij, markm (previous version) Approved by: secteam(delphij) Differential Revision: https://reviews.freebsd.org/D19918
show more ...
|
#
7648bc9f |
| 13-May-2019 |
Alan Somers <asomers@FreeBSD.org> |
MFHead @347527
Sponsored by: The FreeBSD Foundation
|
#
251a32b5 |
| 08-May-2019 |
Kyle Evans <kevans@FreeBSD.org> |
tun/tap: merge and rename to `tuntap`
tun(4) and tap(4) share the same general management interface and have a lot in common. Bugs exist in tap(4) that have been fixed in tun(4), and vice-versa. Let
tun/tap: merge and rename to `tuntap`
tun(4) and tap(4) share the same general management interface and have a lot in common. Bugs exist in tap(4) that have been fixed in tun(4), and vice-versa. Let's reduce the maintenance requirements by merging them together and using flags to differentiate between the three interface types (tun, tap, vmnet).
This fixes a couple of tap(4)/vmnet(4) issues right out of the gate: - tap devices may no longer be destroyed while they're open [0] - VIMAGE issues already addressed in tun by kp
[0] emaste had removed an easy-panic-button in r240938 due to devdrn blocking. A naive glance over this leads me to believe that this isn't quite complete -- destroy_devl will only block while executing d_* functions, but doesn't block the device from being destroyed while a process has it open. The latter is the intent of the condvar in tun, so this is "fixed" (for certain definitions of the word -- it wasn't really broken in tap, it just wasn't quite ideal).
ifconfig(8) also grew the ability to map an interface name to a kld, so that `ifconfig {tun,tap}0` can continue to autoload the correct module, and `ifconfig vmnet0 create` will now autoload the correct module. This is a low overhead addition.
(MFC commentary)
This may get MFC'd if many bugs in tun(4)/tap(4) are discovered after this, and how critical they are. Changes after this are likely easily MFC'd without taking this merge, but the merge will be easier.
I have no plans to do this MFC as of now.
Reviewed by: bcr (manpages), tuexen (testing, syzkaller/packetdrill) Input also from: melifaro Relnotes: yes Differential Revision: https://reviews.freebsd.org/D20044
show more ...
|
#
c2c227a5 |
| 03-Feb-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r343571 through r343711.
|
#
c75f49f7 |
| 31-Jan-2019 |
Konstantin Belousov <kib@FreeBSD.org> |
Make iflib a loadable module.
iflib is already a module, but it is unconditionally compiled into the kernel. There are drivers which do not need iflib(4), and there are situations where somebody mi
Make iflib a loadable module.
iflib is already a module, but it is unconditionally compiled into the kernel. There are drivers which do not need iflib(4), and there are situations where somebody might not want iflib in kernel because of using the corresponding driver as module.
Reviewed by: marius Discussed with: erj Sponsored by: The FreeBSD Foundation MFC after: 2 weeks Differential revision: https://reviews.freebsd.org/D19041
show more ...
|
Revision tags: release/12.0.0, release/11.2.0 |
|
#
675147dd |
| 24-Feb-2018 |
Justin Hibbits <jhibbits@FreeBSD.org> |
Change ident for QORIQ64 kernel conf
Make it match the conf file name.
|
#
0a3ef103 |
| 28-Jan-2018 |
Justin Hibbits <jhibbits@FreeBSD.org> |
Start building modules for QORIQ64
There's no reason not to build modules for 64-bit QorIQ devices. This config has evolved to be analogous to the AIM GENERIC64 kernel, so will grow to match it in
Start building modules for QORIQ64
There's no reason not to build modules for 64-bit QorIQ devices. This config has evolved to be analogous to the AIM GENERIC64 kernel, so will grow to match it in more ways as well.
show more ...
|
#
c2c014f2 |
| 07-Nov-2017 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Merge ^/head r323559 through r325504.
|
#
f6e116ee |
| 04-Nov-2017 |
Enji Cooper <ngie@FreeBSD.org> |
MFhead@r325383
|
#
51cfee5d |
| 04-Nov-2017 |
Justin Hibbits <jhibbits@FreeBSD.org> |
Stop passing -me500 to the assembler for Book-E kernels
We already pass -many to the assembler, and -me500 drops 64-bit instruction handling, for some reason only breaking module building for 64-bit
Stop passing -me500 to the assembler for Book-E kernels
We already pass -many to the assembler, and -me500 drops 64-bit instruction handling, for some reason only breaking module building for 64-bit kernels.
Additionally, build with CTF for dtrace.
show more ...
|
#
140db603 |
| 01-Nov-2017 |
Justin Hibbits <jhibbits@FreeBSD.org> |
Enable a bunch more options in the QORIQ64 kernel
This brings it closer to par with GENERIC64. In the future I hope to have a GENERIC64-E and GENERIC-E kernels as Book-E analogues to the GENERIC64/
Enable a bunch more options in the QORIQ64 kernel
This brings it closer to par with GENERIC64. In the future I hope to have a GENERIC64-E and GENERIC-E kernels as Book-E analogues to the GENERIC64/GENERIC AIM kernels.
show more ...
|
#
0821ef1a |
| 31-Oct-2017 |
Enji Cooper <ngie@FreeBSD.org> |
MFhead@r325209
|
#
a32b5435 |
| 31-Oct-2017 |
Justin Hibbits <jhibbits@FreeBSD.org> |
Make DPAA work in 64-bit mode
Rework the dTSEC and FMan drivers to be more like a full bus relationship, so that dtsec can use bus_alloc_resource() instead of trying to handle the offset from the dt
Make DPAA work in 64-bit mode
Rework the dTSEC and FMan drivers to be more like a full bus relationship, so that dtsec can use bus_alloc_resource() instead of trying to handle the offset from the dts. This required taking some code from the sparc64 ebus driver to allow subdividing the fman region for the dTSEC devices.
show more ...
|