From: Michael Thayer <michael.thayer@oracle.com>
To: Hans de Goede <hdegoede@redhat.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: devel@driverdev.osuosl.org, vbox-dev@virtualbox.org,
David Airlie <airlied@linux.ie>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v3] staging: vboxvideo: Add vboxvideo to drivers/staging
Date: Tue, 27 Jun 2017 13:56:33 +0200 [thread overview]
Message-ID: <9cbd1684-6dba-23e6-6f69-8059a0f2d845@oracle.com> (raw)
In-Reply-To: <99dfd921-8eda-132d-e425-4a1c26499b0c@redhat.com>
Hello Hans,
26.06.2017 18:06, Hans de Goede wrote:
> Hi,
>
> On 23-06-17 11:31, Daniel Vetter wrote:
>> On Thu, Jun 22, 2017 at 11:11:37AM +0200, Hans de Goede wrote:
[vboxvideo driver submission information to staging.]
>>
>> In the end it's up to you, but our experience in drm with -staging has
>> been that's both a pain (separate tree, which makes coordination harder
>> for drm drivers) and a ghetto (no one from drm will look at your
>> patches).
>>
>> Especially for small drivers (and this is one, and I expect if you use
>> all
>> the latest and greates helpers atomic will provide it'll shrink
>> considerably) it's just not worth the pain to polish stuff twice.
>>
>> 0toh I see the benefit of putting stuff into staging so in the end
>> it's up
>> to you, just beware pls.
>
> Thanks for the heads up Daniel, for now I would like to move forward with
> getting this in staging, but I do agree that it would be good to get it
> into drivers/gpu soon. Michael do you think you will have some time soon
> to look at moving this to the atomic helpers ?
Taking a look at that now. There is rather a lot of deprecated API use
there that I will have to clean up first. The ast driver which I was
tracking does not seem to have had much clean-up recently - qxl might
have been a better choice. I will also want to get our local code at
the level of your v4 submission before I start to avoid creating
unneeded difficulties.
By the way, see a small, as yet uncommitted fix below.
Regards
Michael
Index: src/VBox/Additions/linux/drm/vbox_fb.c
===================================================================
--- src/VBox/Additions/linux/drm/vbox_fb.c (revision 116355)
+++ src/VBox/Additions/linux/drm/vbox_fb.c (working copy)
@@ -364,6 +364,9 @@
if (fbdev->helper.fbdev) {
info = fbdev->helper.fbdev;
+#ifdef CONFIG_FB_DEFERRED_IO
+ fb_deferred_io_cleanup(info);
+#endif
unregister_framebuffer(info);
if (info->cmap.len)
fb_dealloc_cmap(&info->cmap);
--
Michael Thayer | VirtualBox engineer
ORACLE Deutschland B.V. & Co. KG | Werkstr. 24 | D-71384 Weinstadt
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstraße 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister
der Handelskammer Midden-Nederland, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2017-06-27 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:11 [PATCH v3 0/1] staging: vboxvideo: Add vboxvideo to drivers/staging Hans de Goede
2017-06-22 9:11 ` [PATCH v3] " Hans de Goede
2017-06-22 12:03 ` Dan Carpenter
2017-06-23 9:16 ` Michael Thayer
2017-06-26 14:55 ` Hans de Goede
2017-06-28 9:23 ` Dan Carpenter
2017-06-23 9:31 ` Daniel Vetter
2017-06-26 16:06 ` Hans de Goede
2017-06-26 16:24 ` Daniel Vetter
2017-06-26 16:26 ` Hans de Goede
2017-06-27 11:56 ` Michael Thayer [this message]
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=9cbd1684-6dba-23e6-6f69-8059a0f2d845@oracle.com \
--to=michael.thayer@oracle.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jani.nikula@linux.intel.com \
--cc=seanpaul@chromium.org \
--cc=vbox-dev@virtualbox.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).