staging: i4l: delete the whole thing (02bbd980) · Commits · e / devices / android_kernel_oneplus_sm8150

drivers/staging/Kconfig

+0 −2

Original line number	Diff line number	Diff line
		@@ -96,8 +96,6 @@ source "drivers/staging/wilc1000/Kconfig"

		source "drivers/staging/most/Kconfig"

		source "drivers/staging/i4l/Kconfig"

		source "drivers/staging/ks7010/Kconfig"

		source "drivers/staging/greybus/Kconfig"

drivers/staging/Makefile

+0 −1

Original line number	Diff line number	Diff line
		@@ -37,7 +37,6 @@ obj-$(CONFIG_FB_TFT) += fbtft/
		obj-$(CONFIG_FSL_MC_BUS) += fsl-mc/
		obj-$(CONFIG_WILC1000) += wilc1000/
		obj-$(CONFIG_MOST) += most/
		obj-$(CONFIG_ISDN_I4L) += i4l/
		obj-$(CONFIG_KS7010) += ks7010/
		obj-$(CONFIG_GREYBUS) += greybus/
		obj-$(CONFIG_BCM2835_VCHIQ) += vc04_services/

drivers/staging/i4l/Documentation/README.act2000

deleted100644 → 0

+0 −104

Original line number	Diff line number	Diff line
		$Id: README.act2000,v 1.3 2000/08/06 09:22:51 armin Exp $

		This document describes the ACT2000 driver for the
		IBM Active 2000 ISDN card.

		There are 3 Types of this card available. A ISA-, MCA-, and PCMCIA-Bus
		Version. Currently, only the ISA-Bus version of the card is supported.
		However MCA and PCMCIA will follow soon.

		The ISA-Bus Version uses 8 IO-ports. The base port address has to be set
		manually using the DIP switches.

		Setting up the DIP switches for the IBM Active 2000 ISDN card:

		Note: S5 and S6 always set off!

		S1 S2 S3 S4 Base-port
		on on on on 0x0200 (Factory default)
		off on on on 0x0240
		on off on on 0x0280
		off off on on 0x02c0
		on on off on 0x0300
		off on off on 0x0340
		on off off on 0x0380
		on on on off 0xcfe0
		off on on off 0xcfa0
		on off on off 0xcf60
		off off on off 0xcf20
		on on off off 0xcee0
		off on off off 0xcea0
		on off off off 0xce60
		off off off off Card disabled

		IRQ is configured by software. Possible values are:

		3, 5, 7, 10, 11, 12, 15 and none (polled mode)


		The ACT2000 driver may either be built into the kernel or as a module.
		Initialization depends on how the driver is built:

		Driver built into the kernel:

		The ACT2000 driver can be configured using the commandline-feature while
		loading the kernel with LILO or LOADLIN. It accepts the following syntax:

		act2000=b,p,i[,idstring]

		where

		b = Bus-Type (1=ISA, 2=MCA, 3=PCMCIA)
		p = portbase (-1 means autoprobe)
		i = Interrupt (-1 means use next free IRQ, 0 means polled mode)

		The idstring is an arbitrary string used for referencing the card
		by the actctrl tool later.

		Defaults used, when no parameters given at all:

		1,-1,-1,""

		which means: Autoprobe for an ISA card, use next free IRQ, let the
		ISDN linklevel fill the IdString (usually "line0" for the first card).

		If you like to use more than one card, you can use the program
		"actctrl" from the utility-package to configure additional cards.

		Using the "actctrl"-utility, portbase and irq can also be changed
		during runtime. The D-channel protocol is configured by the "dproto"
		option of the "actctrl"-utility after loading the firmware into the
		card's memory using the "actctrl"-utility.

		Driver built as module:

		The module act2000.o can be configured during modprobe (insmod) by
		appending its parameters to the modprobe resp. insmod commandline.
		The following syntax is accepted:

		act_bus=b act_port=p act_irq=i act_id=idstring

		where b, p, i and idstring have the same meanings as the parameters
		described for the builtin version above.

		Using the "actctrl"-utility, the same features apply to the modularized
		version as to the kernel-builtin one. (i.e. loading of firmware and
		configuring the D-channel protocol)

		Loading the firmware into the card:

		The firmware is supplied together with the isdn4k-utils package. It
		can be found in the subdirectory act2000/firmware/

		Assuming you have installed the utility-package correctly, the firmware
		will be downloaded into the card using the following command:

		actctrl -d idstring load /etc/isdn/bip11.btl

		where idstring is the Name of the card, given during insmod-time or
		(for kernel-builtin driver) on the kernel commandline. If only one
		ISDN card is used, the -d isdstrin may be omitted.

		For further documentation (adding more IBM Active 2000 cards), refer to
		the manpage actctrl.8 which is included in the isdn4k-utils package.

drivers/staging/i4l/Documentation/README.icn

deleted100644 → 0

+0 −148

Original line number	Diff line number	Diff line
		$Id: README.icn,v 1.7 2000/08/06 09:22:51 armin Exp $

		You can get the ICN-ISDN-card from:

		Thinking Objects Software GmbH
		Versbacher Röthe 159
		97078 Würzburg
		Tel: +49 931 2877950
		Fax: +49 931 2877951

		email info@think.de
		WWW http:/www.think.de


		The card communicates with the PC by two interfaces:
		1. A range of 4 successive port-addresses, whose base address can be
		configured with the switches.
		2. A memory window with 16KB-256KB size, which can be setup in 16k steps
		over the whole range of 16MB. Isdn4linux only uses a 16k window.
		The base address of the window can be configured when loading
		the lowlevel-module (see README). If using more than one card,
		all cards are mapped to the same window and activated as needed.

		Setting up the IO-address dipswitches for the ICN-ISDN-card:

		Two types of cards exist, one with dip-switches and one with
		hook-switches.

		1. Setting for the card with hook-switches:

		(0 = switch closed, 1 = switch open)

		S3 S2 S1 Base-address
		0 0 0 0x300
		0 0 1 0x310
		0 1 0 0x320 (Default for isdn4linux)
		0 1 1 0x330
		1 0 0 0x340
		1 0 1 0x350
		1 1 0 0x360
		1 1 1 NOT ALLOWED!

		2. Setting for the card with dip-switches:

		(0 = switch closed, 1 = switch open)

		S1 S2 S3 S4 Base-Address
		0 0 0 0 0x300
		0 0 0 1 0x310
		0 0 1 0 0x320 (Default for isdn4linux)
		0 0 1 1 0x330
		0 1 0 0 0x340
		0 1 0 1 0x350
		0 1 1 0 0x360
		0 1 1 1 NOT ALLOWED!
		1 0 0 0 0x308
		1 0 0 1 0x318
		1 0 1 0 0x328
		1 0 1 1 0x338
		1 1 0 0 0x348
		1 1 0 1 0x358
		1 1 1 0 0x368
		1 1 1 1 NOT ALLOWED!

		The ICN driver may be built into the kernel or as a module. Initialization
		depends on how the driver is built:

		Driver built into the kernel:

		The ICN driver can be configured using the commandline-feature while
		loading the kernel with LILO or LOADLIN. It accepts the following syntax:

		icn=p,m[,idstring1[,idstring2]]

		where

		p = portbase (default: 0x320)
		m = shared memory (default: 0xd0000)

		When using the ICN double card (4B), you MUST define TWO idstrings.
		idstring must start with a character! There is no way for the driver
		to distinguish between a 2B and 4B type card. Therefore, by supplying
		TWO idstrings, you tell the driver that you have a 4B installed.

		If you like to use more than one card, you can use the program
		"icnctrl" from the utility-package to configure additional cards.
		You need to configure shared memory only once, since the icn-driver
		maps all cards into the same address-space.

		Using the "icnctrl"-utility, portbase and shared memory can also be
		changed during runtime.

		The D-channel protocol is configured by loading different firmware
		into the card's memory using the "icnctrl"-utility.


		Driver built as module:

		The module icn.o can be configured during "insmod'ing" it by
		appending its parameters to the insmod-commandline. The following
		syntax is accepted:

		portbase=p membase=m icn_id=idstring [icn_id2=idstring2]

		where p, m, idstring1 and idstring2 have the same meanings as the
		parameters described for the kernel-version above.

		When using the ICN double card (4B), you MUST define TWO idstrings.
		idstring must start with a character! There is no way for the driver
		to distinguish between a 2B and 4B type card. Therefore, by supplying
		TWO idstrings, you tell the driver that you have a 4B installed.

		Using the "icnctrl"-utility, the same features apply to the modularized
		version like to the kernel-builtin one.

		The D-channel protocol is configured by loading different firmware
		into the card's memory using the "icnctrl"-utility.

		Loading the firmware into the card:

		The firmware is supplied together with the isdn4k-utils package. It
		can be found in the subdirectory icnctrl/firmware/

		There are 3 files:

		loadpg.bin - Image of the bootstrap loader.
		pc_1t_ca.bin - Image of firmware for german 1TR6 protocol.
		pc_eu_ca.bin - Image if firmware for EDSS1 (Euro-ISDN) protocol.

		Assuming you have installed the utility-package correctly, the firmware
		will be downloaded into the 2B-card using the following command:

		icnctrl -d Idstring load /etc/isdn/loadpg.bin /etc/isdn/pc_XX_ca.bin

		where XX is either "1t" or "eu", depending on the D-Channel protocol
		used on your S0-bus and Idstring is the Name of the card, given during
		insmod-time or (for kernel-builtin driver) on the kernel commandline.

		To load a 4B-card, the same command is used, except a second firmware
		file is appended to the commandline of icnctrl.

		-> After downloading firmware, the two LEDs at the back cover of the card
		(ICN-4B: 4 LEDs) must be blinking intermittently now. If a connection
		is up, the corresponding led is lit continuously.

		For further documentation (adding more ICN-cards), refer to the manpage
		icnctrl.8 which is included in the isdn4k-utils package.

drivers/staging/i4l/Documentation/README.pcbit

deleted100644 → 0

+0 −40

Original line number	Diff line number	Diff line
		------------------------------------------------------------------------------
		README file for the PCBIT-D Device Driver.
		------------------------------------------------------------------------------

		The PCBIT is a Euro ISDN adapter manufactured in Portugal by Octal and
		developed in cooperation with Portugal Telecom and Inesc.
		The driver interfaces with the standard kernel isdn facilities
		originally developed by Fritz Elfert in the isdn4linux project.

		The common versions of the pcbit board require a firmware that is
		distributed (and copyrighted) by the manufacturer. To load this
		firmware you need "pcbitctl" available on the standard isdn4k-utils
		package or in the pcbit package available in:

		ftp://ftp.di.fc.ul.pt/pub/systems/Linux/isdn

		Known Limitations:

		- The board reset procedure is at the moment incorrect and will only
		allow you to load the firmware after a hard reset.

		- Only HDLC in B-channels is supported at the moment. There is no
		current support for X.25 in B or D channels nor LAPD in B
		channels. The main reason is that these two other protocol modes have,
		to my knowledge, very little use. If you want to see them implemented
		do send me a mail.

		- The driver often triggers errors in the board that I and the
		manufacturer believe to be caused by bugs in the firmware. The current
		version includes several procedures for error recovery that should
		allow normal operation. Plans for the future include cooperation with
		the manufacturer in order to solve this problem.

		Information/hints/help can be obtained in the linux isdn
		mailing list (isdn4linux@listserv.isdn4linux.de) or directly from me.

		regards,
		Pedro.

		<roque@di.fc.ul.pt>