From caffd5cdfb26cb4851799aa09212423c20c1ade2 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Thu, 25 Aug 2011 18:56:12 +0000 Subject: [PATCH] --- yaml --- r: 275201 b: refs/heads/master c: 9c2416adac986d7d90814d7985a0ea80ebea416f h: refs/heads/master i: 275199: cd56b3bbe1d809a8429a28d4e75cef940cb34c41 v: v3 --- [refs] | 2 +- trunk/Documentation/DocBook/drm.tmpl | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index d06efbd3e9f7..949019b529ae 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: bb49a6a1f3303f9cf23a19f403c9b90cdff0e7da +refs/heads/master: 9c2416adac986d7d90814d7985a0ea80ebea416f diff --git a/trunk/Documentation/DocBook/drm.tmpl b/trunk/Documentation/DocBook/drm.tmpl index 7001937f6b7d..03321ebaf4a7 100644 --- a/trunk/Documentation/DocBook/drm.tmpl +++ b/trunk/Documentation/DocBook/drm.tmpl @@ -369,9 +369,9 @@ using the pci_map_rom() call, a convenience function that takes care of mapping the actual ROM, whether it has been shadowed into memory (typically at address 0xc0000) or exists - on the PCI device in the ROM BAR. Note that once you've - mapped the ROM and extracted any necessary information, be - sure to unmap it; on many devices the ROM address decoder is + on the PCI device in the ROM BAR. Note that after the ROM + has been mapped and any necessary information has been extracted, + it should be unmapped; on many devices the ROM address decoder is shared with other BARs, so leaving it mapped can cause undesired behavior like hangs or memory corruption.