From: James Stevenson <james@stev.org>
To: borkdude@cs.utwente.nl
Cc: linux-kernel@vger.kernel.org, andrewm@uow.edu.au, netdev@oss.sgi.com
Subject: Re: 3c59x support
Date: 01 May 2003 00:17:21 +0100 [thread overview]
Message-ID: <1051744645.2308.11.camel@god.stev.org> (raw)
In-Reply-To: <200304290202.02811.borkdude@cs.utwente.nl>
Hi
i also had problems with the card in some 2.4.x releases
but it seems to work for me on a 2.4.20 kernel.
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:0a.0: 3Com PCI 3c905C Tornado at 0xec00. Vers LK1.1.16
i do still have problems with a card in another machine when rebooting
from windows into linux it fails to init properly.
But since the machine boots from nfs i have not been bothered to
dump the info from this.
On Tue, 2003-04-29 at 01:02, Michiel Borkent wrote:
> Hello,
> I am trying to make a 2.4.20 kernel with 3c59x support.
> My card is a:
>
> 3Com 3c900 Cyclone 10Mbps TPO
>
> card and it only works with the 3c59x-scyld module, I found with Debian Woody
> with a linux v2.2 kernel.
>
> It does NOT work with the normal 3c59x module and as I am trying to make a
> 2.4.20 kernel, it still doesn't work. I chose support for "Vortex/Boomerang"
> and normally my card would be supported I think.
>
> Can someone help me with this?
>
> Greetings,
> Michiel Borkent
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-04-30 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 0:02 3c59x support Michiel Borkent
2003-04-29 11:46 ` Bogdan Costescu
2003-04-30 23:17 ` James Stevenson [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=1051744645.2308.11.camel@god.stev.org \
--to=james@stev.org \
--cc=andrewm@uow.edu.au \
--cc=borkdude@cs.utwente.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).