Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

  <partintro>

    <para>

      This first part of the DRM Developer's Guide documents core DRM code,

      helper libraries for writting drivers and generic userspace interfaces

      helper libraries for writing drivers and generic userspace interfaces

      exposed by DRM drivers.

    </para>

  </partintro>

      providing a solution to every graphics memory-related problems, GEM

      identified common code between drivers and created a support library to

      share it. GEM has simpler initialization and execution requirements than

      TTM, but has no video RAM management capabitilies and is thus limited to

      TTM, but has no video RAM management capabilities and is thus limited to

      UMA devices.

    </para>

    <sect2>

	    vice versa. Drivers must use the kernel dma-buf buffer sharing framework

	    to manage the PRIME file descriptors. Similar to the mode setting

	    API PRIME is agnostic to the underlying buffer object manager, as

	    long as handles are 32bit unsinged integers.

	    long as handles are 32bit unsigned integers.

	  </para>

	  <para>

	    While non-GEM drivers must implement the operations themselves, GEM

      first create properties and then create and associate individual instances

      of those properties to objects. A property can be instantiated multiple

      times and associated with different objects. Values are stored in property

      instances, and all other property information are stored in the propery

      instances, and all other property information are stored in the property

      and shared between all instances of the property.

    </para>

    <para>

  <sect1>

    <title>Legacy Support Code</title>

    <para>

      The section very brievely covers some of the old legacy support code which

      The section very briefly covers some of the old legacy support code which

      is only used by old DRM drivers which have done a so-called shadow-attach

      to the underlying device instead of registering as a real driver. This

      also includes some of the old generic buffer mangement and command

      also includes some of the old generic buffer management and command

      submission code. Do not use any of this in new and modern drivers.

    </para>

With most FireWire controllers, memory access is limited to the low 4 GB

of physical address space.  This can be a problem on IA64 machines where

memory is located mostly above that limit, but it is rarely a problem on

more common hardware such as x86, x86-64 and PowerPC.  However, at least

Agere/LSI FW643e and FW643e2 controllers are known to support access to

physical addresses above 4 GB.

more common hardware such as x86, x86-64 and PowerPC.

At least LSI FW643e and FW643e2 controllers are known to support access to

physical addresses above 4 GB, but this feature is currently not enabled by

Linux.

Together with a early initialization of the OHCI-1394 controller for debugging,

this facility proved most useful for examining long debugs logs in the printk

   compliant, they are based on TI PCILynx chips and require drivers for Win-

   dows operating systems.

   The mentioned kernel log message contains ">4 GB phys DMA" in case of

   OHCI-1394 controllers which support accesses above this limit.

   The mentioned kernel log message contains the string "physUB" if the

   controller implements a writable Physical Upper Bound register.  This is

   required for physical DMA above 4 GB (but not utilized by Linux yet).

2) Establish a working FireWire cable connection:

    error_if_no_space|queue_if_no_space

	If the pool runs out of data or metadata space, the pool will

	either queue or error the IO destined to the data device.  The

	default is to queue the IO until more space is added.

	default is to queue the IO until more space is added or the

	'no_space_timeout' expires.  The 'no_space_timeout' dm-thin-pool

	module parameter can be used to change this timeout -- it

	defaults to 60 seconds but may be disabled using a value of 0.

iii) Messages

- Edit your Thunderbird config settings so that it won't use format=flowed.

  Go to "edit->preferences->advanced->config editor" to bring up the

  thunderbird's registry editor, and set "mailnews.send_plaintext_flowed" to

  "false".

  thunderbird's registry editor.

- Disable HTML Format: Set "mail.identity.id1.compose_html" to "false".

- Set "mailnews.send_plaintext_flowed" to "false"

- Enable "preformat" mode: Set "editor.quotesPreformatted" to "true".

- Set "mailnews.wraplength" from "72" to "0"

- Enable UTF8: Set "prefs.converted-to-utf8" to "true".

- "View" > "Message Body As" > "Plain Text"

- Install the "toggle wordwrap" extension.  Download the file from:

    https://addons.mozilla.org/thunderbird/addon/2351/

  Then go to "tools->add ons", select "install" at the bottom of the screen,

  and browse to where you saved the .xul file.  This adds an "Enable

  Wordwrap" entry under the Options menu of the message composer.

- "View" > "Character Encoding" > "Unicode (UTF-8)"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

TkRat (GUI)

The "intr" line gives counts of interrupts  serviced since boot time, for each

of the  possible system interrupts.   The first  column  is the  total of  all

interrupts serviced; each  subsequent column is the  total for that particular

interrupt.

interrupts serviced  including  unnumbered  architecture specific  interrupts;

each  subsequent column is the  total for that particular numbered interrupt.

Unnumbered interrupts are not shown, only summed into the total.

The "ctxt" line gives the total number of context switches across all CPUs.