FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2020-02-03T17:35:11Z 2020-02-03T17:35:11Z Warner Losh imp@FreeBSD.org 2020-02-03T17:35:11Z urn:sha1:58aa35d42975c298ca0adba705c042596303c9f5 Remove all sparc64 specific files Remove all sparc64 ifdefs Removee indireeect sparc64 ifdefs 2018-04-08T22:59:34Z Oleksandr Tymoshenko gonzo@FreeBSD.org 2018-04-08T22:59:34Z urn:sha1:217d17bcd3f525fbdf124cfbc926f8033da69805 OF_getprop_alloc takes element size argument and returns number of elements in the property. There are valid use cases for such behavior but mostly API consumers pass 1 as element size to get string properties. What API users would expect from OF_getprop_alloc is to be a combination of malloc + OF_getprop with the same semantic of return value. This patch modifies API signature to match these expectations. For the valid use cases with element size != 1 and to reduce modification scope new OF_getprop_alloc_multi function has been introduced that behaves the same way OF_getprop_alloc behaved prior to this patch. Reviewed by: ian, manu Differential Revision: https://reviews.freebsd.org/D14850 2017-11-27T15:10:39Z Pedro F. Giffuni pfg@FreeBSD.org 2017-11-27T15:10:39Z urn:sha1:6ce70ec7f9fa9a99bedcde196187307831315b37 Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task. The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts. 2016-05-18T23:39:31Z Oleksandr Tymoshenko gonzo@FreeBSD.org 2016-05-18T23:39:31Z urn:sha1:14131c0ba4a53ac9a4b7bd4e4fc49d2d1f3a03cc Reviewed by: marius 2016-03-22T22:25:08Z Justin Hibbits jhibbits@FreeBSD.org 2016-03-22T22:25:08Z urn:sha1:f8fd3fb51851136d6e74578405d3ba9b01f223b9 Missed a bunch from r297000. 2016-02-20T01:32:58Z Justin Hibbits jhibbits@FreeBSD.org 2016-02-20T01:32:58Z urn:sha1:7915adb56014e31e8ed8a4418060625c2e223fc0 This simplifies checking for default resource range for bus_alloc_resource(), and improves readability. This is part of, and related to, the migration of rman_res_t from u_long to uintmax_t. Discussed with: jhb Suggested by: marcel 2016-01-27T02:23:54Z Justin Hibbits jhibbits@FreeBSD.org 2016-01-27T02:23:54Z urn:sha1:2dd1bdf1834c53d048d3d9a7079b45afea5cecd7 Summary: Migrate to using the semi-opaque type rman_res_t to specify rman resources. For now, this is still compatible with u_long. This is step one in migrating rman to use uintmax_t for resources instead of u_long. Going forward, this could feasibly be used to specify architecture-specific definitions of resource ranges, rather than baking a specific integer type into the API. This change has been broken out to facilitate MFC'ing drivers back to 10 without breaking ABI. Reviewed By: jhb Sponsored by: Alex Perez/Inertial Computing Differential Revision: https://reviews.freebsd.org/D5075 2011-11-22T21:55:40Z Marius Strobl marius@FreeBSD.org 2011-11-22T21:55:40Z urn:sha1:848e30ff519e332f8f8d11ace65d86fb15470258 of kobj(9) from device drivers. 2011-10-02T23:22:38Z Marius Strobl marius@FreeBSD.org 2011-10-02T23:22:38Z urn:sha1:bda8e754a1ac3be73c297bf03353d56c7ab81ce3 - Implement bus_adjust_resource() methods as far as necessary and in non-PCI bridge drivers as far as feasible without rototilling them. - As NEW_PCIB does a layering violation by activating resources at layers above pci(4) without previously bubbling up their allocation there, move the assignment of bus tags and handles from the bus_alloc_resource() to the bus_activate_resource() methods like at least the other NEW_PCIB enabled architectures do. This is somewhat unfortunate as previously sparc64 (ab)used resource activation to indicate whether SYS_RES_MEMORY resources should be mapped into KVA, which is only necessary if their going to be accessed via the pointer returned from rman_get_virtual() but not for bus_space(9) as the later always uses physical access on sparc64. Besides wasting KVA if we always map in SYS_RES_MEMORY resources, a driver also may deliberately not map them in if the firmware already has done so, possibly in a special way. So in order to still allow a driver to decide whether a SYS_RES_MEMORY resource should be mapped into KVA we let it indicate that by calling bus_space_map(9) with BUS_SPACE_MAP_LINEAR as actually documented in the bus_space(9) page. This is implemented by allocating a separate bus tag per SYS_RES_MEMORY resource and passing the resource via the previously unused bus tag cookie so we later on can call rman_set_virtual() in sparc64_bus_mem_map(). As a side effect this now also allows to actually indicate that a SYS_RES_MEMORY resource should be mapped in as cacheable and/or read-only via BUS_SPACE_MAP_CACHEABLE and BUS_SPACE_MAP_READONLY respectively. - Do some minor cleanup like taking advantage of rman_init_from_resource(), factor out the common part of bus tag allocation into a newly added sparc64_alloc_bus_tag(), hook up some missing newbus methods and replace some homegrown versions with the generic counterparts etc. - While at it, let apb_attach() (which can't use the generic NEW_PCIB code as APB bridges just don't have the base and limit registers implemented) regarding the config space registers cached in pcib_softc and the SYSCTL reporting nodes set up. 2009-12-22T21:02:46Z Marius Strobl marius@FreeBSD.org 2009-12-22T21:02:46Z urn:sha1:1bba41a506f50fb28d77237ce31e23482f496d3e is that the JBus to EBus bridges share the interrupt controller of a sibling JBus to PCIe bridge (at least as far as the OFW device tree is concerned, in reality they are part of the same chip) so we have to probe and attach the latter first. That happens to be also the case due to the fact that the JBus to PCIe bridges appear first in the OFW device tree but it doesn't hurt to ensure the right order.