Bug 82507 - RFE: orinoco_cs: option _not_ to use the default ethXX name.
RFE: orinoco_cs: option _not_ to use the default ethXX name.
Product: Red Hat Public Beta
Classification: Retired
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
: FutureFeature
Depends On: 100622
  Show dependency treegraph
Reported: 2003-01-22 17:18 EST by Aleksey Nogin
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-19 11:57:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Quick patch to add names= parameter. (1.79 KB, patch)
2003-01-22 23:11 EST, Aleksey Nogin
no flags Details | Diff

  None (edit)
Description Aleksey Nogin 2003-01-22 17:18:32 EST
When a laptop has several removable net devices of different kind (wired/wirelss
in particular), it is much easier to handle the configuration when there is a
clear namespace separation. Both wavelan_cs (name=name1[,name2[,name3[,name4]]]
module param) and wvlan_cs (eth=0 module param) have the ability to use a device
name outside of the usual ethXX hierarchy. Now that the wvlan_cs driver is being
phased out by the orinoco_cs driver, it would be really nice if orinoco_cs
supported this feature as well.
Comment 1 Aleksey Nogin 2003-01-22 23:11:45 EST
Created attachment 89540 [details]
Quick patch to add names= parameter.

I wrote a quick patch that adds a names= module parameter (similar to that of
Comment 2 Bill Nottingham 2003-02-19 11:57:17 EST
This needs to be done upstream.
Comment 3 Aleksey Nogin 2003-02-19 20:51:40 EST
Well, without that change *RedHat* is the one removing the functionality that
used to exist in 8.0 (when the wvlan_cs driver was used). Also, I have no
experience with getting things into the kernel...

Also, the way I read https://bugzilla.redhat.com/bugzilla/bug_status.cgi,
"CLOSED UPSTREAM" means that it was actually reported upstream and so far it was

Note You need to log in before you can comment on or make changes to this bug.