From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: Dave Airlie <airlied@gmail.com>,
James Simmons <jsimmons@pentafluge.infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
adaplas@pol.net, dri-devel@lists.sourceforge.net,
xorg@lists.freedesktop.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Resource management.
Date: Tue, 22 Feb 2005 00:59:22 -0500 [thread overview]
Message-ID: <9e47339105022121595913c9b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0502220450190.22255@pentafluge.infradead.org>
On Tue, 22 Feb 2005 05:13:07 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
> > > 4. Which comes to the next point. The code is not modular enough. Take
> > > drm_bufs.c. Everything is a ioctl function. This has a few disadvantages.
> > > One is the fbdev layer couldn't just link into it so fbcon could use
> > > it. The second is it's not easy to take advantage of things like sysfs.
> > > If you could untangle the code somewhat it would make life so much
> > > easier. That would include making life easier for OS ports.
> >
> > the reason we can't take advantage of sysfs or anything like it is
> > that we can't bind to the PCI device as we break things.. this is the
> > root of a lot of our problems...
>
> Is this because you want to be OS portable? This makes things very very
> hard to merge. Fbdev attempts to take advantage the most powerful linux
> kernel features.
My turn to laugh! It's because Linux only allow one driver to bind to
the device and fbdev has already bound to it. We have done
siginificant work to DRM to try and work around this (stealth mode)
but the right solution is to have a common base driver.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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-02-22 5:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 19:11 Resource management James Simmons
2005-02-21 22:53 ` Antonino A. Daplas
2005-02-21 23:25 ` James Simmons
2005-02-22 1:01 ` Jon Smirl
2005-02-22 3:53 ` James Simmons
2005-02-22 4:46 ` [Linux-fbdev-devel] " Dave Airlie
2005-02-22 5:13 ` James Simmons
2005-02-22 5:59 ` Jon Smirl [this message]
2005-02-22 5:23 ` [Linux-fbdev-devel] " Jon Smirl
2005-02-22 17:23 ` James Simmons
2005-02-22 18:59 ` [Linux-fbdev-devel] " Alex Deucher
2005-02-22 13:25 ` Antonino A. Daplas
2005-02-22 14:06 ` Antonino A. Daplas
2005-02-24 19:57 ` James Simmons
2005-02-24 23:05 ` Antonino A. Daplas
2005-02-28 20:01 ` Resource management II James Simmons
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=9e47339105022121595913c9b@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@pol.net \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@pentafluge.infradead.org \
--cc=jsimmons@www.infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg@lists.freedesktop.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).