[mirror_ubuntu-artful-kernel.git] / drivers / block / paride / Kconfig

#
# PARIDE configuration
#
# PARIDE doesn't need PARPORT, but if PARPORT is configured as a module,
# PARIDE must also be a module.
# PARIDE only supports PC style parports. Tough for USB or other parports...

comment "Parallel IDE high-level drivers"
	depends on PARIDE

config PARIDE_PD
	tristate "Parallel port IDE disks"
	depends on PARIDE
	help
	  This option enables the high-level driver for IDE-type disk devices
	  connected through a parallel port. If you chose to build PARIDE
	  support into your kernel, you may answer Y here to build in the
	  parallel port IDE driver, otherwise you should answer M to build
	  it as a loadable module. The module will be called pd. You
	  must also have at least one parallel port protocol driver in your
	  system. Among the devices supported by this driver are the SyQuest
	  EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
	  hard drives from MicroSolutions.

config PARIDE_PCD
	tristate "Parallel port ATAPI CD-ROMs"
	depends on PARIDE
	select BLK_SCSI_REQUEST # only for the generic cdrom code
	---help---
	  This option enables the high-level driver for ATAPI CD-ROM devices
	  connected through a parallel port. If you chose to build PARIDE
	  support into your kernel, you may answer Y here to build in the
	  parallel port ATAPI CD-ROM driver, otherwise you should answer M to
	  build it as a loadable module. The module will be called pcd. You
	  must also have at least one parallel port protocol driver in your
	  system. Among the devices supported by this driver are the
	  MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
	  you have such a CD-ROM drive, you should also say Y or M to "ISO
	  9660 CD-ROM file system support" below, because that's the file
	  system used on CD-ROMs.

config PARIDE_PF
	tristate "Parallel port ATAPI disks"
	depends on PARIDE
	help
	  This option enables the high-level driver for ATAPI disk devices
	  connected through a parallel port. If you chose to build PARIDE
	  support into your kernel, you may answer Y here to build in the
	  parallel port ATAPI disk driver, otherwise you should answer M
	  to build it as a loadable module. The module will be called pf.
	  You must also have at least one parallel port protocol driver in
	  your system. Among the devices supported by this driver are the
	  MicroSolutions backpack PD/CD drive and the Imation Superdisk
	  LS-120 drive.

config PARIDE_PT
	tristate "Parallel port ATAPI tapes"
	depends on PARIDE
	help
	  This option enables the high-level driver for ATAPI tape devices
	  connected through a parallel port. If you chose to build PARIDE
	  support into your kernel, you may answer Y here to build in the
	  parallel port ATAPI disk driver, otherwise you should answer M
	  to build it as a loadable module. The module will be called pt.
	  You must also have at least one parallel port protocol driver in
	  your system. Among the devices supported by this driver is the
	  parallel port version of the HP 5GB drive.

config PARIDE_PG
	tristate "Parallel port generic ATAPI devices"
	depends on PARIDE
	---help---
	  This option enables a special high-level driver for generic ATAPI
	  devices connected through a parallel port. The driver allows user
	  programs, such as cdrtools, to send ATAPI commands directly to a
	  device.

	  If you chose to build PARIDE support into your kernel, you may
	  answer Y here to build in the parallel port generic ATAPI driver,
	  otherwise you should answer M to build it as a loadable module. The
	  module will be called pg.

	  You must also have at least one parallel port protocol driver in
	  your system.

	  This driver implements an API loosely related to the generic SCSI
	  driver. See <file:include/linux/pg.h>. for details.

	  You can obtain the most recent version of cdrtools from
	  <ftp://ftp.berlios.de/pub/cdrecord/>. Versions 1.6.1a3 and
	  later fully support this driver.

comment "Parallel IDE protocol modules"
	depends on PARIDE

config PARIDE_ATEN
	tristate "ATEN EH-100 protocol"
	depends on PARIDE
	help
	  This option enables support for the ATEN EH-100 parallel port IDE
	  protocol. This protocol is used in some inexpensive low performance
	  parallel port kits made in Hong Kong. If you chose to build PARIDE
	  support into your kernel, you may answer Y here to build in the
	  protocol driver, otherwise you should answer M to build it as a
	  loadable module. The module will be called aten. You must also
	  have a high-level driver for the type of device that you want to
	  support.

config PARIDE_BPCK
	tristate "MicroSolutions backpack (Series 5) protocol"
	depends on PARIDE
	---help---
	  This option enables support for the Micro Solutions BACKPACK
	  parallel port Series 5 IDE protocol.  (Most BACKPACK drives made
	  before 1999 were Series 5) Series 5 drives will NOT always have the
	  Series noted on the bottom of the drive. Series 6 drivers will.

	  In other words, if your BACKPACK drive doesn't say "Series 6" on the
	  bottom, enable this option.

	  If you chose to build PARIDE support into your kernel, you may
	  answer Y here to build in the protocol driver, otherwise you should
	  answer M to build it as a loadable module.  The module will be
	  called bpck.  You must also have a high-level driver for the type
	  of device that you want to support.

config PARIDE_BPCK6
	tristate "MicroSolutions backpack (Series 6) protocol"
	depends on PARIDE && !64BIT
	---help---
	  This option enables support for the Micro Solutions BACKPACK
	  parallel port Series 6 IDE protocol.  (Most BACKPACK drives made
	  after 1999 were Series 6) Series 6 drives will have the Series noted
	  on the bottom of the drive.  Series 5 drivers don't always have it
	  noted.

	  In other words, if your BACKPACK drive says "Series 6" on the
	  bottom, enable this option.

	  If you chose to build PARIDE support into your kernel, you may
	  answer Y here to build in the protocol driver, otherwise you should
	  answer M to build it as a loadable module.  The module will be
	  called bpck6.  You must also have a high-level driver for the type
	  of device that you want to support.

config PARIDE_COMM
	tristate "DataStor Commuter protocol"
	depends on PARIDE
	help
	  This option enables support for the Commuter parallel port IDE
	  protocol from DataStor. If you chose to build PARIDE support
	  into your kernel, you may answer Y here to build in the protocol
	  driver, otherwise you should answer M to build it as a loadable
	  module. The module will be called comm. You must also have
	  a high-level driver for the type of device that you want to support.

config PARIDE_DSTR
	tristate "DataStor EP-2000 protocol"
	depends on PARIDE
	help
	  This option enables support for the EP-2000 parallel port IDE
	  protocol from DataStor. If you chose to build PARIDE support
	  into your kernel, you may answer Y here to build in the protocol
	  driver, otherwise you should answer M to build it as a loadable
	  module. The module will be called dstr. You must also have
	  a high-level driver for the type of device that you want to support.

config PARIDE_FIT2
	tristate "FIT TD-2000 protocol"
	depends on PARIDE
	help
	  This option enables support for the TD-2000 parallel port IDE
	  protocol from Fidelity International Technology. This is a simple
	  (low speed) adapter that is used in some portable hard drives. If
	  you chose to build PARIDE support into your kernel, you may answer Y
	  here to build in the protocol driver, otherwise you should answer M
	  to build it as a loadable module. The module will be called ktti.
	  You must also have a high-level driver for the type of device that
	  you want to support.

config PARIDE_FIT3
	tristate "FIT TD-3000 protocol"
	depends on PARIDE
	help
	  This option enables support for the TD-3000 parallel port IDE
	  protocol from Fidelity International Technology. This protocol is
	  used in newer models of their portable disk, CD-ROM and PD/CD
	  devices. If you chose to build PARIDE support into your kernel, you
	  may answer Y here to build in the protocol driver, otherwise you
	  should answer M to build it as a loadable module. The module will be
	  called fit3. You must also have a high-level driver for the type
	  of device that you want to support.

config PARIDE_EPAT
	tristate "Shuttle EPAT/EPEZ protocol"
	depends on PARIDE
	help
	  This option enables support for the EPAT parallel port IDE protocol.
	  EPAT is a parallel port IDE adapter manufactured by Shuttle
	  Technology and widely used in devices from major vendors such as
	  Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
	  PARIDE support into your kernel, you may answer Y here to build in
	  the protocol driver, otherwise you should answer M to build it as a
	  loadable module. The module will be called epat. You must also
	  have a high-level driver for the type of device that you want to
	  support.

config PARIDE_EPATC8
	bool "Support c7/c8 chips"
	depends on PARIDE_EPAT
	help
	  This option enables support for the newer Shuttle EP1284 (aka c7 and
	  c8) chip. You need this if you are using any recent Imation SuperDisk
	  (LS-120) drive.

config PARIDE_EPIA
	tristate "Shuttle EPIA protocol"
	depends on PARIDE
	help
	  This option enables support for the (obsolete) EPIA parallel port
	  IDE protocol from Shuttle Technology. This adapter can still be
	  found in some no-name kits. If you chose to build PARIDE support
	  into your kernel, you may answer Y here to build in the protocol
	  driver, otherwise you should answer M to build it as a loadable
	  module. The module will be called epia. You must also have a
	  high-level driver for the type of device that you want to support.

config PARIDE_FRIQ
	tristate "Freecom IQ ASIC-2 protocol"
	depends on PARIDE
	help
	  This option enables support for version 2 of the Freecom IQ parallel
	  port IDE adapter.  This adapter is used by the Maxell Superdisk
	  drive.  If you chose to build PARIDE support into your kernel, you
	  may answer Y here to build in the protocol driver, otherwise you
	  should answer M to build it as a loadable module. The module will be
	  called friq. You must also have a high-level driver for the type
	  of device that you want to support.

config PARIDE_FRPW
	tristate "FreeCom power protocol"
	depends on PARIDE
	help
	  This option enables support for the Freecom power parallel port IDE
	  protocol. If you chose to build PARIDE support into your kernel, you
	  may answer Y here to build in the protocol driver, otherwise you
	  should answer M to build it as a loadable module. The module will be
	  called frpw. You must also have a high-level driver for the type
	  of device that you want to support.

config PARIDE_KBIC
	tristate "KingByte KBIC-951A/971A protocols"
	depends on PARIDE
	help
	  This option enables support for the KBIC-951A and KBIC-971A parallel
	  port IDE protocols from KingByte Information Corp. KingByte's
	  adapters appear in many no-name portable disk and CD-ROM products,
	  especially in Europe. If you chose to build PARIDE support into your
	  kernel, you may answer Y here to build in the protocol driver,
	  otherwise you should answer M to build it as a loadable module. The
	  module will be called kbic. You must also have a high-level driver
	  for the type of device that you want to support.

config PARIDE_KTTI
	tristate "KT PHd protocol"
	depends on PARIDE
	help
	  This option enables support for the "PHd" parallel port IDE protocol
	  from KT Technology. This is a simple (low speed) adapter that is
	  used in some 2.5" portable hard drives. If you chose to build PARIDE
	  support into your kernel, you may answer Y here to build in the
	  protocol driver, otherwise you should answer M to build it as a
	  loadable module. The module will be called ktti. You must also
	  have a high-level driver for the type of device that you want to
	  support.

config PARIDE_ON20
	tristate "OnSpec 90c20 protocol"
	depends on PARIDE
	help
	  This option enables support for the (obsolete) 90c20 parallel port
	  IDE protocol from OnSpec (often marketed under the ValuStore brand
	  name). If you chose to build PARIDE support into your kernel, you
	  may answer Y here to build in the protocol driver, otherwise you
	  should answer M to build it as a loadable module. The module will
	  be called on20. You must also have a high-level driver for the
	  type of device that you want to support.

config PARIDE_ON26
	tristate "OnSpec 90c26 protocol"
	depends on PARIDE
	help
	  This option enables support for the 90c26 parallel port IDE protocol
	  from OnSpec Electronics (often marketed under the ValuStore brand
	  name). If you chose to build PARIDE support into your kernel, you
	  may answer Y here to build in the protocol driver, otherwise you
	  should answer M to build it as a loadable module. The module will be
	  called on26. You must also have a high-level driver for the type
	  of device that you want to support.

#
Commit	Line	Data
1da177e4 LT	1	#
	2	# PARIDE configuration
	3	#
	4	# PARIDE doesn't need PARPORT, but if PARPORT is configured as a module,
482a579b	5	# PARIDE must also be a module.
6a19b41b	6	# PARIDE only supports PC style parports. Tough for USB or other parports...
1da177e4 LT	7
	8	comment "Parallel IDE high-level drivers"
	9	depends on PARIDE
	10
	11	config PARIDE_PD
	12	tristate "Parallel port IDE disks"
	13	depends on PARIDE
	14	help
	15	This option enables the high-level driver for IDE-type disk devices
	16	connected through a parallel port. If you chose to build PARIDE
	17	support into your kernel, you may answer Y here to build in the
	18	parallel port IDE driver, otherwise you should answer M to build
	19	it as a loadable module. The module will be called pd. You
	20	must also have at least one parallel port protocol driver in your
	21	system. Among the devices supported by this driver are the SyQuest
	22	EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
	23	hard drives from MicroSolutions.
	24
	25	config PARIDE_PCD
	26	tristate "Parallel port ATAPI CD-ROMs"
	27	depends on PARIDE
72148aec	28	select BLK_SCSI_REQUEST # only for the generic cdrom code
1da177e4 LT	29	---help---
	30	This option enables the high-level driver for ATAPI CD-ROM devices
	31	connected through a parallel port. If you chose to build PARIDE
	32	support into your kernel, you may answer Y here to build in the
	33	parallel port ATAPI CD-ROM driver, otherwise you should answer M to
	34	build it as a loadable module. The module will be called pcd. You
	35	must also have at least one parallel port protocol driver in your
	36	system. Among the devices supported by this driver are the
	37	MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
	38	you have such a CD-ROM drive, you should also say Y or M to "ISO
	39	9660 CD-ROM file system support" below, because that's the file
	40	system used on CD-ROMs.
	41
	42	config PARIDE_PF
	43	tristate "Parallel port ATAPI disks"
	44	depends on PARIDE
	45	help
	46	This option enables the high-level driver for ATAPI disk devices
	47	connected through a parallel port. If you chose to build PARIDE
	48	support into your kernel, you may answer Y here to build in the
	49	parallel port ATAPI disk driver, otherwise you should answer M
	50	to build it as a loadable module. The module will be called pf.
	51	You must also have at least one parallel port protocol driver in
	52	your system. Among the devices supported by this driver are the
	53	MicroSolutions backpack PD/CD drive and the Imation Superdisk
	54	LS-120 drive.
	55
	56	config PARIDE_PT
	57	tristate "Parallel port ATAPI tapes"
	58	depends on PARIDE
	59	help
	60	This option enables the high-level driver for ATAPI tape devices
	61	connected through a parallel port. If you chose to build PARIDE
	62	support into your kernel, you may answer Y here to build in the
	63	parallel port ATAPI disk driver, otherwise you should answer M
	64	to build it as a loadable module. The module will be called pt.
	65	You must also have at least one parallel port protocol driver in
	66	your system. Among the devices supported by this driver is the
	67	parallel port version of the HP 5GB drive.
	68
	69	config PARIDE_PG
	70	tristate "Parallel port generic ATAPI devices"
	71	depends on PARIDE
	72	---help---
	73	This option enables a special high-level driver for generic ATAPI
	74	devices connected through a parallel port. The driver allows user
	75	programs, such as cdrtools, to send ATAPI commands directly to a
	76	device.
	77
	78	If you chose to build PARIDE support into your kernel, you may
	79	answer Y here to build in the parallel port generic ATAPI driver,
	80	otherwise you should answer M to build it as a loadable module. The
	81	module will be called pg.
	82
	83	You must also have at least one parallel port protocol driver in
	84	your system.
	85
	86	This driver implements an API loosely related to the generic SCSI
	87	driver. See <file:include/linux/pg.h>. for details.
	88
	89	You can obtain the most recent version of cdrtools from
	90	<ftp://ftp.berlios.de/pub/cdrecord/>. Versions 1.6.1a3 and
	91	later fully support this driver.
	92
93	comment "Parallel IDE protocol modules"
94	depends on PARIDE
95
96	config PARIDE_ATEN
97	tristate "ATEN EH-100 protocol"
98	depends on PARIDE
99	help
100	This option enables support for the ATEN EH-100 parallel port IDE
101	protocol. This protocol is used in some inexpensive low performance
102	parallel port kits made in Hong Kong. If you chose to build PARIDE
103	support into your kernel, you may answer Y here to build in the
104	protocol driver, otherwise you should answer M to build it as a
105	loadable module. The module will be called aten. You must also
106	have a high-level driver for the type of device that you want to
107	support.
108
109	config PARIDE_BPCK
110	tristate "MicroSolutions backpack (Series 5) protocol"
111	depends on PARIDE
112	---help---
113	This option enables support for the Micro Solutions BACKPACK
114	parallel port Series 5 IDE protocol. (Most BACKPACK drives made
115	before 1999 were Series 5) Series 5 drives will NOT always have the
116	Series noted on the bottom of the drive. Series 6 drivers will.
117
118	In other words, if your BACKPACK drive doesn't say "Series 6" on the
119	bottom, enable this option.
120
121	If you chose to build PARIDE support into your kernel, you may
122	answer Y here to build in the protocol driver, otherwise you should
123	answer M to build it as a loadable module. The module will be
124	called bpck. You must also have a high-level driver for the type
125	of device that you want to support.
126
127	config PARIDE_BPCK6
128	tristate "MicroSolutions backpack (Series 6) protocol"
129	depends on PARIDE && !64BIT
130	---help---
131	This option enables support for the Micro Solutions BACKPACK
132	parallel port Series 6 IDE protocol. (Most BACKPACK drives made
133	after 1999 were Series 6) Series 6 drives will have the Series noted
134	on the bottom of the drive. Series 5 drivers don't always have it
135	noted.
136
137	In other words, if your BACKPACK drive says "Series 6" on the
138	bottom, enable this option.
139
140	If you chose to build PARIDE support into your kernel, you may
141	answer Y here to build in the protocol driver, otherwise you should
142	answer M to build it as a loadable module. The module will be
143	called bpck6. You must also have a high-level driver for the type
144	of device that you want to support.
145
146	config PARIDE_COMM
147	tristate "DataStor Commuter protocol"
148	depends on PARIDE
149	help
150	This option enables support for the Commuter parallel port IDE
151	protocol from DataStor. If you chose to build PARIDE support
152	into your kernel, you may answer Y here to build in the protocol
153	driver, otherwise you should answer M to build it as a loadable
154	module. The module will be called comm. You must also have
155	a high-level driver for the type of device that you want to support.
156
157	config PARIDE_DSTR
158	tristate "DataStor EP-2000 protocol"
159	depends on PARIDE
160	help
161	This option enables support for the EP-2000 parallel port IDE
162	protocol from DataStor. If you chose to build PARIDE support
163	into your kernel, you may answer Y here to build in the protocol
164	driver, otherwise you should answer M to build it as a loadable
165	module. The module will be called dstr. You must also have
166	a high-level driver for the type of device that you want to support.
167
168	config PARIDE_FIT2
169	tristate "FIT TD-2000 protocol"
170	depends on PARIDE
171	help
172	This option enables support for the TD-2000 parallel port IDE
173	protocol from Fidelity International Technology. This is a simple
174	(low speed) adapter that is used in some portable hard drives. If
175	you chose to build PARIDE support into your kernel, you may answer Y
176	here to build in the protocol driver, otherwise you should answer M
177	to build it as a loadable module. The module will be called ktti.
178	You must also have a high-level driver for the type of device that
179	you want to support.
180
181	config PARIDE_FIT3
182	tristate "FIT TD-3000 protocol"
183	depends on PARIDE
184	help
185	This option enables support for the TD-3000 parallel port IDE
186	protocol from Fidelity International Technology. This protocol is
187	used in newer models of their portable disk, CD-ROM and PD/CD
188	devices. If you chose to build PARIDE support into your kernel, you
189	may answer Y here to build in the protocol driver, otherwise you
190	should answer M to build it as a loadable module. The module will be
191	called fit3. You must also have a high-level driver for the type
192	of device that you want to support.
193
194	config PARIDE_EPAT
195	tristate "Shuttle EPAT/EPEZ protocol"
196	depends on PARIDE
197	help
198	This option enables support for the EPAT parallel port IDE protocol.
199	EPAT is a parallel port IDE adapter manufactured by Shuttle
200	Technology and widely used in devices from major vendors such as
201	Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
202	PARIDE support into your kernel, you may answer Y here to build in
203	the protocol driver, otherwise you should answer M to build it as a
204	loadable module. The module will be called epat. You must also
205	have a high-level driver for the type of device that you want to
206	support.
207
208	config PARIDE_EPATC8
0cb3d9c6 KC	209	bool "Support c7/c8 chips"
0cb3d9c6 KC	210	depends on PARIDE_EPAT
1da177e4 LT	211	help
	212	This option enables support for the newer Shuttle EP1284 (aka c7 and
	213	c8) chip. You need this if you are using any recent Imation SuperDisk
	214	(LS-120) drive.
	215
	216	config PARIDE_EPIA
	217	tristate "Shuttle EPIA protocol"
	218	depends on PARIDE
	219	help
	220	This option enables support for the (obsolete) EPIA parallel port
	221	IDE protocol from Shuttle Technology. This adapter can still be
	222	found in some no-name kits. If you chose to build PARIDE support
	223	into your kernel, you may answer Y here to build in the protocol
	224	driver, otherwise you should answer M to build it as a loadable
	225	module. The module will be called epia. You must also have a
	226	high-level driver for the type of device that you want to support.
	227
	228	config PARIDE_FRIQ
	229	tristate "Freecom IQ ASIC-2 protocol"
	230	depends on PARIDE
	231	help
	232	This option enables support for version 2 of the Freecom IQ parallel
	233	port IDE adapter. This adapter is used by the Maxell Superdisk
	234	drive. If you chose to build PARIDE support into your kernel, you
	235	may answer Y here to build in the protocol driver, otherwise you
	236	should answer M to build it as a loadable module. The module will be
	237	called friq. You must also have a high-level driver for the type
	238	of device that you want to support.
	239
	240	config PARIDE_FRPW
	241	tristate "FreeCom power protocol"
	242	depends on PARIDE
	243	help
	244	This option enables support for the Freecom power parallel port IDE
	245	protocol. If you chose to build PARIDE support into your kernel, you
	246	may answer Y here to build in the protocol driver, otherwise you
	247	should answer M to build it as a loadable module. The module will be
	248	called frpw. You must also have a high-level driver for the type
	249	of device that you want to support.
	250
	251	config PARIDE_KBIC
	252	tristate "KingByte KBIC-951A/971A protocols"
	253	depends on PARIDE
	254	help
	255	This option enables support for the KBIC-951A and KBIC-971A parallel
	256	port IDE protocols from KingByte Information Corp. KingByte's
	257	adapters appear in many no-name portable disk and CD-ROM products,
	258	especially in Europe. If you chose to build PARIDE support into your
	259	kernel, you may answer Y here to build in the protocol driver,
	260	otherwise you should answer M to build it as a loadable module. The
	261	module will be called kbic. You must also have a high-level driver
	262	for the type of device that you want to support.
	263
	264	config PARIDE_KTTI
	265	tristate "KT PHd protocol"
	266	depends on PARIDE
	267	help
	268	This option enables support for the "PHd" parallel port IDE protocol
	269	from KT Technology. This is a simple (low speed) adapter that is
	270	used in some 2.5" portable hard drives. If you chose to build PARIDE
	271	support into your kernel, you may answer Y here to build in the
	272	protocol driver, otherwise you should answer M to build it as a
	273	loadable module. The module will be called ktti. You must also
	274	have a high-level driver for the type of device that you want to
275	support.
276
277	config PARIDE_ON20
278	tristate "OnSpec 90c20 protocol"
279	depends on PARIDE
280	help
281	This option enables support for the (obsolete) 90c20 parallel port
282	IDE protocol from OnSpec (often marketed under the ValuStore brand
283	name). If you chose to build PARIDE support into your kernel, you
284	may answer Y here to build in the protocol driver, otherwise you
285	should answer M to build it as a loadable module. The module will
286	be called on20. You must also have a high-level driver for the
287	type of device that you want to support.
288
289	config PARIDE_ON26
290	tristate "OnSpec 90c26 protocol"
291	depends on PARIDE
292	help
293	This option enables support for the 90c26 parallel port IDE protocol
294	from OnSpec Electronics (often marketed under the ValuStore brand
295	name). If you chose to build PARIDE support into your kernel, you
296	may answer Y here to build in the protocol driver, otherwise you
297	should answer M to build it as a loadable module. The module will be
298	called on26. You must also have a high-level driver for the type
299	of device that you want to support.
300
301	#