staging: remove i2o subsystem (4a72a7af) · Commits · e / devices / android_kernel_oneplus_sm8150

drivers/staging/Kconfig

+0 −2

Original line number	Original line	Diff line number	Diff line
	@@ -108,8 +108,6 @@ source "drivers/staging/clocking-wizard/Kconfig"

	source "drivers/staging/fbtft/Kconfig"		source "drivers/staging/fbtft/Kconfig"

	source "drivers/staging/i2o/Kconfig"

	source "drivers/staging/fsl-mc/Kconfig"		source "drivers/staging/fsl-mc/Kconfig"

	endif # STAGING		endif # STAGING

drivers/staging/Makefile

+0 −1

Original line number	Original line	Diff line number	Diff line
	@@ -46,5 +46,4 @@ obj-$(CONFIG_CRYPTO_SKEIN) += skein/
	obj-$(CONFIG_UNISYSSPAR) += unisys/		obj-$(CONFIG_UNISYSSPAR) += unisys/
	obj-$(CONFIG_COMMON_CLK_XLNX_CLKWZRD) += clocking-wizard/		obj-$(CONFIG_COMMON_CLK_XLNX_CLKWZRD) += clocking-wizard/
	obj-$(CONFIG_FB_TFT) += fbtft/		obj-$(CONFIG_FB_TFT) += fbtft/
	obj-$(CONFIG_I2O) += i2o/
	obj-$(CONFIG_FSL_MC_BUS) += fsl-mc/		obj-$(CONFIG_FSL_MC_BUS) += fsl-mc/

drivers/staging/i2o/Kconfig

deleted100644 → 0

+0 −120

Original line number	Original line	Diff line number	Diff line
	menuconfig I2O
	tristate "I2O device support"
	depends on PCI
	---help---
	The Intelligent Input/Output (I2O) architecture allows hardware
	drivers to be split into two parts: an operating system specific
	module called the OSM and an hardware specific module called the
	HDM. The OSM can talk to a whole range of HDM's, and ideally the
	HDM's are not OS dependent. This allows for the same HDM driver to
	be used under different operating systems if the relevant OSM is in
	place. In order for this to work, you need to have an I2O interface
	adapter card in your computer. This card contains a special I/O
	processor (IOP), thus allowing high speeds since the CPU does not
	have to deal with I/O.

	If you say Y here, you will get a choice of interface adapter
	drivers and OSM's with the following questions.

	To compile this support as a module, choose M here: the
	modules will be called i2o_core.

	If unsure, say N.

	if I2O

	config I2O_LCT_NOTIFY_ON_CHANGES
	bool "Enable LCT notification"
	default y
	---help---
	Only say N here if you have a I2O controller from SUN. The SUN
	firmware doesn't support LCT notification on changes. If this option
	is enabled on such a controller the driver will hang up in a endless
	loop. On all other controllers say Y.

	If unsure, say Y.

	config I2O_EXT_ADAPTEC
	bool "Enable Adaptec extensions"
	default y
	---help---
	Say Y for support of raidutils for Adaptec I2O controllers. You also
	have to say Y to "I2O Configuration support", "I2O SCSI OSM" below
	and to "SCSI generic support" under "SCSI device configuration".

	config I2O_EXT_ADAPTEC_DMA64
	bool "Enable 64-bit DMA"
	depends on I2O_EXT_ADAPTEC && ( 64BIT \|\| HIGHMEM64G )
	default y
	---help---
	Say Y for support of 64-bit DMA transfer mode on Adaptec I2O
	controllers.
	Note: You need at least firmware version 3709.

	config I2O_CONFIG
	tristate "I2O Configuration support"
	depends on VIRT_TO_BUS
	---help---
	Say Y for support of the configuration interface for the I2O adapters.
	If you have a RAID controller from Adaptec and you want to use the
	raidutils to manage your RAID array, you have to say Y here.

	To compile this support as a module, choose M here: the
	module will be called i2o_config.

	Note: If you want to use the new API you have to download the
	i2o_config patch from http://i2o.shadowconnect.com/

	config I2O_CONFIG_OLD_IOCTL
	bool "Enable ioctls (OBSOLETE)"
	depends on I2O_CONFIG
	default y
	---help---
	Enables old ioctls.

	config I2O_BUS
	tristate "I2O Bus Adapter OSM"
	---help---
	Include support for the I2O Bus Adapter OSM. The Bus Adapter OSM
	provides access to the busses on the I2O controller. The main purpose
	is to rescan the bus to find new devices.

	To compile this support as a module, choose M here: the
	module will be called i2o_bus.

	config I2O_BLOCK
	tristate "I2O Block OSM"
	depends on BLOCK
	---help---
	Include support for the I2O Block OSM. The Block OSM presents disk
	and other structured block devices to the operating system. If you
	are using an RAID controller, you could access the array only by
	the Block OSM driver. But it is possible to access the single disks
	by the SCSI OSM driver, for example to monitor the disks.

	To compile this support as a module, choose M here: the
	module will be called i2o_block.

	config I2O_SCSI
	tristate "I2O SCSI OSM"
	depends on SCSI
	---help---
	Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
	I2O controller. You can use both the SCSI and Block OSM together if
	you wish. To access a RAID array, you must use the Block OSM driver.
	But you could use the SCSI OSM driver to monitor the single disks.

	To compile this support as a module, choose M here: the
	module will be called i2o_scsi.

	config I2O_PROC
	tristate "I2O /proc support"
	---help---
	If you say Y here and to "/proc file system support", you will be
	able to read I2O related information from the virtual directory
	/proc/i2o.

	To compile this support as a module, choose M here: the
	module will be called i2o_proc.

	endif # I2O

drivers/staging/i2o/Makefile

deleted100644 → 0

+0 −16

Original line number	Original line	Diff line number	Diff line
	#
	# Makefile for the kernel I2O OSM.
	#
	# Note : at this point, these files are compiled on all systems.
	# In the future, some of these should be built conditionally.
	#

	i2o_core-y += iop.o driver.o device.o debug.o pci.o exec-osm.o memory.o
	i2o_bus-y += bus-osm.o
	i2o_config-y += config-osm.o
	obj-$(CONFIG_I2O) += i2o_core.o
	obj-$(CONFIG_I2O_CONFIG)+= i2o_config.o
	obj-$(CONFIG_I2O_BUS) += i2o_bus.o
	obj-$(CONFIG_I2O_BLOCK) += i2o_block.o
	obj-$(CONFIG_I2O_SCSI) += i2o_scsi.o
	obj-$(CONFIG_I2O_PROC) += i2o_proc.o

drivers/staging/i2o/README

deleted100644 → 0

+0 −98

Original line number	Original line	Diff line number	Diff line

	Linux I2O Support (c) Copyright 1999 Red Hat Software
	and others.

	This program is free software; you can redistribute it and/or
	modify it under the terms of the GNU General Public License
	as published by the Free Software Foundation; either version
	2 of the License, or (at your option) any later version.

	AUTHORS (so far)

	Alan Cox, Building Number Three Ltd.
	Core code, SCSI and Block OSMs

	Steve Ralston, LSI Logic Corp.
	Debugging SCSI and Block OSM

	Deepak Saxena, Intel Corp.
	Various core/block extensions
	/proc interface, bug fixes
	Ioctl interfaces for control
	Debugging LAN OSM

	Philip Rumpf
	Fixed assorted dumb SMP locking bugs

	Juha Sievanen, University of Helsinki Finland
	LAN OSM code
	/proc interface to LAN class
	Bug fixes
	Core code extensions

	Auvo Häkkinen, University of Helsinki Finland
	LAN OSM code
	/Proc interface to LAN class
	Bug fixes
	Core code extensions

	Taneli Vähäkangas, University of Helsinki Finland
	Fixes to i2o_config

	CREDITS

	This work was made possible by

	Red Hat Software
	Funding for the Building #3 part of the project

	Symbios Logic (Now LSI)
	Host adapters, hints, known to work platforms when I hit
	compatibility problems

	BoxHill Corporation
	Loan of initial FibreChannel disk array used for development work.

	European Commission
	Funding the work done by the University of Helsinki

	SysKonnect
	Loan of FDDI and Gigabit Ethernet cards

	ASUSTeK
	Loan of I2O motherboard

	STATUS:

	o The core setup works within limits.
	o The scsi layer seems to almost work.
	I'm still chasing down the hang bug.
	o The block OSM is mostly functional
	o LAN OSM works with FDDI and Ethernet cards.

	TO DO:

	General:
	o Provide hidden address space if asked
	o Long term message flow control
	o PCI IOP's without interrupts are not supported yet
	o Push FAIL handling into the core
	o DDM control interfaces for module load etc
	o Add I2O 2.0 support (Deffered to 2.5 kernel)

	Block:
	o Multiple major numbers
	o Read ahead and cache handling stuff. Talk to Ingo and people
	o Power management
	o Finish Media changers

	SCSI:
	o Find the right way to associate drives/luns/busses

	Lan:
	o Performance tuning
	o Test Fibre Channel code

	Tape:
	o Anyone seen anything implementing this ?
	(D.S: Will attempt to do so if spare cycles permit)