linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kronos <kronos@kronoz.cjb.net>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Petr Vandrovec <VANDROVE@vc.cvut.cz>
Subject: Re: framebuffer_{alloc,release}
Date: Tue, 23 Sep 2003 17:49:29 +0200	[thread overview]
Message-ID: <20030923154929.GA4240@dreamland.darkstar.lan> (raw)
In-Reply-To: <Pine.LNX.4.44.0309222223310.6431-100000@phoenix.infradead.org>

Il Mon, Sep 22, 2003 at 10:24:04PM +0100, James Simmons ha scritto: 
> This is acceptable. I applied your changes.

Good. I've just finished matroxfb, you can do a bk pull from:

bk://mesa3d.bkbits.net/fbdev-2.5

This will update the following files:

 drivers/video/Kconfig                   |   20 
 drivers/video/matrox/g450_pll.c         |  166 +++---
 drivers/video/matrox/g450_pll.h         |    6 
 drivers/video/matrox/i2c-matroxfb.c     |   18 
 drivers/video/matrox/matroxfb_DAC1064.c |  586 ++++++++++++------------
 drivers/video/matrox/matroxfb_DAC1064.h |    4 
 drivers/video/matrox/matroxfb_Ti3026.c  |  256 +++++-----
 drivers/video/matrox/matroxfb_accel.c   |  130 ++---
 drivers/video/matrox/matroxfb_accel.h   |    2 
 drivers/video/matrox/matroxfb_base.c    |  778 +++++++++++++++-----------------
 drivers/video/matrox/matroxfb_base.h    |   76 ---
 drivers/video/matrox/matroxfb_crtc2.c   |  259 +++++-----
 drivers/video/matrox/matroxfb_crtc2.h   |    2 
 drivers/video/matrox/matroxfb_g450.c    |  162 +++---
 drivers/video/matrox/matroxfb_g450.h    |    8 
 drivers/video/matrox/matroxfb_maven.c   |   38 -
 drivers/video/matrox/matroxfb_misc.c    |  264 +++++-----
 drivers/video/matrox/matroxfb_misc.h    |   10 
 18 files changed, 1355 insertions(+), 1430 deletions(-)

through these ChangeSets:

<kronos@kronoz.cjb.net> (03/09/23 1.1290)
   Port driver to the new framebuffer_{alloc,release} API.

<kronos@kronoz.cjb.net> (03/09/21 1.1289)
   Remove FB_MATROX_MULTIHEAD and helper macros.
   Now minfo is always dynamically allocated.


Luca
-- 
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
"La mia teoria scientifica preferita e` quella secondo la quale gli 
 anelli di Saturno sarebbero interamente composti dai bagagli andati 
 persi nei viaggi aerei." -- Mark Russel


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-23 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 16:01 framebuffer_{alloc,release} Kronos
2003-09-22 21:24 ` framebuffer_{alloc,release} James Simmons
2003-09-23 15:49   ` Kronos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-16 19:27 framebuffer_{alloc,release} Kronos
2003-09-17  8:52 ` framebuffer_{alloc,release} Sven Luther
2003-09-17 15:47   ` framebuffer_{alloc,release} Kronos
2003-09-17 19:11 ` framebuffer_{alloc,release} 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=20030923154929.GA4240@dreamland.darkstar.lan \
    --to=kronos@kronoz.cjb.net \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=jsimmons@infradead.org \
    --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).