summaryrefslogtreecommitdiffstats
path: root/sys/arm/conf/NOTES
Commit message (Collapse)AuthorAgeFilesLines
* MFC 303522,303647,303860,303880,304168,304169,304170,304479,304485,305549:jhb2016-10-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Chelsio T4/T5 VF driver. 303522: Various fixes to the t4/5nex character device. - Remove null open/close methods. - Don't set d_flags to 0 explicitly. - Remove t5_cdevsw as the .d_name member isn't really used and doesn't warrant a separate cdevsw just for the name. - Use ENOTTY as the error value for an unknown ioctl request. - Use make_dev_s() to close race with setting si_drv1. 303647: Store the offset of the KDOORBELL and GTS registers in the softc. VF devices use a different register layout than PF devices. Storing the offset in a value in the softc allows code to be shared between the PF and VF drivers. 303860: Reserve an adapter flag IS_VF to mark VF devices vs PF devices. 303880: Track the base absolute ID of ingress and egress queues. Use this to map an absolute queue ID to a logical queue ID in interrupt handlers. For the regular cxgbe/cxl drivers this should be a no-op as the base absolute ID should be zero. VF devices have a non-zero base absolute ID and require this change. While here, export the absolute ID of egress queues via a sysctl. 304168: Make SGE parameter handling more VF-friendly. Add fields to hold the SGE control register and free list buffer sizes to the sge_params structure. Populate these new fields in t4_init_sge_params() for PF devices and change t4_read_chip_settings() to pull these values out of the params structure instead of reading registers directly. This will permit t4_read_chip_settings() to be reused for VF devices which cannot read SGE registers directly. While here, move the call to t4_init_sge_params() to get_params__post_init(). The VF driver will populate the SGE parameters structure via a different method before calling t4_read_chip_settings(). 304169: Update mailbox writes to work with VF devices. - Use alternate register locations for the data and control registers for VFs. - Do a dummy read to force the writes to the mailbox data registers to post before the write to the control register on VFs. - Do not check the PCI-e firmware register for errors on VFs. 304170: Add support for register dumps on VF devices. - Add handling of VF register sets to t4_get_regs_len() and t4_get_regs(). - While here, use t4_get_regs_len() in the ioctl handler for regdump instead of inlining it. 304479: Add structures for VF-specific adapter parameters. While here, mark which parameters are PF-specific and which are VF-specific. 304485: Reorder sysctls so that nodes shared with the VF driver are added first. This permits a single early return for VF devices in the routines that add sysctl nodes. 305549: Chelsio T4/T5 VF driver. The cxgbev/cxlv driver supports Virtual Function devices for Chelsio T4 and T4 adapters. The VF devices share most of their code with the existing PF4 driver (cxgbe/cxl) and as such the VF device driver currently depends on the PF4 driver. Similar to the cxgbe/cxl drivers, the VF driver includes a t4vf/t5vf PCI device driver that attaches to the VF device. It then creates child cxgbev/cxlv devices representing ports assigned to the VF. By default, the PF driver assigns a single port to each VF. t4vf_hw.c contains VF-specific routines from the shared code used to fetch VF-specific parameters from the firmware. t4_vf.c contains the VF-specific PCI device driver and includes its own attach routine. VF devices are required to use a different firmware request when transmitting packets (which in turn requires a different CPL message to encapsulate messages). This alternate firmware request does not permit chaining multiple packets in a single message, so each packet results in a firmware request. In addition, the different CPL message requires more detailed information when enabling hardware checksums, so parse_pkt() on VF devices must examine L2 and L3 headers for all packets (not just TSO packets) for VF devices. Finally, L2 checksums on non-UDP/non-TCP packets do not work reliably (the firmware trashes the IPv4 fragment field), so IPv4 checksums for such packets are calculated in software. Most of the other changes in the non-VF-specific code are to expose various variables and functions private to the PF driver so that they can be used by the VF driver. Note that a limited subset of cxgbetool functions are supported on VF devices including register dumps, scheduler classes, and clearing of statistics. In addition, TOE is not supported on VF devices, only for the PF interfaces. Sponsored by: Chelsio Communications
* Move 'device pci' for the PCI bus driver to the MI NOTES file.jhb2016-04-291-2/+0
| | | | | The PCI bus was already listed in all of the MD NOTES files and the driver should at least compile on all platforms.
* Remove vestiges of IEEE-488/GPIB drivers removed in r276214.jhb2016-04-291-2/+0
|
* Remove old COMPAT_FREEBSD options from the ARM kernel configs. We replacedandrew2016-03-161-0/+4
| | | | | | | the ABI in 10.0, and have removed support for the old ABI in 11. As such any of these options to provide compatibility prior to 10 are unneeded. Sponsored by: ABT Systems Ltd
* Create the twsi device option in preparation to move the driver to a commonandrew2016-02-141-0/+3
| | | | | | location. The device is also found in Allwinner SoCs. Sponsored by: ABT Systems Ltd
* ARM: Remove support for xscale i80219 and i80321 CPUs. We haven't singlemmel2016-02-031-2/+0
| | | | supported config/board with these CPUs.
* Remove the arm KERNPHYSADDR option as it is no longer used. The makeandrew2015-12-221-1/+0
| | | | option is still in existance as it is used to build the trampoline code.
* ARM: option PPC_PROBE_CHIPSET is applicable only for x86. Don't enable itmmel2015-12-151-0/+1
| | | | | | for ARM LINT config. Approved by: kib (mentor)
* Start to remove support for the XScale i80321. As far as I can tell nobodyandrew2015-10-281-4/+0
| | | | uses this which makes it difficult to support.
* Start to remove support for the Samsung s3c24x0 SoCs by removing the kernelandrew2015-10-271-2/+0
| | | | config, and support from NOTES.
* Implement the lockstat provider using SDT(9) instead of the custom providermarkj2015-07-191-1/+0
| | | | | | | | in lockstat.ko. This means that lockstat probes now have typed arguments and will utilize SDT probe hot-patching support when it arrives. Reviewed by: gnn Differential Revision: https://reviews.freebsd.org/D2993
* Allow DTrace to be compiled-in to the kernel.br2015-06-101-0/+23
| | | | | | | | This will require for AArch64 as we dont have modules yet. Sponsored by: HEIF5 Sponsored by: ARM Ltd. Differential Revision: https://reviews.freebsd.org/D1997
* Plug cxgbe(4) back into !powerpc && !arm builds, instead of building itnp2015-01-161-0/+1
| | | | on amd64 only.
* Move the ARM Samsung s3c2xx0 support files into the samsung directory, togavin2014-09-251-1/+1
| | | | | | match other platforms. Discussed with: andrew
* Move sys/arm/econa to sys/arm/cavium/cns11xx.rpaulo2014-04-071-1/+1
|
* Remove all traces of support for ARM chips prior to the arm9 series. Weian2014-03-091-3/+0
| | | | | | | never actually ran on these chips (other than using SA1 support in an emulator to do the early porting to FreeBSD long long ago). The clutter and complexity of some of this code keeps getting in the way of other maintenance, so it's time to go.
* We need nand now that the boards reference it.imp2014-01-201-0/+1
|
* Remove the remaining references to the now-obsolete sheevaplug config files,ian2013-01-271-1/+0
| | | | | | | which have been replaced by the generic db88f6xxx config which works for all kirkwood-series chips. Approved by: cognet (mentor)
* Add NOTES and Makefile in order to generate LINT. NOTES contains prettymarcel2012-11-271-0/+90
much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
OpenPOWER on IntegriCloud