02 Nov, 2017
1 commit
-
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.By default all files without license information are under the default
license of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if
Reviewed-by: Philippe Ombredanne
Reviewed-by: Thomas Gleixner
Signed-off-by: Greg Kroah-Hartman
29 Oct, 2015
3 commits
-
This allows saving a little of space when not using ssb on Broadcom SoC.
Signed-off-by: Rafał Miłecki
Signed-off-by: Kalle Valo -
This cleans main.c a bit and will allow us to compile SoC related code
conditionally in the future.Signed-off-by: Rafał Miłecki
Signed-off-by: Kalle Valo -
ssb bus can be found on various "host" devices like PCI/PCMCIA/SDIO.
Every ssb bus contains cores AKA devices.
The main idea is to have ssb driver scan/initialize bus and register
ready-to-use cores. This way ssb drivers can operate on a single core
mostly ignoring underlaying details.For some reason PCMCIA support was split between ssb and b43. We got
PCMCIA host device probing in b43, then bus scanning in ssb and then
wireless core probing back in b43. The truth is it's very unlikely we
will ever see PCMCIA ssb device with no 802.11 core but I still don't
see any advantage of the current architecture.With proposed change we get the same functionality with a simpler
architecture, less Kconfig symbols, one killed EXPORT and hopefully
cleaner b43. Since b43 supports both: ssb & bcma I prefer to keep ssb
specific code in ssb driver.This mostly moves code from b43's pcmcia.c to bridge_pcmcia_80211.c. We
already use similar solution with b43_pci_bridge.c. I didn't use "b43"
in name of this new file as in theory any driver can operate on wireless
core.Signed-off-by: Rafał Miłecki
Signed-off-by: Kalle Valo
10 Jan, 2013
1 commit
-
Signed-off-by: Rafał Miłecki
Signed-off-by: John W. Linville
22 Nov, 2012
1 commit
-
Register a GPIO driver to access the GPIOs provided by the chip.
The GPIOs of the SoC should always start at 0 and the other GPIOs could
start at a random position. There is just one SoC in a system and when
they start at 0 the number is predictable.Signed-off-by: Hauke Mehrtens
Patchwork: http://patchwork.linux-mips.org/patch/4591
Acked-by: Florian Fainelli
09 Sep, 2009
1 commit
-
Add support for communicating with a Sonics Silicon Backplane through a
SDIO interface, as found in the Nintendo Wii WLAN daughter card.The Nintendo Wii WLAN card includes a custom Broadcom 4318 chip with
a SDIO host interface.Signed-off-by: Albert Herranz
Signed-off-by: Michael Buesch
Signed-off-by: John W. Linville
10 Feb, 2009
1 commit
-
This adds support for the SSB PMU.
A PMU is found on Low-Power devices.Signed-off-by: Michael Buesch
Signed-off-by: John W. Linville
14 Mar, 2008
1 commit
-
This adds support for reading/writing the SPROM invariants
for PCMCIA based devices.Signed-off-by: Michael Buesch
Signed-off-by: John W. Linville
07 Mar, 2008
1 commit
-
This adds the Gigabit Ethernet driver for the SSB
Gigabit Ethernet core. This driver actually is a frontend to
the Tigon3 driver. So the real work is done by tg3.
This device is used in the Linksys WRT350N.Signed-off-by: Michael Buesch
Signed-off-by: John W. Linville
28 Feb, 2008
1 commit
-
The bridge code was unnecessary enabled by the b44
driver, but it prevents the bcm43xx driver from
being loaded, as the bridge claims the same pci ids.Now we enable the birdge only if the b43{legacy}
drivers are selected.Signed-off-by: Alexey Zaytsev
Acked-by: Larry Finger
Signed-off-by: John W. Linville
21 Feb, 2008
1 commit
-
This fixes the SSB watchdog access for devices without a chipcommon.
These devices have the watchdog on the extif.Signed-off-by: Michael Buesch
Signed-off-by: John W. Linville
11 Oct, 2007
1 commit
-
SSB is an SoC bus used in a number of embedded devices. The most
well-known of these devices is probably the Linksys WRT54G, but there
are others as well. The bus is also used internally on the BCM43xx
and BCM44xx devices from Broadcom.This patch also includes support for SSB ID tables in modules, so
that SSB drivers can be loaded automatically.Signed-off-by: Michael Buesch
Signed-off-by: John W. Linville
Signed-off-by: David S. Miller