[Top] [All Lists]

Re: ipw2100: firmware problem

To: Pavel Machek <pavel@xxxxxx>
Subject: Re: ipw2100: firmware problem
From: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>
Date: Wed, 08 Jun 2005 16:46:01 -0500
Cc: Jeff Garzik <jgarzik@xxxxxxxxx>, Netdev list <netdev@xxxxxxxxxxx>, kernel list <linux-kernel@xxxxxxxxxxxxxxx>, "James P. Ketrenos" <ipw2100-admin@xxxxxxxxxxxxxxx>
In-reply-to: <20050608212707.GA2535@xxxxxxxxxx>
References: <20050608142310.GA2339@xxxxxxxxxx> <42A723D3.3060001@xxxxxxxxxxxxxxx> <20050608212707.GA2535@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050519
Pavel Machek wrote:

>>We've been looking into whether the initrd can have the firmware affixed
>>to the end w/ some magic bytes to identify it.  If it works, enhancing
>>the request_firmware to support both hotplug and an initrd approach may
>>be reasonable.
>That seems pretty ugly to me... imagine more than one driver does this
Not ideal, but not *that bad* if there is a standard way to stick the
data on the initrd image.  Its annoying to have to do it, but it does
enable the most usage models and allows the network to be brought up as
early as possible--which other components in the system may be relying on.

>Having a parameter to control this seems a bit too complex to me.
>How is 
>insmod ipw2100 enable=1
>different from
>insmod ipw2100
>iwconfig eth1 start_scanning_or_whatever
It defaults to enabled, so you just need to do:

    insmod ipw2100

and it will auto associate with an open network.  For the use case where
users want the device to load but not initialize, they can use

    insmod ipw2100 disable=1

If hotplug and firmware loading worked early in the init sequence, no
one would have issue with the current model; it works as users expect it
to work.  It magically finds and associates to networks, and your
network scripts can then kick off DHCP, all with little to no special
crafting or utility interfacing. 


<Prev in Thread] Current Thread [Next in Thread>