linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlo E. Prelz" <fluido@fluido.as>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Re: FBDEV 2.6.0-test7 updates.
Date: Thu, 16 Oct 2003 12:19:05 +0200	[thread overview]
Message-ID: <20031016101905.GA7454@casa.fluido.as> (raw)
In-Reply-To: <1066298431.1407.119.camel@gaston>

	Subject: Re: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
	Date: gio, ott 16, 2003 at 12:00:32 +0200

Quoting Benjamin Herrenschmidt (benh@kernel.crashing.org):

> My new driver (bk://ppc.bkbits.net/linuxppc-2.5-benh) now uses a copy
> of XFree PCI IDs list, making it much easier to keep in sync. It should
> also support the 9200.

The latest (*NON*bk) patch distributed by James appears to include your
new driver. The header from radeon_base.c  reads:

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

/*
 *      drivers/video/radeonfb.c
 *      framebuffer driver for ATI Radeon chipset video boards
 *
 *      Copyright 2003  Ben. Herrenschmidt <benh@kernel.crashing.org>
 *      Copyright 2000  Ani Joshi <ajoshi@kernel.crashing.org>
 *
 *      i2c bits from Luca Tettamanti <kronos@kronoz.cjb.net>
 *
 *      Special thanks to ATI DevRel team for their hardware donations.
 *
 *      ...Insert GPL boilerplate here...
 *
 *      TODO: - Bring a couple of cleanups from 2.4 to the mode setting code,
 *            - Split CRT vs. FP register calc/setting
 *            - Add CRTC2 support for mirror at least, dual head then
 *            - Add back some accel
 *
 */


#define RADEON_VERSION  "0.2.0"

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--


Thus the rest of my previous message should be referred to
your new driver.

Carlo

PS I am BK-handicapped. I had downloaded the program, and tried your
instruction as per an old message of yours, and no download would take
place. Since, if I recall correctly, bk cannot be used for free on
closed-source projects, I cannot switch to it (nor lose too much time
on it): I work on projects of both types, and changing every time
between RCS/CVS and bk would be very umcomfortable.

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  reply	other threads:[~2003-10-16 10:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 22:59 FBDEV 2.6.0-test7 updates James Simmons
2003-10-15 23:17 ` Andrew Morton
2003-10-15 23:22   ` James Simmons
2003-10-15 23:20 ` Andrew Morton
2003-10-15 23:27   ` James Simmons
2003-10-16  9:19     ` Carlo E. Prelz
2003-10-16  9:29       ` Sven Luther
2003-10-17 16:48         ` James Simmons
2003-10-16 10:00       ` Benjamin Herrenschmidt
2003-10-16 10:19         ` Carlo E. Prelz [this message]
2003-10-16 10:41           ` Benjamin Herrenschmidt
2003-10-16 10:48             ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-16 10:42           ` Benjamin Herrenschmidt
2003-10-17 10:04             ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-17 10:49               ` Benjamin Herrenschmidt
2003-10-17 11:10                 ` Carlo E. Prelz
2003-10-17 11:16                   ` Benjamin Herrenschmidt
2003-10-17 14:44                     ` [Linux-fbdev-devel] " Kronos
2003-10-17 17:29                       ` James Simmons
2003-10-18 21:28                   ` [Linux-fbdev-devel] " Pavel Machek
2003-10-17 17:40                 ` James Simmons
2003-10-17 14:26               ` [Linux-fbdev-devel] " Kronos
2003-10-16 21:06         ` Otto Solares
2003-10-17 10:30           ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 16:52           ` James Simmons
2003-10-17 19:34             ` [Linux-fbdev-devel] " Jon Smirl
2003-10-17 19:50               ` Dave Jones
2003-10-17 22:42       ` Jon Smirl
2003-10-16  0:24   ` Michel Dänzer
2003-10-16  8:19   ` Benjamin Herrenschmidt
2003-10-17 16:45     ` [Linux-fbdev-devel] " James Simmons
2003-10-16  5:08 ` Jan De Luyck
2003-10-17 16:44   ` James Simmons
2003-10-16  5:17 ` Jan De Luyck
2003-10-16 10:44 ` Adrian Bunk
2003-10-16 17:48   ` James Simmons
2003-10-16 19:58 ` Geert Uytterhoeven
2003-10-16 20:40   ` [Linux-fbdev-devel] " Sam Ravnborg
2003-10-17 11:18   ` Benjamin Herrenschmidt
2003-10-17 17:25     ` [Linux-fbdev-devel] " James Simmons
2003-10-17 17:45       ` Torrey Hoffman
2003-10-17 17:23   ` [Linux-fbdev-devel] " 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=20031016101905.GA7454@casa.fluido.as \
    --to=fluido@fluido.as \
    --cc=benh@kernel.crashing.org \
    --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).