From: Nils Gillmann <ng0@n0.is>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix@gnu.org, Nils Gillmann <ng0@n0.is>
Subject: Re: Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+)
Date: Wed, 9 May 2018 08:19:48 +0000 [thread overview]
Message-ID: <20180509081948.mgjqkpcq6tyeqjgg@abyayala> (raw)
In-Reply-To: <87wowdmh1o.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Pierre Neidhardt transcribed 1.4K bytes:
>
> Thanks for the tip! :)
>
> > I can't advocate how to package or do this here (which is
> > too bad),
>
> Why not? Is it non-free? Custom kernel compilation is fine to discuss
> on this mailing list if I'm not mistaken. Only proprietary firmware
> packaging isn't. Correct me if I'm wrong.
drm-tip is a branch of the Linux kernel, not the GNU variant linux-libre.
> > but for all things graphics related this will be suggested
> > by upstream most certainly.
> >
> >
> > 0: branch as in the repository, not linux repository itself. In case you
> > are unfamilar with linux development branching model.
>
> Which repository? Sorry, I didn't get this.
Linux drm-tip. I didn't link to it for reasons, but "git kernel.org linux drm-tip"
should help.. if it helps in your case at all. I'm not sure.
> > 1: Variants of https://bugs.freedesktop.org/buglist.cgi?quicksearch=i915%20intel_cpu_fifo_underrun_irq_handler&list_id=579081
> > and this is still going on.
>
> Indeed, I've seen this issue many times on a couple of machines.
>
> --
> Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-05-09 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 6:06 Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+) Pierre Neidhardt
2018-04-13 6:50 ` Tomáš Čech
2018-04-13 7:33 ` Pierre Neidhardt
2018-04-13 10:14 ` Pierre Neidhardt
2018-04-24 8:37 ` Ludovic Courtès
2018-04-24 13:17 ` Pierre Neidhardt
2018-05-03 6:45 ` Pierre Neidhardt
2018-05-08 21:11 ` Nils Gillmann
2018-05-09 7:20 ` Pierre Neidhardt
2018-05-09 8:19 ` Nils Gillmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180509081948.mgjqkpcq6tyeqjgg@abyayala \
--to=ng0@n0.is \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.