From: Roman Kiryanov <rkir@google.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Lingfeng Yang <lfy@google.com>,
Alistair Strachan <astrachan@google.com>
Subject: Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver
Date: Wed, 30 Jan 2019 19:56:14 -0800 [thread overview]
Message-ID: <CAOGAQeo6zr=FYFPHt3NUajdStWyQe3oPZYNEn+o2GxXwXWd14g@mail.gmail.com> (raw)
In-Reply-To: <20190130144414.GA8357@kroah.com>
> Also, why does the other Android "emulator", cuttlefish, not need
> special drivers like this and the other goldfish drivers? Shouldn't you
> be using the same interfaces that they use that are already merged
> upstream?
> Actually, now that cuttlefish works on a mainline kernel, can't we just
> delete the existing goldfish code?
cuttlefish is a separate emulator with different assumptions which do
not work for us.
Our emulator runs on Linux, Mac and Windows, it uses host's GPU
directly for rendering.
I am not sure how cuttlefish accesses host's GPU memory (it might not
support this),
but we need it to support coherent memory access for Vulcan. We also
might use it to access
host's camera pixels to avoid copying them.
Please keep goldfish drivers.
next prev parent reply other threads:[~2019-01-31 3:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 2:11 [PATCH v3 1/3] drivers: platform: goldfish: fix the checkpatch complain in Kconfig rkir
2019-01-09 2:11 ` [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver rkir
2019-01-09 8:31 ` Greg KH
2019-01-10 1:41 ` Roman Kiryanov
2019-01-16 4:53 ` Roman Kiryanov
2019-01-22 11:07 ` Greg KH
2019-01-29 8:32 ` Roman Kiryanov
2019-01-29 9:37 ` Greg KH
2019-01-30 14:44 ` Greg KH
2019-01-31 3:56 ` Roman Kiryanov [this message]
2019-01-09 2:11 ` [PATCH v3 3/3] drivers: platform: goldfish: goldfish_sync: " rkir
2019-01-22 11:08 ` Greg KH
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='CAOGAQeo6zr=FYFPHt3NUajdStWyQe3oPZYNEn+o2GxXwXWd14g@mail.gmail.com' \
--to=rkir@google.com \
--cc=astrachan@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=lfy@google.com \
--cc=linux-kernel@vger.kernel.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).