All of lore.kernel.org
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 3c59x and resume
Date: Mon, 25 Mar 2002 15:16:48 -0500	[thread overview]
Message-ID: <20020325201648.GH1853@ufies.org> (raw)
In-Reply-To: <1016914030.949.20.camel@phantasy> <Pine.LNX.3.96.1020325143511.4219B-100000@gatekeeper.tmr.com>

[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]

On Mon, Mar 25, 2002 at 02:44:31PM -0500, Bill Davidsen wrote:
> On 23 Mar 2002, Robert Love wrote:
> 
> > Ideally we'd have a dynamically created array for the cards and hash
> > into that, but, ugh, this is getting gross especially since 99% of us
> > have one card and never remove it.
> 
>   To address the problem of running out of id's, a bitmap of "id's in use"
> could be used, and number recycled. This is done infrequently and overhead
> is hardly a problem, although getting things released at suspect may be.

I agree but I believe this is not the real issue.

>   Getting the right options on the right card and the right card on the
> expected number is another problem. I fight that all the time on my
> laptop, with one NIC in the laptop and one in the dock. In spite of clear
> information in modules.conf giving which driver goes with each NIC (via
> alias), I don't get eth1 with no eth0 as I want, the first one is always
> eth0, loads the wrong driver when not docked, and then doesn't get
> initialized right by the startup scripts.
> 
>   I also have another NIC I put in a pcmcia slot to become a router on
> occasion, that also gets a random NIC number. Unfortunately it doesn't
> look like a trivial job to use the info in modules.conf to fix the general
> random numbering. The modules.conf interface seems to work in the wrong
> direction, what I think we want is "when you load this driver use this
> name", so eth2 could be the only NIC in the system under some conditions.

This is a subset of the problem I try to explain. 
In this case Greg has posted a nice solution a few mails ago (using a
userland tool called ifname IIRC).

Christophe

> 
> -- 
> bill davidsen <davidsen@tmr.com>
>   CTO, TMR Associates, Inc
> Doing interesting things with little computers since 1979.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8  F67A 8F45 2F1E D72C B41E

Cats seem go on the principle that it never does any harm to ask for
what you want. --Joseph Wood Krutch

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

  reply	other threads:[~2002-03-25 20:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-23 16:16 [PATCH] 3c59x and resume christophe barbé
2002-03-23 18:39 ` Andrew Morton
2002-03-23 20:06   ` Robert Love
2002-03-23 22:44     ` christophe barbé
2002-03-24  8:07       ` Greg KH
2002-03-24 14:25         ` christophe barbé
2002-03-25 18:01           ` Greg KH
2002-03-25 18:19             ` christophe barbé
2002-03-25 19:11               ` Greg KH
2002-03-25 20:27                 ` christophe barbé
2002-03-25 20:58                 ` christophe barbé
2002-03-25 11:34     ` Joachim Breuer
2002-03-25 11:53       ` Xavier Bestel
2002-03-25 21:31         ` Joachim Breuer
2002-03-25 19:44     ` Bill Davidsen
2002-03-25 20:16       ` christophe barbé [this message]
2002-03-26  0:57 ` Jeff Garzik
2002-03-26  1:40   ` christophe barbé
2002-03-26  4:10     ` Jeff Garzik
2002-03-26  4:39       ` christophe barbé
2002-03-26  4:50         ` Andrew Morton
2002-03-26 16:56           ` christophe barbé
2002-03-26 16:57             ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020325201648.GH1853@ufies.org \
    --to=christophe.barbe.ml@online.fr \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.