Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
d2a03c2f
Commit
d2a03c2f
authored
Dec 06, 2002
by
Martin Schwidefsky
Committed by
Linus Torvalds
Dec 06, 2002
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[PATCH] s390: chandev.
Remove channel device layer.
parent
c7d8d8ce
Changes
3
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
1 addition
and
3345 deletions
+1
-3345
drivers/s390/Kconfig
drivers/s390/Kconfig
+0
-39
drivers/s390/misc/Makefile
drivers/s390/misc/Makefile
+1
-2
drivers/s390/misc/chandev.c
drivers/s390/misc/chandev.c
+0
-3304
No files found.
drivers/s390/Kconfig
View file @
d2a03c2f
...
...
@@ -524,47 +524,8 @@ config FDDI
comment "S/390 network device drivers"
depends on NETDEVICES
config CHANDEV
bool "Channel Device Configuration"
depends on NETDEVICES
---help---
The channel device layer is a layer to provide a consistent
interface for configuration & default machine check (devices
appearing & disappearing) handling on Linux for s/390 & z/Series
channel devices.
s/390 & z/Series channel devices include among others
lcs (the most common ethernet/token ring/fddi standard on
zSeries)
ctc/escon hi speed like serial link standard on zSeries
claw used to talk to cisco routers.
qeth gigabit ethernet.
These devices use two channels one read & one write for
configuration & communication (& a third channel, the data
channel the case of gigabit ethernet). The motivation
behind developing this layer was that there was a lot of
duplicate code among the channel device drivers for
configuration.
Also the lcs & ctc drivers tended to fight over
3088/08's & 3088/1F's which could be either 2216/3172
channel attached lcs compatible devices or escon/ctc pipes
had to be configured separately as they couldn't autodetect,
this is now simplified by doing the configuration in a single
place (the channel device layer).
This layer isn't invasive & it is quite okay to use channel
drivers which don't use the channel device layer in
conjunction with drivers which do.
For more info see the chandev manpage usually distributed in
<file:Documentation/s390/chandev.8> in the Linux source tree.
config HOTPLUG
bool
depends on CHANDEV
default y
---help---
Say Y here if you want to plug devices into your computer while
...
...
drivers/s390/misc/Makefile
View file @
d2a03c2f
...
...
@@ -2,7 +2,6 @@
# S/390 miscellaneous devices
#
obj-$(CONFIG_CHANDEV)
+=
chandev.o
export-objs
+=
chandev.o
# placeholder for stuff to come...
include
$(TOPDIR)/Rules.make
drivers/s390/misc/chandev.c
deleted
100644 → 0
View file @
c7d8d8ce
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment