linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alain RICHARD <alain.richard@equation.fr>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: benh 2.4.4-pre3, Titanium and AirPort
Date: Wed, 18 Apr 2001 18:46:00 +0200	[thread overview]
Message-ID: <20010418164600.23936@mailhost.mipsys.com> (raw)
In-Reply-To: <a05010409b70362ba0a13@[192.168.240.10]>


>
>- at module loading and without options, the driver recognize the
>card as "firmware ID 1F vendor 1 (lucent) version 7.25" and "WEP
>supported, "128"-bit key and then complains about enable to load
>module airport0 and airport1. I was thinking that airport cards where
>binded to airport0 and not eth0 by default and support only 40 bit
>mode ?

I noticed that 128 bit thing too after I did the 1.3 aiport update
from MacOS (it updated the card's firmware). No clue if the driver
is right about it or not.

The ethX by default can be changed with the eth=0 module option. It's
done that way in the original driver, I didn't change it.

>- the driver no longer seams to support the various setting as
>options for the module; what is now the recommended way of doing it ?

I removed the "enc" one that I added previously to avoid diff'ing
too much from the original source. You pass most options via
iwconfig. Just make sure to have the interface up as I keep the
card powered down when the interface is down to save power.

Ben..


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-04-18 16:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 11:04 benh 2.4.4-pre3, Titanium and AirPort Alain RICHARD
2001-04-18 11:52 ` Benjamin Herrenschmidt
2001-04-18 13:25   ` Alain RICHARD
2001-04-18 15:14     ` Michel Dänzer
2001-04-18 15:15     ` Benjamin Herrenschmidt
2001-04-18 16:21       ` Alain RICHARD
2001-04-18 16:46         ` Benjamin Herrenschmidt [this message]

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=20010418164600.23936@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=alain.richard@equation.fr \
    --cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).