[PATCH v2 2/2] powerpc/configs: replace deprecated riva/nvidia with nouveau

Bartlomiej Zolnierkiewicz b.zolnierkie at samsung.com
Mon May 18 12:48:37 UTC 2020

On 5/18/20 1:19 PM, Emil Velikov wrote:
> Hi Michael,
> On Mon, 18 May 2020 at 08:30, Michael Ellerman <mpe at ellerman.id.au> wrote:
>> Emil Velikov <emil.l.velikov at gmail.com> writes:
>>> As mentioned in earlier commit, the riva and nvidia fbdev drivers have
>>> seen no love over the years, are short on features and overall below par
>>> Users are encouraged to switch to the nouveau drm driver instead.
>>> v2: Split configs to separate patch, enable nouveau (Bartlomiej)
>>> Cc: Antonino Daplas <adaplas at gmail.com>
>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie at samsung.com>
>>> Cc: linux-fbdev at vger.kernel.org
>>> Cc: dri-devel at lists.freedesktop.org
>>> Cc: Michael Ellerman <mpe at ellerman.id.au>
>>> Cc: Benjamin Herrenschmidt <benh at kernel.crashing.org>
>>> Cc: Paul Mackerras <paulus at samba.org>
>>> Cc: linuxppc-dev at lists.ozlabs.org
>>> Signed-off-by: Emil Velikov <emil.l.velikov at gmail.com>
>>> Acked-by: Daniel Vetter <daniel.vetter at ffwll.ch> (v1)
>>> ---
>>> Hi all unless, there are objections I would prefer to merge this via
>>> the drm tree.
>> Have you tested that the resulting kernels work on the relevant
>> hardware?
> Sadly, no I haven't. I'm updating the defconfigs as requested by the
> fbdev maintainer.

I've just noticed that v1 (patch #1/1) & v2 (patch #1/2) lack
Cc: to powerpc Maintainers so they cannot see the context of
changes in this patch.

Also you've proposed v1 yourself and it has already contained
modifications to defconfigs (removal of setting the config
options for the old drivers) in addition to marking the old
drivers as BROKEN.

It now turns out that v1 has also never been tested. :(

Please don't submit untested patches without marking them
as such.

>> The old drivers may be crufty but they presumably have been tested by
>> people and at least somewhat work.
>> So I'd be inclined to leave the defconfigs alone until someone can test
>> that the new driver works at all.


Fully agreed. I would also like you to review/ack patch #1/2:


Best regards,
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

> Works for me.
>> I gave it a quick spin on a G5 I have access to and dmesg has a bunch of
>> errors in it (see below). I can't actually tell if the display is
>> working because the machine is remote, and I can't go and check it at
>> the moment because the office is closed.
>>From what I can see, there seems to be three bits:
>  - attempted out-of-bound attempts to read the vbios
> Genuine concern or noise? Likely using the bios from open firmware,
> check any of the other options - see NvBios in [1]
>  - cannot figure out the timer input frequency
> No idea
>  - the TV1 EDID is empty
> Is there an actual TV connected to the device, check with another cable
> Regardless of the patches, reporting [2] the above would be a nice move.
> Thanks
> Emil
> [1] https://protect2.fireeye.com/url?k=d6cf7004-8b548c67-d6cefb4b-0cc47a31cdbc-7c3b251c170ed483&q=1&u=https%3A%2F%2Fnouveau.freedesktop.org%2Fwiki%2FKernelModuleParameters%2F
> [2] https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues

More information about the dri-devel mailing list