From: Philippe Anel <xigh@free.fr>
To: Greg Bacon <gbacon@hiwaay.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Radeon and fossil
Date: Thu, 17 Jun 2004 11:37:11 +0200 [thread overview]
Message-ID: <6.1.1.1.0.20040617113349.0246c780@pop.free.fr> (raw)
In-Reply-To: <10d11j16pr5bl57@corp.supernews.com>
Hello,
At 11:05 AM 6/17/2004, you wrote:
>I have a box with a Radeon 7000. I found Philippe Anel's driver,
>but his howto seems to be geared toward a kfs install rather than
>fossil.
I don't understand that point.
>Is there a more sensible way of making the edits -- no rio, remember --
>than copying into /n/c (or /n/a), updating, mounting a -AWP view,
>copying the modified sources back, and rebuiling the kernel and aux/vga?
Hmm, you can use ed(1) ... :)
>Will the mkfiles need modification to run under /n/fossil?
No.
>Thanks,
>Greg
Philippe.
prev parent reply other threads:[~2004-06-17 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 9:05 Greg Bacon
2004-06-17 9:37 ` Philippe Anel [this message]
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=6.1.1.1.0.20040617113349.0246c780@pop.free.fr \
--to=xigh@free.fr \
--cc=9fans@cse.psu.edu \
--cc=gbacon@hiwaay.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).