From: Chad A Daelhousen <cd9@cse.Buffalo.EDU>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Dominique Dumont <domi.dumont@free.fr>
Subject: Re: Missing radeonfb documentation in kernel doc (fwd)
Date: Mon, 3 May 2004 15:38:43 -0400 [thread overview]
Message-ID: <20040503193843.GA24446@armstrong.cse.Buffalo.EDU> (raw)
In-Reply-To: <Pine.GSO.4.58.0405031952180.27296@waterleaf.sonytel.be>
At Mon, May 03, 2004 at 07:52:42PM +0200, Geert Uytterhoeven wrote:
> ---------- Forwarded message ----------
> Date: Mon, 03 May 2004 19:15:40 +0200
> From: Dominique Dumont <domi.dumont@free.fr>
> To: Geert Uytterhoeven <geert@linux-m68k.org>
> Subject: Missing radeonfb documentation in kernel doc
>
>
> Hello Geert
>
> I'm wrestling with radeonfb for my Radeon 9200 board.
>
> I've finally found some interesting doc [1]. Unfortunately, its
> licence [2] does not permit a copy in the kernel sources, but could
> you please at least mention the URL ?
Ah, crud, stale license :/
I've been maintaining that somewhere else[1] now, and relicensed it
under Creative Commons by-sa 1.0.
[1] http://www.cse.buffalo.edu/~cd9/radeonfb.html
--
Chad Daelhousen
My opinions are my own, unless UB purchases my soul.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-05-03 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 17:52 Missing radeonfb documentation in kernel doc (fwd) Geert Uytterhoeven
2004-05-03 19:38 ` Chad A Daelhousen [this message]
2004-05-13 14:17 ` S3triofb, pm3fb, retz3fb: abandoned? David Eger
2004-05-13 14:26 ` Romain Dolbeau
2004-05-13 14:42 ` Geert Uytterhoeven
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=20040503193843.GA24446@armstrong.cse.Buffalo.EDU \
--to=cd9@cse.buffalo.edu \
--cc=benh@kernel.crashing.org \
--cc=domi.dumont@free.fr \
--cc=geert@linux-m68k.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).