search for: 907d

...retrieved! ------------------------- I never used LDAP, though, and never intended to do so. Anyone knows how to fix this? Thanks and bye. Dominik Geisel -- I don't know with what weapons World War III will be fought, but World War IV will be fought with sticks and stones. -Albert Einstein 907D F135 0EF8 5A4D 633B 805D 25E7 478B 1322 4688

...2: * Don't just program the DMA notifier offset, make sure to actually perform an update v3: * Don't call UPDATE() * Actually read the correct notifier fields, as apparently the CAPABILITIES_DONE field lives in a different location than the main NV_DISP_CORE_NOTIFIER_1 field. As well, 907d+ use a different CAPABILITIES_DONE field then pre-907d cards. Signed-off-by: Lyude Paul <lyude at redhat.com> Fixes: 4a2cb4181b07 ("drm/nouveau/kms/nv50-: Probe SOR and PIOR caps for DP interlacing support") Cc: <stable at vger.kernel.org> # v5.8+ --- drivers/gpu/drm/nouve...

...2: * Don't just program the DMA notifier offset, make sure to actually perform an update v3: * Don't call UPDATE() * Actually read the correct notifier fields, as apparently the CAPABILITIES_DONE field lives in a different location than the main NV_DISP_CORE_NOTIFIER_1 field. As well, 907d+ use a different CAPABILITIES_DONE field then pre-907d cards. v4: * Don't forget to check the return value of core507d_read_caps() v5: * Get rid of NV50_DISP_CAPS_NTFY[14], use NV50_DISP_CORE_NTFY * Disable notifier after calling GetCapabilities() Signed-off-by: Lyude Paul <lyude at redha...

...ES. return code = -1 Sorta kinda working...I think: 81rc2# ./net drs showrepl T3 dos charset 'CP850' unavailable - using ASCII Default-First-Site-Name\T3 DSA Options: 0x00000001 Site Options: (none) DSA object GUID: fdaf2ed0-3630-41ba-96a6-554f0316bf75 DSA invocationID: 5b89c863-f8b0-4310-907d-20e978c9fd98 ==== INBOUND NEIGHBORS ==== DC=tms3,DC=com Default-First-Site-Name\DEATHKNIGHT via RPC DSA object GUID: 58bfc826-cd9f-445d-b6e5-ab7314ba0671 Last attempt @ Wed Jul 7 20:59:24 2010 PDT was successful. 0 consecutive failure(s)....

...2: * Don't just program the DMA notifier offset, make sure to actually perform an update v3: * Don't call UPDATE() * Actually read the correct notifier fields, as apparently the CAPABILITIES_DONE field lives in a different location than the main NV_DISP_CORE_NOTIFIER_1 field. As well, 907d+ use a different CAPABILITIES_DONE field then pre-907d cards. v4: * Don't forget to check the return value of core507d_read_caps() Signed-off-by: Lyude Paul <lyude at redhat.com> Fixes: 4a2cb4181b07 ("drm/nouveau/kms/nv50-: Probe SOR and PIOR caps for DP interlacing support")...

These didn't apply cleanly to v5.8, so here's a backported version. Lyude Paul (2): drm/nouveau/kms/nv50-: Program notifier offset before requesting disp caps drm/nouveau/kms/nv50-: Log SOR/PIOR caps drivers/gpu/drm/nouveau/dispnv50/core507d.c | 25 ++++++++++++++++----- drivers/gpu/drm/nouveau/dispnv50/disp.c | 10 +++++++++ 2 files changed, 29 insertions(+), 6 deletions(-)