From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: "Ville Syrjälä" <syrjala@sci.fi>,
"Jon Smirl" <jonsmirl@gmail.com>,
"DRI developer's list" <dri-devel@lists.sourceforge.net>
Subject: Re: Re: waitforVBlank, how does this even work?
Date: Fri, 04 Mar 2005 09:47:21 +1100 [thread overview]
Message-ID: <1109890041.5610.230.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.62.0503031011150.21362@node2.an-vo.com>
On Thu, 2005-03-03 at 10:12 -0500, Vladimir Dergachev wrote:
> >>>> With which part ? ;)
> >>>
> >>> On having a small stub module that does just IRQs ... I think the base
> >>> module should be the fbdev (mode setting etc...)
> >>
> >> Oh, but I was not suggesting that. I just meant that interrupt handling
> >> code is self-contained and can easily serve several consumers.
> >
> > I'm with you here. And the same should IMHO hold for DMA handling. And for
> > memory management of course.
>
> With one refinement - the DMA code would need to be a customer of IRQ
> code..
No, again, DMA is what DRM is for, or you want to re-invent the whole
architecture ?
Ben.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-03 22:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 5:50 waitforVBlank, how does this even work? Jon Smirl
2005-03-02 5:55 ` Jon Smirl
2005-03-02 7:10 ` Benjamin Herrenschmidt
2005-03-02 7:30 ` [Linux-fbdev-devel] " Ville Syrjälä
2005-03-02 7:53 ` Benjamin Herrenschmidt
2005-03-02 14:42 ` Torgeir Veimo
2005-03-02 16:32 ` Vladimir Dergachev
2005-03-02 17:09 ` Jon Smirl
2005-03-02 17:15 ` Vladimir Dergachev
2005-03-02 17:30 ` Jon Smirl
2005-03-02 17:45 ` Vladimir Dergachev
2005-03-02 17:51 ` Jon Smirl
2005-03-02 19:45 ` Vladimir Dergachev
2005-03-02 18:08 ` Eric Sellers
2005-03-02 19:06 ` Jon Smirl
2005-03-02 17:29 ` James Simmons
2005-03-02 22:38 ` Benjamin Herrenschmidt
2005-03-03 0:04 ` James Simmons
2005-03-02 23:42 ` Benjamin Herrenschmidt
2005-03-03 1:03 ` Vladimir Dergachev
2005-03-03 2:23 ` Benjamin Herrenschmidt
2005-03-03 3:01 ` Vladimir Dergachev
2005-03-03 7:55 ` Ville Syrjälä
2005-03-03 15:12 ` Vladimir Dergachev
2005-03-03 22:47 ` Benjamin Herrenschmidt [this message]
2005-03-03 22:08 ` Benjamin Herrenschmidt
2005-03-04 13:18 ` Ville Syrjälä
2005-03-04 22:35 ` Benjamin Herrenschmidt
2005-03-05 6:30 ` Ville Syrjälä
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=1109890041.5610.230.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=syrjala@sci.fi \
/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 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.