public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Linux-4.16.* & NVidia
Date: Sat, 14 Apr 2018 15:30:21 +0200	[thread overview]
Message-ID: <20180414133021.w3456o2ussrm6i7g@solfire> (raw)
In-Reply-To: <CAGfcS_n8YtjZB9HwUphvSqu=7c3cNJREKp1nNGCeeeF2MhbQww@mail.gmail.com>

On 04/14 09:20, Rich Freeman wrote:
> On Sat, Apr 14, 2018 at 9:11 AM, András Csányi <sayusi.ando@gmail.com> wrote:
> > Stay at stable kernel version, imho. There are a few people here waiting for
> > nvidia with ~x86 flagged kernel.
> >
> 
> This is pretty much the reality of using any out-of-tree kernel
> module, and especially the case for a proprietary module like the
> nvidia drivers.  They're often not compatible across kernel 4.x
> version changes, and upstream projects often do not target mainline in
> their official releases.
> 
> IMO you're better off still sticking to longterm, such as 4.14.
> Otherwise you're still dealing with stable dropping support for your
> version but the out-of-kernel module takes a week to support the new
> version.  There isn't any overlap in linux stable support release
> across versions - they stop one and start the next.  Only the longterm
> releases get overlapping support windows.
> 
> 
> -- 
> Rich


Hi,

I jyst wanted to no, whether Yes or No.
The rest I will decide on myself,

So..."no" to summarize/ :)

Thanks for the help.
Cheers
Meino




  reply	other threads:[~2018-04-14 13:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14 13:00 [gentoo-user] Linux-4.16.* & NVidia tuxic
2018-04-14 13:11 ` András Csányi
2018-04-14 13:20   ` Rich Freeman
2018-04-14 13:30     ` tuxic [this message]
2018-04-14 18:28 ` P Levine
2018-04-17 18:19   ` davidroman96
2018-04-18  3:12     ` tuxic
2018-04-18 12:57       ` Mark Knecht
2018-04-18 16:01         ` Elijah Mark Anderson
2018-04-14 21:13 ` Elijah Mark Anderson
2018-04-14 21:21   ` tuxic

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=20180414133021.w3456o2ussrm6i7g@solfire \
    --to=tuxic@posteo.de \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox