Merge with /home/shaggy/git/linus-clean/

  It has many tips and hints!

The aoetools are userland programs that are designed to work with this

driver.  The aoetools are on sourceforge.

  http://aoetools.sourceforge.net/

The scripts in this Documentation/aoe directory are intended to

document the use of the driver and are not necessary if you install

the aoetools.

CREATING DEVICE NODES

  Users of udev should find the block device nodes created

  "echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to

  limit ATA over Ethernet traffic to eth2 and eth4.  AoE traffic from

  untrusted networks should be ignored as a matter of security.

  untrusted networks should be ignored as a matter of security.  See

  also the aoe_iflist driver option described below.

  "echo > /dev/etherd/discover" tells the driver to find out what AoE

  devices are available.

  These character devices may disappear and be replaced by sysfs

  counterparts, so distribution maintainers are encouraged to create

  scripts that use these devices.

  counterparts.  Using the commands in aoetools insulates users from

  these implementation details.

  The block devices are named like this:

  through which we are communicating with the remote AoE device.

  There is a script in this directory that formats this information

  in a convenient way.

  in a convenient way.  Users with aoetools can use the aoe-stat

  command.

  root@makki root# sh Documentation/aoe/status.sh 

     e10.0            eth3              up

      e4.7            eth1              up

      e4.8            eth1              up

      e4.9            eth1              up

  Use /sys/module/aoe/parameters/aoe_iflist (or better, the driver

  option discussed below) instead of /dev/etherd/interfaces to limit

  AoE traffic to the network interfaces in the given

  whitespace-separated list.  Unlike the old character device, the

  sysfs entry can be read from as well as written to.

  It's helpful to trigger discovery after setting the list of allowed

  interfaces.  The aoetools package provides an aoe-discover script

  for this purpose.  You can also directly use the

  /dev/etherd/discover special file described above.

DRIVER OPTIONS

  There is a boot option for the built-in aoe driver and a

  corresponding module parameter, aoe_iflist.  Without this option,

  all network interfaces may be used for ATA over Ethernet.  Here is a

  usage example for the module parameter.

    modprobe aoe_iflist="eth1 eth3"

	echo "$me Error: sysfs is not mounted" 1>&2

	exit 1

}

test -z "`lsmod | grep '^aoe'`" && {

	echo  "$me Error: aoe module is not loaded" 1>&2

	exit 1

}

for d in `ls -d $sysd/block/etherd* 2>/dev/null | grep -v p` end; do

	# maybe ls comes up empty, so we use "end"

pci_for_each_bus()		Superseded by pci_find_next_bus()

pci_find_device()		Superseded by pci_get_device()

pci_find_subsys()		Superseded by pci_get_subsys()

pci_find_slot()			Superseded by pci_get_slot()

pcibios_find_class()		Superseded by pci_get_class()

pci_find_class()		Superseded by pci_get_class()

pci_(read|write)_*_nodev()	Superseded by pci_bus_(read|write)_*()

These functions are intended for use by individual drivers, and are defined in 

struct pci_driver:

        int  (*save_state) (struct pci_dev *dev, u32 state);

        int  (*suspend) (struct pci_dev *dev, u32 state);

        int  (*suspend) (struct pci_dev *dev, pm_message_t state);

        int  (*resume) (struct pci_dev *dev);

        int  (*enable_wake) (struct pci_dev *dev, u32 state, int enable);

save_state

----------

Usage:

if (dev->driver && dev->driver->save_state)

	dev->driver->save_state(dev,state);

The driver should use this callback to save device state. It should take into

account the current state of the device and the requested state in order to

avoid any unnecessary operations.

For example, a video card that supports all 4 states (D0-D3), all controller

context is preserved when entering D1, but the screen is placed into a low power

state (blanked). 

The driver can also interpret this function as a notification that it may be

entering a sleep state in the near future. If it knows that the device cannot

enter the requested state, either because of lack of support for it, or because

the device is middle of some critical operation, then it should fail.

This function should not be used to set any state in the device or the driver

because the device may not actually enter the sleep state (e.g. another driver

later causes causes a global state transition to fail).

Note that in intermediate low power states, a device's I/O and memory spaces may

be disabled and may not be available in subsequent transitions to lower power

states.

        int  (*enable_wake) (struct pci_dev *dev, pci_power_t state, int enable);

suspend

	  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;

	  newer boards don't support it.  If you have ISA, say Y, otherwise N.

config ISA_DMA_API

	bool

	default y

config PCI

	bool

	depends on !ALPHA_JENSEN