[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1237145146.4209.45.camel@hashbaz.i.decadent.org.uk>
Date: Sun, 15 Mar 2009 19:25:46 +0000
From: Ben Hutchings <bhutchings@...arflare.com>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, gospo@...hat.com,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
Subject: Re: [net-next PATCH 11/11] ixgbe: Add documentation for the driver
On Sat, 2009-03-14 at 01:15 -0700, Jeff Kirsher wrote:
> From: PJ Waskiewicz <peter.p.waskiewicz.jr@...el.com>
>
> Documentation for the ixgbe driver in the kernel docs area is missing.
> This adds that documentation.
[...]
> +2. Load the module:
> +
> +# modprobe ixgbe
> +
> + The insmod command can be used if the full
> + path to the driver module is specified. For example:
> +
> + insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/ixgbe/ixgbe.ko
> +
> + With 2.6 based kernels also make sure that older ixgbe drivers are
> + removed from the kernel, before loading the new module:
> +
> + rmmod ixgbe; modprobe ixgbe
> +
> +3. Assign an IP address to the interface by entering the following, where
> + x is the interface number:
> +
> + ifconfig ethx <IP_address>
> +
> +4. Verify that the interface works. Enter the following, where <IP_address>
> + is the IP address for another machine on the same subnet as the interface
> + that is being tested:
> +
> + ping <IP_address>
[...]
This is the same as for any network driver, so there is no point
including it in driver-specific documentation.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists