https://bugs.freedesktop.org/show_bug.cgi?id=100228
--- Comment #25 from Boris Vinogradov ---
Created attachment 141455
--> https://bugs.freedesktop.org/attachment.cgi?id=141455=edit
Kernel log with new firmware after some boot
But I have some boot with reproduce error.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=100228
--- Comment #24 from Boris Vinogradov ---
(In reply to Boris Vinogradov from comment #23)
> Created attachment 141453 [details]
> Kernel log with new firmware
>
> There're no any changes for me with new firmare from git.
(In reply to Boris
https://bugs.freedesktop.org/show_bug.cgi?id=100228
--- Comment #23 from Boris Vinogradov ---
Created attachment 141453
--> https://bugs.freedesktop.org/attachment.cgi?id=141453=edit
Kernel log with new firmware
There're no any changes for me with new firmare from git.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=107817
--- Comment #1 from Ilia Mirkin ---
Should be fixed by:
https://github.com/skeggsb/nouveau/commit/c122b4b8854c3ac7d1d5a8fd902b54e9e42a27ac
Ben -- probably worth backporting...
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=100228
--- Comment #22 from Rhys Kidd ---
So there's updated low-level firmware shipped by NVIDIA for the GP107 (and
other pre-GP108 Pascal GPUs) [0]. This might resolve or improve the situation
for mobile GP107 users.
nvidia: switch GP10[2467] to
From: Colin Ian King
Don't populate the array vsoff on the stack but instead make it
static. Makes the object code smaller by 67 bytes:
Before:
textdata bss dec hex filename
5753 112 0586516e9 .../nouveau/nvkm/subdev/bios/dp.o
After:
textdata
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on pci/next]
[also build test WARNING on v4.19-rc2 next-20180831]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Tue, Sep 04, 2018 at 03:07:52PM +0800, Daniel Drake wrote:
> On Tue, Sep 4, 2018 at 2:43 PM, Mika Westerberg
> wrote:
> > Yes, can you check if the failing device BAR is included in any of the
> > above entries? If not then it is probably not related.
>
> mtrr again for reference:
> reg00:
On Tue, Sep 4, 2018 at 2:43 PM, Mika Westerberg
wrote:
> Yes, can you check if the failing device BAR is included in any of the
> above entries? If not then it is probably not related.
mtrr again for reference:
reg00: base=0x0c000 ( 3072MB), size= 1024MB, count=1: uncachable
reg01:
On Tue, Sep 04, 2018 at 09:52:02AM +0800, Daniel Drake wrote:
> # cat /proc/mtrr
> reg00: base=0x0c000 ( 3072MB), size= 1024MB, count=1: uncachable
> reg01: base=0x0a000 ( 2560MB), size= 512MB, count=1: uncachable
> reg02: base=0x09000 ( 2304MB), size= 256MB, count=1: uncachable
>
On Tue, 4 Sep 2018 at 10:59, Ilia Mirkin wrote:
>
> This is the beginnings of HDMI 2.0 support. All of the "extra"
> features are left out, such as 12/16bpc, YUV420, etc.
>
> I've verified that with this code, a GP108 (GT1030) can switch between
> 4k@60 and 1920x1080@60 on a LG 4K TV. Further,
11 matches
Mail list logo
