public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Herrmann <dh.herrmann@gmail.com>,
	<dri-devel@lists.freedesktop.org>
Cc: Ingo Molnar <mingo@kernel.org>, <linux-fbdev@vger.kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	<linux-kernel@vger.kernel.org>, Tom Gundersen <teg@jklm.no>
Subject: Re: [PATCH 00/11] SimpleDRM & Sysfb
Date: Mon, 3 Mar 2014 12:12:33 +0200	[thread overview]
Message-ID: <53145591.4070004@ti.com> (raw)
In-Reply-To: <1390486503-1504-1-git-send-email-dh.herrmann@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3032 bytes --]

Hi,

On 23/01/14 16:14, David Herrmann wrote:
> Hi
> 
> Another round of SimpleDRM patches. I somehow lost track of the last ones and as
> this is a major rewrite, I'll just start at v1 again.
> 
> Some comments up-front:
> 
>  - @Ingo: Patch #1 and #2 are unchanged from the previous ML discussions. I
>    included them in this series as the other patches depend on them. Could you
>    pick them up for the x86 tree? The other 9 patches won't make it in 3.14 so
>    no reason to put them through the DRM tree.
>    All mentioned issues should be addressed. If there's still sth missing,
>    please let me know.
> 
>  - The DRM patches depend on my "DRM Anonymous Inode" patches. But it should be
>    trivial to apply them on drm-next (I think only one line needs to be changed:
>    i_mapping => dev_mapping).
> 
>  - I tested the SimpleDRM fbdev fallback with linux-console+Xorg and it works
>    fine. The DRM backend is only tested with some DRM tests I have locally. I
>    have no idea how to make Xorg pick up a specific /dev/dri/card0 card. It
>    always tells me "no screens found" (as the underlying device is not marked as
>    boot_vga..). If someone knows how to tell Xorg to use card0, I'd gladly test
>    this. But I'm no longer used to writing xorg.confs..
> 
> 
> This series introduces two new concepts: sysfb and SimpleDRM
> Sysfb is just a generalization of the x86-sysfb concept. It allows to register
> firmware-framebuffers with the system as platform-devices. This way, drivers can
> properly bind to these devices and we prevent multiple drivers from accessing
> the same firmware-framebuffer.
> Sysfb also provides hooks to get a safe handover to real hw-drivers (like i915).
> Please see the "video: sysfb: add generic firmware-fb interface" patch for a
> thorough description of the API. This patch also adds a rather verbose
> documentation of all known firmware-fb facilities.
> 
> As second part, this series introduces SimpleDRM. It's a very basic DRM driver
> that can replace efifb, vesafb, simplefb and friends. It's 100% compatible to
> the "udl" DRM driver, so user-space like xf86-video-modesetting can pick them up
> just fine. User-space that cannot deal with drmModeDirtyFB() (like weston and
> friends) currently cannot use SimpleDRM. However, that's also true for all other
> DRM drivers which provide shadow framebuffers. We could provide something like
> FB-DEFIO, but that's just useless overhead to paper of lazy user-space.
> 
> I have tested this with all hardware that I have at home, with a lot hand-over
> combinations (with/without SYSFB, with efifb/vesafb/simplefb, with SimpleDRM,
> ...) and all worked great so far.

What's the status with this one? Headed for 3.15?

Are the SimpleDRM and sysfb linked somehow? (I.e. do they need to be in
the same series?)

And jfyi, the drivers/video/ changes will conflict with the
drivers/video/ directory reorganization series, which may be merged for
3.15.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  parent reply	other threads:[~2014-03-03 10:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 14:14 [PATCH 00/11] SimpleDRM & Sysfb David Herrmann
2014-01-23 14:14 ` [PATCH 01/11] x86: sysfb: fool-proof CONFIG_X86_SYSFB David Herrmann
2014-01-23 14:14 ` [PATCH 02/11] x86: sysfb: remove sysfb when probing real hw David Herrmann
2014-01-23 16:51   ` Ingo Molnar
2014-01-23 17:07     ` David Herrmann
2014-01-23 17:14       ` Ingo Molnar
2014-01-23 19:09         ` David Herrmann
2014-01-24 10:16           ` Ingo Molnar
2014-01-23 14:14 ` [PATCH 03/11] fbdev: efifb: add dev->remove() callback David Herrmann
2014-01-23 14:14 ` [PATCH 04/11] fbdev: vesafb: " David Herrmann
2014-01-23 14:14 ` [PATCH 05/11] x86: sysfb: store apertures in simplefb platform-data David Herrmann
2014-01-23 14:14 ` [PATCH 06/11] video: sysfb: add generic firmware-fb interface David Herrmann
2014-01-23 14:14 ` [PATCH 07/11] drm: mgag200: remove redundant fbdev removal David Herrmann
2014-01-23 14:15 ` [PATCH 08/11] drm/i915: remove sysfbs early David Herrmann
2014-01-23 14:15 ` [PATCH 09/11] drm: add SimpleDRM driver David Herrmann
2014-01-23 14:15 ` [PATCH 10/11] drm: simpledrm: add fbdev fallback support David Herrmann
2014-01-23 14:15 ` [PATCH 11/11] x86/sysfb: allow sysfb+simpledrm combination David Herrmann
2014-01-27 22:18 ` [PATCH 00/11] SimpleDRM & Sysfb David Herrmann
2014-02-21  9:56   ` Thierry Reding
2014-03-03 10:12 ` Tomi Valkeinen [this message]
2014-03-03 10:29   ` David Herrmann
2014-03-03 10:45     ` Tomi Valkeinen
2014-03-03 11:09       ` David Herrmann
2014-03-03 11:22         ` Tomi Valkeinen
2014-03-06 12:16           ` David Herrmann
2014-03-07 12:44             ` Tomi Valkeinen
2014-03-07 13:05               ` David Herrmann
2014-03-07 13:52                 ` Tomi Valkeinen
2014-03-07 14:06                   ` David Herrmann

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=53145591.4070004@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=teg@jklm.no \
    /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