From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/cmd/aux/vga/3dfx.c
Date: Tue, 30 Apr 2002 11:58:36 +0100 [thread overview]
Message-ID: <f1847cb0b38313aded74678c9ad77c9c@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
it needs the plan 9 c compiler, but
it's not actually the kernel that's at fault here: aux/vga is
a user-level program, and it's in the bzip'd file
system on the diskette. i've put a modified diskette image that
might work on http://www.vitanuova.com/ndisk.gz;
you'll need to replace plan9.ini by the one you've been using.
[-- Attachment #2: Type: message/rfc822, Size: 2450 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/cmd/aux/vga/3dfx.c
Date: Tue, 30 Apr 2002 09:35:09 GMT
Message-ID: <9d21a718.0204291131.4757a61d@posting.google.com>
Should applying this patch enable one to install on a system using a
3dfx Voodoo3 2000 AGP card? I was having problems starting rio.
Since I don't have a successful installation yet to recompile from, is
there any way to make this change to the kernel of the installation
boot floppy? Can the Plan 9 kernel source be recompiled with GCC under
FreeBSD or Linux or does it require the Plan 9 C compiler?
Thanks,
CJayC
forsyth@caldo.demon.co.uk wrote in message news:<9feae800a6ef4819082f8895aa5d3f29@caldo.demon.co.uk>...
> this has been wrong for ages but only blew up in the new release:
> the aux/vga 3dfx code was dividing just once too often.
>
> term% yesterday -d 3dfx.c
> diff /n/dump/2002/04291/sys/src/cmd/aux/vga/3dfx.c 3dfx.c
> 30c30
> < ulong r[Nior/4];
> ---
> > ulong r[Nior];
next reply other threads:[~2002-04-30 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 10:58 forsyth [this message]
2002-05-07 12:00 ` CJayC
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 14:18 forsyth
2002-05-17 9:09 ` CJayC
2002-04-29 9:30 forsyth
2002-04-30 9:35 ` CJayC
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=f1847cb0b38313aded74678c9ad77c9c@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).