[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: 5.9 points Re: 7.0 points 5.1 points Re: Call for Foundation-supported Project Ideas
From:       Warner Losh <imp () bsdimp ! com>
Date:       2022-01-06 16:41:33
Message-ID: CANCZdfoa5AAYAs7p8=sOm9PFeW51=kHp1z1dfFzi=AVzpr-Syw () mail ! gmail ! com
[Download RAW message or body]

On Thu, Jan 6, 2022, 9:35 AM Stefan Blachmann <sblachmann@gmail.com> wrote:

> Correct.
> Only late in the discussion Warner mentioned that the kms drm drivers
> need to be loaded.
> So my request has became moot.
>
> The drm kmod drivers usually are being associated as graphics drivers for
> xorg.
> Thus it is not at all intuitive/obvious that these are also required
> on console-only computers to make resuming succeed.
>
> Given this, it is rather a *documentation* *issue*, as the necessity
> to install/load the drm kmod drivers is *not* mentioned anywhere in
> the documentation regarding suspend/resume, making users wonder why
> resuming fails.
>

Absolutely agreed on need more docs and an update pass. I raised it as part
of this year's core team meeting with the foundation. Though this one issue
likely can be handled by a simple document PR.

Warner


> On 1/6/22, Joerg Sonnenberger <joerg@bec.de> wrote:
> > On Wed, Jan 05, 2022 at 11:22:39AM -0700, Warner Losh wrote:
> >> Why bother. Load the kms drm drivers. The suspend/resume code is in
> those
> >> drivers. They work console, X11 and wayland, more or less.  It's an
> >> absolutely
> >> insane idea to spend limited funds on the crazy ideas presented in this
> >> thread.
> >> They are known to be flakey, unreliable or technically just not
> possible.
> >
> > The main problem is that modern VGA devices often only have just enough
> > VESA BIOS support to give Windows a generic framebuffer as fallback.
> > Otherwise, I don't think it is as flakey. All that said, spending funds
> > on it would certainly be misdirected.
> >
> > Joerg
> >
> >
>
>

[Attachment #3 (text/html)]

<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Jan 6, 2022, 9:35 AM Stefan Blachmann &lt;<a \
href="mailto:sblachmann@gmail.com">sblachmann@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Correct.<br> Only late in the \
discussion Warner mentioned that the kms drm drivers<br> need to be loaded.<br>
So my request has became moot.<br>
<br>
The drm kmod drivers usually are being associated as graphics drivers for xorg.<br>
Thus it is not at all intuitive/obvious that these are also required<br>
on console-only computers to make resuming succeed.<br>
<br>
Given this, it is rather a *documentation* *issue*, as the necessity<br>
to install/load the drm kmod drivers is *not* mentioned anywhere in<br>
the documentation regarding suspend/resume, making users wonder why<br>
resuming fails.<br></blockquote></div></div><div dir="auto"><br></div><div \
dir="auto">Absolutely agreed on need more docs and an update pass. I raised it as \
part of this year&#39;s core team meeting with the foundation. Though this one issue \
likely can be handled by a simple document PR.</div><div dir="auto"><br></div><div \
dir="auto">Warner</div><div dir="auto"><br></div><div dir="auto"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
On 1/6/22, Joerg Sonnenberger &lt;<a href="mailto:joerg@bec.de" target="_blank" \
rel="noreferrer">joerg@bec.de</a>&gt; wrote:<br> &gt; On Wed, Jan 05, 2022 at \
11:22:39AM -0700, Warner Losh wrote:<br> &gt;&gt; Why bother. Load the kms drm \
drivers. The suspend/resume code is in those<br> &gt;&gt; drivers. They work console, \
X11 and wayland, more or less.   It&#39;s an<br> &gt;&gt; absolutely<br>
&gt;&gt; insane idea to spend limited funds on the crazy ideas presented in this<br>
&gt;&gt; thread.<br>
&gt;&gt; They are known to be flakey, unreliable or technically just not \
possible.<br> &gt;<br>
&gt; The main problem is that modern VGA devices often only have just enough<br>
&gt; VESA BIOS support to give Windows a generic framebuffer as fallback.<br>
&gt; Otherwise, I don&#39;t think it is as flakey. All that said, spending funds<br>
&gt; on it would certainly be misdirected.<br>
&gt;<br>
&gt; Joerg<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]