aboutsummaryrefslogtreecommitdiff
path: root/sys/arm/conf/TEGRA124
Commit message (Collapse)AuthorAgeFilesLines
* sys: RealTek -> Realtekykla2025-11-271-2/+2
| | | | | | | | | | | Realtek changed how it styled its name 25 or so years ago, but the old style persisted in many places. These products use the new styling in their datasheets. Signed-off-by: ykla yklaxds@gmail.com Sponsored by: Chinese FreeBSD Community Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1901
* sys: NOTES: Fix comment for wlan_* devices; GENERIC*: Re-order 'wlan_tkip'Olivier Certner2025-09-091-1/+1
| | | | | | | | | | | | | | | | | Fix the comment introducing the 'wlan_*' devices (AES-CCMP is missing) after introducing AES-GCMP. While here, re-order the devices in order of appearance of the related technologies. No functional change (intended). Reviewed by: adrian, emaste Fixes: 7bf82ea4fdda ("sys: add wlan_gcmp to GENERIC kernels as appropriate") MFC after: 3 days MFC to: stable/15 Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52444
* sys: add wlan_gcmp to GENERIC kernels as appropriateAdrian Chadd2025-03-271-0/+1
| | | | | | | Add wlan_gcmp wherever CCMP is defined in kernel configs. Differential Revision: https://reviews.freebsd.org/D49343 Reviewed by: bz, cy
* arm: Add evdev to the TEGRA124 configMark Johnston2024-07-111-0/+5
| | | | | | This is required for the kernel to link after commit 13d00a43cba4. Fixes: 13d00a43cba4 ("conf: Add usbhid and hidbus to GENERIC* kernel configs")
* conf: Add usbhid and hidbus to GENERIC* kernel configsEmmanuel Vadot2024-07-101-0/+4
| | | | | | | | | | | 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
* arm: Set NEW_PCIB in DEFAULTS rather than a subset of kernel configsJessica Clarke2024-02-221-1/+0
| | | | | | | | | | | | | | | | | | | All other architectures set NEW_PCIB in DEFAULTS, with arm being the one remaining straggler that only sets it for GENERIC and TEGRA124. ARMADA38X and ARMADAXP contain device pci but don't set NEW_PCIB, however GENERIC claims to support them and as part of that NEW_PCIB support was added to mv_pci, so these configs are most likely just stale. Other than NOTES that just leaves ALPINE as the one kernel with PCI support not covered by GENERIC, but al_pci is supported by arm64 which enables NEW_PCIB, and it's just a generic_pcie_fdt_driver with some fixup code to deal with quirks so should support PCI_RES_BUS just fine. Therefore it is believed that all in-tree kernel configs support NEW_PCIB in reality, and so let's take a step towards removing all the non-NEW_PCIB code by having it always-on everywhere. Reviewed by: emaste, jhb, manu MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D43806
* sys: Remove $FreeBSD$: one-line sh patternWarner Losh2023-08-161-1/+0
| | | | Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
* arm: conf: Remove options EXT_RESOURCESEmmanuel Vadot2022-02-211-2/+1
| | | | | | | It is now unused in kernel code. MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D33837
* sys/*/conf/*, docs: fix links to handbookCeri Davies2021-05-201-1/+1
| | | | | | | | | | | | While here, fix all links to older en_US.ISO8859-1 documentation in the src/ tree. PR: 255026 Reported by: Michael Büker <freebsd@michael-bueker.de> Reviewed by: dbaio Approved by: blackend (mentor), re (gjb) MFC after: 10 days Differential Revision: https://reviews.freebsd.org/D30265
* Factor-out hardware-independent part of USB HID support to new moduleVladimir Kondratyev2021-01-071-0/+3
| | | | | | | | 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
* arm: Fix TEGRA124 kernelEmmanuel Vadot2019-07-271-0/+1
| | | | | | | | | | Since r350162 device syscon is needed for sdhci driver. Add it to the config file. Reported by: dim Notes: svn path=/head/; revision=350372
* sys: Remove DEV_RANDOM device optionConrad Meyer2019-06-211-1/+0
| | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=349253
* tun/tap: merge and rename to `tuntap`Kyle Evans2019-05-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=347241
* Revert drm2 removal.Warner Losh2018-08-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Revert r338177, r338176, r338175, r338174, r338172 After long consultations with re@, core members and mmacy, revert these changes. Followup changes will be made to mark them as deprecated and prent a message about where to find the up-to-date driver. Followup commits will be made to make this clear in the installer. Followup commits to reduce POLA in ways we're still exploring. It's anticipated that after the freeze, this will be removed in 13-current (with the residual of the drm2 code copied to sys/arm/dev/drm2 for the TEGRA port's use w/o the intel or radeon drivers). Due to the impending freeze, there was no formal core vote for this. I've been talking to different core members all day, as well as Matt Macey and Glen Barber. Nobody is completely happy, all are grudgingly going along with this. Work is in progress to mitigate the negative effects as much as possible. Requested by: re@ (gjb, rgrimes) Notes: svn path=/head/; revision=338285
* disconnect drm2 from tegra build until made self-containedMatt Macy2018-08-221-1/+0
| | | | Notes: svn path=/head/; revision=338174
* Update several more URLsEitan Adler2017-10-291-2/+2
| | | | | | | | - Primarily http -> https - Primarily FreeBSD project URLs Notes: svn path=/head/; revision=325096
* Tag all armv7 kernels as such in their machine config line.Warner Losh2017-10-051-1/+1
| | | | | | | | | | | | | | Transition all boards that support arm cortex CPUs to armv7. This leaves two armv6 kernels in the tree. RPI-B, which uses the BCM2835 which has a ARM1176 core, and VERSATILEPB, which is a qemu board setup around the time RPI-B went in. Copy std.armv6 to std.armv7, even though that duplicates a lot of stuff. More work needs to be done to sort out the duplication. Differential Revision: https://reviews.freebsd.org/D12027 Notes: svn path=/head/; revision=324341
* Remove the MULTIDELAY option from arm. It's now enabled when PLATFORM isAndrew Turner2017-07-071-1/+0
| | | | | | | enabled. Notes: svn path=/head/; revision=320777
* Remove PLATFORM_SMP. It's unneeded as all configs with both PLATFORM andAndrew Turner2017-07-041-1/+0
| | | | | | | SMP use it so we can switch to the combination of these as the check. Notes: svn path=/head/; revision=320647
* Implement drivers for NVIDIA tegra124 display controller, HDMI sourceMichal Meloun2016-12-261-5/+4
| | | | | | | | | | | | | | | | | | | | and host1x module. Unfortunately, tegra124 SoC doesn't have 2D acceleration engine and 3D requires not yet started nouveau driver. These drivers forms a first non-x86 DRM2 enabled graphic stack. Note, there are 2 outstanding issues: - The code uses gross hack in order to be comply with OBJT_MGTDEVICE pager. (See tegra_bo_init_pager() in tegra_bo.c) - Due to improper(probably) refcounting in drm_gem_mmap_single() (in drm_gem.c), the gem objects are never released. I hope that I will be able to address both issues in finite time, but I don't want to touch x86 world now. MFC after: 1 month Notes: svn path=/head/; revision=310600
* Add NVIDIA Tegra XHCI driver and coresponding firmware blob.Michal Meloun2016-11-071-1/+3
| | | | | | | | MFC after: 3 weeks Approved by: core@ (NVIDIA license) Notes: svn path=/head/; revision=308391
* TEGRA: Add support for MULTIDELAY option.Michal Meloun2016-09-291-0/+1
| | | | Notes: svn path=/head/; revision=306442
* Remove HZ=<various> from all armv6 configs, put HZ=1000 in std.armv6.Ian Lepore2016-07-091-1/+0
| | | | | | | | | | | All armv6 processors are plenty fast enough for HZ=1000. No changes are made for older arm systems, because some chips are a bit wimpy for 1000 while others do fine, so it has to be set on a per-config basis. Notes: svn path=/head/; revision=302506
* Consolidate debugging options from all arm kernel configs to std.arm[v6].Ian Lepore2016-07-091-16/+0
| | | | Notes: svn path=/head/; revision=302505
* Add HWPMC_HOOKS to std.armv6 to make them availableBjoern A. Zeeb2016-05-161-1/+0
| | | | | | | | | | | | so the module could be loaded. Discussed with: andrew Reviewed by: andrew Sponsored by: DARPA/AFRL Differential Revision: https://reviews.freebsd.org/D6359 Notes: svn path=/head/; revision=299963
* ARM: Teach LINUX_BOOT_ABI to recognize DT blob.Michal Meloun2016-03-261-0/+1
| | | | | | | | | | This allow us to boot FreeBSD kernel (using uImage encapsulation) directly from U-boot using 'bootm' command or by Android fastboot loader. For now, kernel uImage must be marked as Linux, but we can add support for FreeBSD into U-Boot later. Notes: svn path=/head/; revision=297284
* TEGRA: Connect TEGRA124 to universe build.Michal Meloun2016-03-181-0/+156
Notes: svn path=/head/; revision=297026
generated by cgit v1.2.3 (git 2.25.1) at 2026-04-04 23:51:34 +0000