Re: [Mesa-dev] [PATCH 2/4] pipe-loader: Fallback to kmsro driver when no matching driver name found
Eric Anholt writes: > [ Unknown signature status ] > Rob Herring writes: > >> If we can't find a driver matching by name, then use the kmsro driver. >> This removes the need for needing a driver descriptor for every possible >> KMS driver. >> >> Signed-off-by: Rob Herring > > I've pushed patch 1 and 2, and the hx8357d rebase. And a followup for the rest of tinydrm: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/165 signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH 2/4] pipe-loader: Fallback to kmsro driver when no matching driver name found
Rob Herring writes: > If we can't find a driver matching by name, then use the kmsro driver. > This removes the need for needing a driver descriptor for every possible > KMS driver. > > Signed-off-by: Rob Herring I've pushed patch 1 and 2, and the hx8357d rebase. signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH 2/4] pipe-loader: Fallback to kmsro driver when no matching driver name found
Eric Anholt writes: > [ Unknown signature status ] > Rob Herring writes: > >> If we can't find a driver matching by name, then use the kmsro driver. >> This removes the need for needing a driver descriptor for every possible >> KMS driver. >> >> Signed-off-by: Rob Herring > > Oh, very nice. > > There's some risk here -- for example, vkms (with prime enabled, which > it doesn't currently) will fail badly at prime sharing buffers with > hardware drivers doing WC mappings of buffers. But I guess we should be > preventing that at the kernel level when we enable prime, and having > userspace maybe test creating a shared resource when loading kmsro with > a particular backend. That is to say, Reviewed-by: Eric Anholt If you've got display-only KMS and a render node, we should make sure that Mesa glues those two together. signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH 2/4] pipe-loader: Fallback to kmsro driver when no matching driver name found
Rob Herring writes: > If we can't find a driver matching by name, then use the kmsro driver. > This removes the need for needing a driver descriptor for every possible > KMS driver. > > Signed-off-by: Rob Herring Oh, very nice. There's some risk here -- for example, vkms (with prime enabled, which it doesn't currently) will fail badly at prime sharing buffers with hardware drivers doing WC mappings of buffers. But I guess we should be preventing that at the kernel level when we enable prime, and having userspace maybe test creating a shared resource when loading kmsro with a particular backend. signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH 2/4] pipe-loader: Fallback to kmsro driver when no matching driver name found
Reviewed-by: Alyssa Rosenzweig ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
