From: phaet0n <phaet0n@hotmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] mga4xx driver issues
Date: Mon, 1 Oct 2001 09:50:54 +0000 [thread overview]
Message-ID: <758512ed.0109271433.6cf961ce@posting.google.com> (raw)
Philippe,
I'm having problems building the aux/vga
binary with the mgaG4xx driver. I get
the following errors:
mga4xx.c:521 not a member of struct/union: rid
mga4xx.c:522 not a member of struct/union: rid
mga4xx.c:530 not a member of struct/union: rid
Checking pci.h reveals that there is no
field called rid in Pcidev. I believe
that I am up-to-date wrt updates. However
I'm unsure that my method for building,
which is running mk 'ARCH=pc' install in
/sys/src is correct. Is it? I build
kernels by running mk 'CONF=pcdisk' 9pcdisk
in /sys/src/9/pc. Is this ok as well?
I feel rusty all over again, but hopefully
this driver will get me back to 32bit
colour goodness. In any case, thanks for
your work. Hopefully with this I'll be
using plan9 exclusively.
next reply other threads:[~2001-10-01 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 9:50 phaet0n [this message]
2001-10-01 10:38 ` Boyd Roberts
2001-10-01 13:01 phaet0n
2001-10-01 16:16 Philippe Anel
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=758512ed.0109271433.6cf961ce@posting.google.com \
--to=phaet0n@hotmail.com \
--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).