From: Daniel Vetter <firstname.lastname@example.org> To: Pekka Paalanen <email@example.com> Cc: Haneen Mohammed <firstname.lastname@example.org>, Rodrigo Siqueira <email@example.com>, Neil Armstrong <firstname.lastname@example.org>, DRI Development <email@example.com>, Melissa Wen <firstname.lastname@example.org>, Thomas Zimmermann <email@example.com>, Daniel Vetter <firstname.lastname@example.org> Subject: Re: [PATCH 3/3] drm/vkms: fbdev emulation support Date: Tue, 13 Oct 2020 09:53:44 +0200 [thread overview] Message-ID: <CAKMK7uHY_nrB=0-xkWi+FXFosCY1XPVXLJb+mGqDR+GpRZ6C6Q@mail.gmail.com> (raw) In-Reply-To: <20201013091410.06c98a1c@eldfell> On Tue, Oct 13, 2020 at 8:14 AM Pekka Paalanen <email@example.com> wrote: > > On Mon, 12 Oct 2020 16:23:35 +0200 > Daniel Vetter <firstname.lastname@example.org> wrote: > > > On Mon, Oct 12, 2020 at 02:40:58PM +0200, Neil Armstrong wrote: > > > Hi, > > > > > ... > > > > It's weird because it the kernel is misconfigured and no console is specified on the cmdline > > > this console could become the main console... > > > > > > It's a great feature, but couldn't this be a module parameter ? > > > > If you have vkms enabled in a distro, you're doing it wrong. > > That's really not a great position to take. I would prefer that > if a random contributor writes a Weston patch and runs 'meson test', it > will use VKMS to run Weston's DRM-backend tests on his machine > automatically, maybe save for some seat and device node access > permissions bits which distributions could be delivering as well. > > Just put the VKMS device node into a non-default seat, and Xorg etc. > will happily ignore it. > > For the fbdev device node, I don't know. Maybe a module parameter > really is a good choice there, defaulting to off. I have no interest in > testing anything against fbdev, but other people might disagree of > course. > > Why? Gitlab CI is still not running tests for every commit, just per > MR, and it might even be infeasible too. > > I am also hoping for a future where I don't have to build my own kernel > just to be able to run Weston DRM tests with VKMS. That means I want to > be able to run my machine with VKMS loaded and active at all times, > without affecting the normal desktop. I already have such a setup with > an extra AMD card, but you can't run most KMS tests against real > hardware drivers. I just realized that building vkms is no problem, since it doesn't auto-load. And if our Grand Plans with configurability come true, then your test-harness will want to do that loading and setup itself anyway. With that there also shouldn't be any problems with fbcon, since presumably you already have that bound to the real gpu. So I think we're all fine here, for everyone. Now if you built-in vkms, that's a different thing. And for that I really think a "don't do that" is the right choice. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list email@example.com https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-13 7:53 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-09 23:21 [PATCH 1/3] drm/vkms: Set preferred depth correctly Daniel Vetter 2020-10-09 23:21 ` [PATCH 2/3] drm/vkms: Switch to shmem helpers Daniel Vetter 2020-10-12 10:59 ` Chris Wilson 2020-10-12 11:20 ` Thomas Zimmermann 2020-10-12 11:22 ` Thomas Zimmermann 2020-10-12 12:41 ` Melissa Wen 2020-10-13 11:10 ` [PATCH] " Daniel Vetter 2020-10-09 23:21 ` [PATCH 3/3] drm/vkms: fbdev emulation support Daniel Vetter 2020-10-12 11:24 ` Thomas Zimmermann 2020-10-12 12:40 ` Neil Armstrong 2020-10-12 14:23 ` Daniel Vetter 2020-10-13 6:14 ` Pekka Paalanen 2020-10-13 7:53 ` Daniel Vetter [this message] 2020-10-13 10:19 ` Pekka Paalanen 2020-10-13 11:03 ` Daniel Vetter 2020-10-16 10:10 ` Melissa Wen 2020-10-20 8:34 ` Daniel Vetter 2020-10-12 11:08 ` [PATCH 1/3] drm/vkms: Set preferred depth correctly Thomas Zimmermann 2020-10-12 12:59 ` Melissa Wen 2020-10-15 21:39 ` Daniel Vetter 2020-10-16 10:18 ` Melissa Wen 2020-10-16 10:38 ` Simon Ser 2020-10-16 11:35 ` Daniel Vetter 2020-10-16 17:02 ` Melissa Wen 2020-10-16 17:05 ` Daniel Vetter 2020-10-17 8:39 ` Melissa Wen 2020-10-17 15:23 ` Daniel Vetter 2020-10-27 10:13 ` Thomas Zimmermann 2020-10-27 10:18 ` Daniel Vetter
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='CAKMK7uHY_nrB=0-xkWi+FXFosCY1XPVXLJb+mGqDR+GpRZ6C6Q@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 3/3] drm/vkms: fbdev emulation support' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.