From: Chris Baker <bakerc@pacbell.net>
To: space19@earthlink.net
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Asante 10/100 Rev. b now working!
Date: 14 Sep 1999 19:44:17 -0700 [thread overview]
Message-ID: <87ogf4ki66.fsf@perisphere.worldsfair> (raw)
In-Reply-To: Shawn Anderson's message of "Tue, 14 Sep 1999 04:45:15 -0600"
Shawn Anderson <space19@earthlink.net> writes:
> Forwarded from the linux-tulip mailing list:
[...]
> That's the problem.
> The pre-0.91j Tulip drivers work on the PowerPC, but used the descriptor
> byte-swapping feature of the Tulip so that the driver wouldn't need to
> byte
> swap on the PPC. (It still must in the setup, but not during
> operation.)
>
> But the most of the Tulip clones, including the PNIC, didn't both to
> implement the byte-swap feature.
>
> I used to advise just buying a real Tulip board. But I decided that I
> had
> spent way too much answering "bug" reports, and it was only going to get
> worse with the increasing number of clone chips. So the v0.91j and
> later
> drivers have explicit byte swapping.
>
> Get the new driver from
> http://cesdis.gsfc.nasa.gov/linux/drivers/kern-2.3/index.html
> ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/kern-2.3/
>
> You *must* get the new support files (k_compat.h pci-netif.[ch]) as
> well!
This is great! This should also help all the Pacbell DSL customers
that got free KNE110's. Shawn, thanks for tracking this down.
Anyway, now the bad news: I'm running R4 on the machine in question.
When I try to compile pci-netif.c I get the following output:
pci-netif.c: In function `pci_find_capability':
pci-netif.c:342: `PCI_STATUS_CAP_LIST' undeclared (first use this function)
pci-netif.c:342: (Each undeclared identifier is reported only once
pci-netif.c:342: for each function it appears in.)
pci-netif.c:344: `PCI_CAPABILITY_LIST' undeclared (first use this function)
pci-netif.c: In function `acpi_wake':
pci-netif.c:364: `PCI_CAP_ID_PM' undeclared (first use this function)
pci-netif.c: In function `acpi_set_pwr_state':
pci-netif.c:396: `PCI_CAP_ID_PM' undeclared (first use this function)
The rest of the package seems to be designed to work with older
kernels (I'm using 2.1.130), so I suspect that this is a ppc specific
problem. Does anyone have any ideas?
TIA,
cbb
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~1999-09-15 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37DE273B.97EB1DBC@earthlink.net>
1999-09-15 2:44 ` Chris Baker [this message]
1999-09-15 22:35 Asante 10/100 Rev. b now working! Ira K Weiny
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=87ogf4ki66.fsf@perisphere.worldsfair \
--to=bakerc@pacbell.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
--cc=space19@earthlink.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).