Fix typos in Documentation/: 'N'-'P'

---

  The NAND and NOR support has been merged from the linux-mtd project.

  Any prolbems, see http://www.linux-mtd.infradead.org/ for more

  Any problems, see http://www.linux-mtd.infradead.org/ for more

  information or up-to-date versions of linux-mtd.

at a time during a write batch.  It is this characteristic that can make

the anticipatory scheduler perform anomalously with controllers supporting

TCQ, or with hardware striped RAID devices. Setting the antic_expire

queue paramter (see below) to zero disables this behavior, and the anticipatory

scheduler behaves essentially like the deadline scheduler.

queue parameter (see below) to zero disables this behavior, and the 

anticipatory scheduler behaves essentially like the deadline scheduler.

When read anticipation is enabled (antic_expire is not zero), reads

are dispatched to the disk controller one at a time.

of ii.  Just keeping issue order suffices.  Ancient SCSI

controllers/drives and IDE drives are in this category.

2. Forced flushing to physcial medium

2. Forced flushing to physical medium

Again, if you're not gonna do synchronization with disk drives (dang,

it sounds even more appealing now!), the reason you use I/O barriers

If set to '1' then the frequency decreases as quickly as it increases,

if set to '2' it decreases at half the rate of the increase.

ignore_nice_load: this parameter takes a value of '0' or '1', when set

to '0' (its default) then all processes are counted towards towards the

'cpu utilisation' value.   When set to '1' then processes that are

ignore_nice_load: this parameter takes a value of '0' or '1'. When

set to '0' (its default), all processes are counted towards the

'cpu utilisation' value.  When set to '1', the processes that are

run with a 'nice' value will not count (and thus be ignored) in the

overal usage calculation.  This is useful if you are running a CPU

overall usage calculation.  This is useful if you are running a CPU

intensive calculation on your laptop that you do not care how long it

takes to complete as you can 'nice' it and prevent it from taking part

in the deciding process of whether to increase your CPU frequency.

In packet update mode the packet size has to be given before any packets can

be downloaded. It is done as below

echo XXXX > /sys/devices/platform/dell_rbu/packet_size

In the packet update mechanism, the user neesd to create a new file having

In the packet update mechanism, the user needs to create a new file having

packets of data arranged back to back. It can be done as follows

The user creates packets header, gets the chunk of the BIOS image and

places it next to the packetheader; now, the packetheader + BIOS image chunk

NOTE:

This driver requires a patch for firmware_class.c which has the modified

request_firmware_nowait function.

Also after updating the BIOS image an user mdoe application neeeds to execute

code which message the BIOS update request to the BIOS. So on the next reboot

Also after updating the BIOS image a user mode application needs to execute

code which sends the BIOS update request to the BIOS. So on the next reboot

the BIOS knows about the new image downloaded and it updates itself.

Also don't unload the rbu drive if the image has to be updated.

Also don't unload the rbu driver if the image has to be updated.