From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mircea Damian <dmircea@linux.kappa.ro>, linux-kernel@vger.kernel.org
Subject: Re: do NOT compile 2.2.18 with egcs-1.1.2
Date: Thu, 14 Dec 2000 11:38:13 +0100 [thread overview]
Message-ID: <20001214113813.C9662@werewolf.able.es> (raw)
In-Reply-To: <20001214102145.B17934@linux.kappa.ro> <E146VXg-00045d-00@the-village.bc.nu>
In-Reply-To: <E146VXg-00045d-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 14, 2000 at 11:23:14 +0100
On Thu, 14 Dec 2000 11:23:14 Alan Cox wrote:
> > I just want to let other know that kernel 2.2.18 does not work properly (*)
> > on my box if I compile it with egcs-2.91.66 19990314/Linux (egcs-1.1.2
> > release). Instead gcc-2.7.2.3 works ok.
> >
> > (*) the network driver PCI NE2000 does not work with all three cards. It
> > just sees them but they do not work.
>
> I don't believe that is likely to be the reason. The driver has not changed
> since 2.2.15 if not earlier, and it still seems to work with the cards I have
> here (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>
> Alan
I use 2.2.18 with ne2k-pci from kernel and that of scyld, and work fine under
2.91 (egcs)
BTW, when a resync of 2.2 net drivers with scyld ? perhaps 2.2.19 ?
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
Linux werewolf 2.2.18-aa1 #1 SMP Mon Dec 11 21:26:28 CET 2000 i686
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-14 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 8:21 do NOT compile 2.2.18 with egcs-1.1.2 Mircea Damian
2000-12-14 10:23 ` Alan Cox
2000-12-14 10:38 ` J . A . Magallon [this message]
2000-12-14 10:51 ` Alan Cox
2000-12-14 14:01 ` J . A . Magallon
2000-12-14 14:38 ` Mircea Damian
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=20001214113813.C9662@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmircea@linux.kappa.ro \
--cc=linux-kernel@vger.kernel.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