From: Nelson Abramson <pogtal@erols.com>
To: Josh Kindler <josh@antihype.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: atyfb problems?
Date: Sun, 13 Aug 2000 11:33:17 -0400 [thread overview]
Message-ID: <3996BFBD.FD8DE0D7@erols.com> (raw)
In-Reply-To: B5BC31B9.2C74%josh@antihype.com
Josh Kindler wrote:
> Hmm... I jsut got the latest (as of last night) rsync of Ben's kernel. When
> I compiled it, I got the following error. Previous kernels compiled fine, is
> this a known issue or am I just stupid?
>
> atyfb.c:641: redefinition of `reset_GTC_3D_engine'
> atyfb.c:631: `reset_GTC_3D_engine' previously defined here
> <snip>
Try disabling ATI Mach support.
> Also I have an (AFAIK) unresolved airport problem:
> I can compile it fine, but then when I insmod it i get:
>
> airport.o: unresolved symbol isa_io_base
IIRC, this is in the list archives. (hint, search for the error)
HTH
--Nelson Abramson
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-13 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-13 16:06 atyfb problems? Josh Kindler
2000-08-13 15:33 ` Nelson Abramson [this message]
2000-08-14 20:34 ` Michael Schmitz
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=3996BFBD.FD8DE0D7@erols.com \
--to=pogtal@erols.com \
--cc=josh@antihype.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).