linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jorge Luis Zapata Muga <jorgeluis.zapata@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: modesetting and fbdev
Date: Thu, 31 Jan 2008 23:52:47 -0800	[thread overview]
Message-ID: <200801312352.47290.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <eb77d7060801311558i40942c34y71f0831f64e63d0c@mail.gmail.com>

On Thursday, January 31, 2008 3:58 pm Jorge Luis Zapata Muga wrote:
> On Jan 31, 2008 5:55 AM, Jesse Barnes <jbarnes@virtuousgeek.org> 
wrote:
> > On Wednesday 30 January 2008 11:55:19 am Jorge Luis Zapata Muga 
wrote:
> > > Hi all, I've seen some patches and discussions about modesetting
> > > into the kernel and fb devices, what is the relation or plans
> > > with that beside the pros and cons? keep the fb api? some kind of
> > > merge between both?
> >
> > The DRM modesetting code preserves compatibility with the fb
> > interfaces, so if you write a DRM based modesetting driver, fb
> > applications can run on top unmodified.  Also, the existing fb
> > stuff won't go away (though some maintainers may choose to replace
> > their fb drivers with DRM modesetting based ones).  Which type of
> > driver to write just depends on what your hw is capable of and
> > whether you feel the slightly higher complexity of a DRM based
> > driver is justified (it probably will be if you ever plan on adding
> > 3d support to your stack or if you want to exploit the fancy output
> > control that the DRM based API provides).
> >
> > Hope that helps.
>
> Yes it does, thanks for explaining ... my concerns are about multiple
> framebuffers on one chip, from what i see you reference a framebuffer
> == output (correct me if im wrong),

Yeah, that's wrong. :)  It supports multiple memory objects, which you 
can bind to CRTCs, which connect to outputs, arbitrarily.

> and i thought that maybe this 
> upper controller (drm) could take the control of hw with multiple
> graphics layers i.e one framebuffer for every gfx layer, like
> controlling the compositing of them, beside the memory controller/3d
> thing. Is this in consideration?

Yes, definitely.  One of the design goals for these new parts of the DRM 
layer was to fully support output reconfiguration and routing, so the 
system should be as flexible as the underlying hardware allows.

> Where is the main development taken? on the modesetting-101 branch?

Yep, that's the main tree right now.

Jesse

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-02-01  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 19:55 modesetting and fbdev Jorge Luis Zapata Muga
2008-01-31  4:55 ` Jesse Barnes
2008-01-31 23:58   ` Jorge Luis Zapata Muga
2008-02-01  7:52     ` Jesse Barnes [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=200801312352.47290.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=jorgeluis.zapata@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).