| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Still early (not released yet, albeit being on rc7 it is unlikely to
break at this point), but this these versions received extra care for
6.13 and fbdev issue seem resolved.
565.77(NFB) users will have to stick to <6.13 on manually patch still.
Unknown if that branch will even get new releases anymore, nor how long
left until the next branch. Drop the comment in advance though.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NVIDIA has fixed 550.142 to build with 6.13-rc3 (565.77 fails), but
has not addressed/noticed that fbdev=1 is broken. So keep a reminder
to not add =6.13 even if it builds when 6.13 releases.
Also note in 565.77 in case a new version releases that only fixed
the build failure and not fbdev=1.
Patches exists, but would rather not use these, hard to tell if
they're correct. Users should stick to 6.12 or older until proper
fixes.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Was announced that LTS kernel 6.1 will get an extra year of
support, so this may give an extra year in the tree to these
drivers (still depends on if Gentoo's kernel maintainers are
going to keep these in the tree for that long, or if these
drivers will still be in a usable state by then).
Given 6.6.x hasn't been extended, 470 users may need to go
back to 6.1.x for that extra year (without patching anyway).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I915 now selects TTM in newer kernels making it usable, however
the text is unaware of changes and versions, so just drop the
mention that I915 is not usable and suggest checking the kernel's
help.
Also list QXL example first, it's smaller to build. Still keep
AMDGPU listed mostly because it's more recognizable by users.
Leaving 535 as-is, last I know of TTM_HELPERS doesn't matter for
it and it likely does not have that long of support.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Not interesting to show pipestatus -v when the 2nd command
is an ebuild internal and will die on its own if failed.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/924715
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/875233
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
| |
No longer a beta, considered a new feature branch instead (NFB).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Doesn't seem to have received 550.135 fixes for ttm and kernel 6.12
still, maybe these won't get updated till the next branch. May still
be affected by the last security vulnerability too.. but it's masked,
use as your own risks. Did gain Vulkan 1.4 support though.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Happened to glance over that comment I wrote and was
wondering what I was reading.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Seems to be quite a few issues and may not be trivial to fix, upstream
already has some sanity checks to pickup that conftests failed and it
should be fixed properly in time.
Using KERNEL_CC to ensure it's used everywhere for modules, esp.
conftest.sh. Non-modules parts seems fine with c23.
For 390/470, just add it to the list of other permanent (ugly)
workarounds and update's 470 comment given it's no longer supported.
Due for removal from the tree in roughly 2 years or less and so just
need to hold on until then.
Closes: https://bugs.gentoo.org/944092
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
|
|
|
| |
6.12 fixes (and probably sec fixes too) haven't made it in,
this just adds the two latest vulkan extensions
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Would make it a hard failure (no ~) given a NVIDIA sanity check already
causes the build to fail, but there is a variable to override that.
Doesn't hurt to do our own standard check, mention the variable, and
warn that using it is unsupported given the increasing amount of users
jumping on PREEMPT_RT (that for most they likely do not need nor
understand for who it's useful for, and notably that it will also hurt
performance).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|