Attachment 124334 Details for Bug 93354 – attachment-31088-0.html

attachment-31088-0.html

attachment-31088-0.html (text/html), 3.40 KB, created by guy goode on 2016-06-05 16:34:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: guy goode

Created: 2016-06-05 16:34:03 UTC

Size: 3.40 KB

patch

obsolete

><div dir="ltr"><div>This patch was originally intended to support a form of gpu output source provider which made my hp envy laptop work with 950 nvidia/intel ramdac type graphics design.Â  Since then, there have been patches made to render/xrandr and I am not interested in porting the design forwards.Â  HP and NVIDIA are the beneficiary of this patch, and they did not seem interested in even looking.Â  Today, to use this device you must fallback to just the intel ramdac, and lose the gpu entirely.Â  too bad.<br><br></div>but thanks for looking.Â  your the first person to even look.<br><br><div>incidentally, the --retain option repairs a problem where the update is applied in the server, and then immediately replaced with the default config, which removes the effect of the xrandr reconfig.Â  --retain causes the change to stick, and therefore be effective.<br></div><div><br></div><div>Like I said, this change is of low value since HP / NVIDIA support is not interested in it.<br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 5, 2016 at 6:24 AM,  <span dir="ltr">&lt;<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>    
>      
>    
>    <div><span><a href="mailto:peter@lekensteyn.nl" title="Peter Wu &lt;peter@lekensteyn.nl&gt;" target="_blank"> <span>Peter Wu</span></a>
></span> changed
>          <a title="NEW - fixes to allow use of xrandr for setprovideroutputsource type configs" href="https://bugs.freedesktop.org/show_bug.cgi?id=93354" target="_blank">bug 93354</a>
>          <br>
>             <table border="1" cellpadding="8" cellspacing="0">
>          <tbody><tr>
>            <th>What</th>
>            <th>Removed</th>
>            <th>Added</th>
>          </tr>
>
>         <tr>
>           <td style="text-align:right">CC</td>
>           <td>
>               Â 
>           </td>
>           <td><a href="mailto:peter@lekensteyn.nl" target="_blank">peter@lekensteyn.nl</a>
>           </td>
>         </tr></tbody></table>
>      <p>
>        </p><div>
>            <b><a title="NEW - fixes to allow use of xrandr for setprovideroutputsource type configs" href="https://bugs.freedesktop.org/show_bug.cgi?id=93354#c1" target="_blank">Comment # 1</a>
>              on <a title="NEW - fixes to allow use of xrandr for setprovideroutputsource type configs" href="https://bugs.freedesktop.org/show_bug.cgi?id=93354" target="_blank">bug 93354</a>
>              from <span><a href="mailto:peter@lekensteyn.nl" title="Peter Wu &lt;peter@lekensteyn.nl&gt;" target="_blank"> <span>Peter Wu</span></a>
></span></b>
>        <pre>Not a dev, but your chances of getting this merged will increase if you do not
>put your patches in a tarball but send them to the xorg-devel list with an
>appropriate commit message.
>
>Based on the indentation, the xrrprovider.c change in x.patch seems reasonable,
>it handles clients which use a different byte order. No idea about the
>rrmonitor.c changes though.
>
>About y.patch, as a user I read the manual page and still have no idea what the
>&quot;--retain&quot; option does.</pre>
>        </div>
>      <p></p>
>
>
>      <hr>
>      <span>You are receiving this mail because:</span>
>
>      <ul>
>          <li>You reported the bug.</li>
>      </ul>
>    </div>
></blockquote></div><br></div>

<div dir="ltr"><div>This patch was originally intended to support a form of gpu output source provider which made my hp envy laptop work with 950 nvidia/intel ramdac type graphics design.Â  Since then, there have been patches made to render/xrandr and I am not interested in porting the design forwards.Â  HP and NVIDIA are the beneficiary of this patch, and they did not seem interested in even looking.Â  Today, to use this device you must fallback to just the intel ramdac, and lose the gpu entirely.Â  too bad.<br><br></div>but thanks for looking.Â  your the first person to even look.<br><br><div>incidentally, the --retain option repairs a problem where the update is applied in the server, and then immediately replaced with the default config, which removes the effect of the xrandr reconfig.Â  --retain causes the change to stick, and therefore be effective.<br></div><div><br></div><div>Like I said, this change is of low value since HP / NVIDIA support is not interested in it.<br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 5, 2016 at 6:24 AM,  <span dir="ltr">&lt;<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    
      
    
    <div><span><a href="mailto:peter@lekensteyn.nl" title="Peter Wu &lt;peter@lekensteyn.nl&gt;" target="_blank"> <span>Peter Wu</span></a>
</span> changed
          <a title="NEW - fixes to allow use of xrandr for setprovideroutputsource type configs" href="https://bugs.freedesktop.org/show_bug.cgi?id=93354" target="_blank">bug 93354</a>
          <br>
             <table border="1" cellpadding="8" cellspacing="0">
          <tbody><tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right">CC</td>
           <td>
               Â 
           </td>
           <td><a href="mailto:peter@lekensteyn.nl" target="_blank">peter@lekensteyn.nl</a>
           </td>
         </tr></tbody></table>
      <p>
        </p><div>
            <b><a title="NEW - fixes to allow use of xrandr for setprovideroutputsource type configs" href="https://bugs.freedesktop.org/show_bug.cgi?id=93354#c1" target="_blank">Comment # 1</a>
              on <a title="NEW - fixes to allow use of xrandr for setprovideroutputsource type configs" href="https://bugs.freedesktop.org/show_bug.cgi?id=93354" target="_blank">bug 93354</a>
              from <span><a href="mailto:peter@lekensteyn.nl" title="Peter Wu &lt;peter@lekensteyn.nl&gt;" target="_blank"> <span>Peter Wu</span></a>
</span></b>
        <pre>Not a dev, but your chances of getting this merged will increase if you do not
put your patches in a tarball but send them to the xorg-devel list with an
appropriate commit message.

Based on the indentation, the xrrprovider.c change in x.patch seems reasonable,
it handles clients which use a different byte order. No idea about the
rrmonitor.c changes though.

About y.patch, as a user I read the manual page and still have no idea what the
&quot;--retain&quot; option does.</pre>
        </div>
      <p></p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You reported the bug.</li>
      </ul>
    </div>
</blockquote></div><br></div>

Actions: View

Attachments on bug 93354: 120467 | 124334

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.