From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jordan Benjamin <jordanb@caltech.edu>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb & fbdev code status
Date: Sun, 16 Nov 2003 18:20:29 +1100 [thread overview]
Message-ID: <1068967229.4645.64.camel@gaston> (raw)
In-Reply-To: <EFF3F4D4-1804-11D8-A894-0003931DDB42@caltech.edu>
On Sun, 2003-11-16 at 18:17, Jordan Benjamin wrote:
> Thanks for a very informative reply. My only other question now is:
> where can I find the current radeonfb code? I apologize if this should
> be obvious to me (I do have an excuse though--I'm recovering from
> throat surgery and on a lot of painkillers!). Thanks,
The up-to-date version of the "new" driver can always be found in
my "powermac" tree which, I suppose, will work just fine on non-pmac
as well and is available either via bk
(bk://ppc.bkbits.net/linuxppc-2.5-benh) or via rsync
(source.mvista.org::linuxppc-2.5-benh)
I think the current fbdev patches have a fairly recent version too,
but I'd prefer if we did the debugging using my tree so I can push
updates along as we find problems
Ben.
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
next prev parent reply other threads:[~2003-11-16 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 20:51 radeonfb & fbdev code status Jordan Benjamin
2003-11-16 5:05 ` Benjamin Herrenschmidt
2003-11-16 7:17 ` Jordan Benjamin
2003-11-16 7:20 ` Benjamin Herrenschmidt [this message]
2003-11-16 7:34 ` John Zielinski
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=1068967229.4645.64.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jordanb@caltech.edu \
--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).