From: Otto Wyss <otto.wyss@orpatec.ch>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [linux-2.6.10] radeonfb / oops
Date: Sat, 05 Feb 2005 11:40:25 +0100 [thread overview]
Message-ID: <4204A298.456AC16F@orpatec.ch> (raw)
In-Reply-To: Pine.LNX.4.56.0502042158250.26459@pentafluge.infradead.org
Could anyone move the newest sources of the radeonfb to the CVS of
linux-fbdev, set up the kbuild makefile (see threat
"http://sourceforge.net/mailarchive/forum.php?thread_id=5626720&forum_id=2357")
and maintain it? Just tell me your sourceforge.net account and I give
you access rights. Look at the ??? driver as Toni had done it (see "http://cvs.sf.net/viewcvs.py/linux-fbdev/FBdev/drivers/i810fb/Readme?view=markup").
BTW any framebuffer driver maintainer can do it if he wants.
O. Wyss
--
Development of frame buffer drivers: http://linux-fbdev.sf.net
Sample code snippets for wxWidgets: http://wxcode.sf.net
How to build well-designed applications: http://wxguide.sf.net
Desktop with a consistent look and feel: http://wyodesktop.sf.net
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-05 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 8:25 [linux-2.6.10] radeonfb / oops Paweł Sikora
2005-02-04 5:59 ` Benjamin Herrenschmidt
2005-02-04 20:42 ` James Simmons
2005-02-04 21:04 ` Jon Smirl
2005-02-04 21:17 ` Otto Wyss
2005-02-04 21:59 ` James Simmons
2005-02-05 0:36 ` Jon Smirl
2005-02-05 10:40 ` Otto Wyss [this message]
2005-02-04 20:42 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2005-02-12 15:39 Paweł Sikora
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=4204A298.456AC16F@orpatec.ch \
--to=otto.wyss@orpatec.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.