From: Kronos <kronos@kronoz.cjb.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] New FBDev patch
Date: Fri, 9 Jan 2004 18:17:33 +0100 [thread overview]
Message-ID: <20040109171733.GA13027@dreamland.darkstar.lan> (raw)
In-Reply-To: <Pine.LNX.4.44.0401082108080.12797-100000@phoenix.infradead.org>
Il Thu, Jan 08, 2004 at 10:03:54PM +0000, James Simmons ha scritto:
>
> This is the latest patch against 2.6.0-rc3. Give it a try.
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
> <kronos@kronoz.cjb.net> (03/09/17 1.1267.40.1)
> Add new API framebuffer_alloc and framebuffer_release.
>
> Framebuffer info structure (ie. struct fb_info) must be obtained from
> framebuffer_alloc. When it is no longer needed (after unregister_framebuffer
> and clean up) it can be released using framebuffer_release.
>
> If the framebuffer is not registered yet (eg. on error path) then fb_info must
> be released via kfree.
Are we sure that we want this for 2.6? Greg KH has a much less intrusive
patch, maybe you should take that instead and keep my work 2.7.
If you decide to go with framebuffer_alloc then I have more patches for
you ;)
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
I went to God just to see
And I was looking at me
Saw heaven and hell were lies
When I'm God everyone dies
next prev parent reply other threads:[~2004-01-09 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 22:03 New FBDev patch James Simmons
2004-01-08 23:05 ` Paul Mundt
2004-01-08 23:12 ` Tomas Szepe
2004-01-09 0:35 ` James Simmons
2004-01-10 17:15 ` Re: New FBDev patch (a little report) Javier Villavicencio
2004-01-11 7:35 ` Benjamin Herrenschmidt
2004-01-11 7:42 ` Benjamin Herrenschmidt
2004-01-08 23:26 ` New FBDev patch Russell King
2004-01-09 19:54 ` James Simmons
2004-01-11 12:09 ` Russell King
2004-01-09 17:17 ` Kronos [this message]
2004-01-09 20:06 ` 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=20040109171733.GA13027@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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).