public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Markus <midian@ihme.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4] forcedeth
Date: Sun, 09 Nov 2003 10:47:33 +0100	[thread overview]
Message-ID: <3FAE0D35.40908@colorfullife.com> (raw)

Markus wrote:

>I tested this driver for my Nforce2 mobo on 2.6.0-test9, and this driver
>seemed useless, it just printed some random numbers in my konsole (And
>trust me, it was hard to edit lilo.conf so I even could boot back to old
>kernel when all the numbers just were jumping around)
>
The driver has full debugging enabled, and that includes hexdumping the 
start of every packet. This should disappear if you replace the "#if 1" 
with "#if 0", around line 80.

> And it broke the
>other card too, ifconfig was right, now there was this card too, but no
>one from them worked. Thanks anyway.
>
Which other card? I'm interested in more details, please explain.

So far I received two bug reports:
- smp locking is broken (stupid bug, I have a fix)
- sometimes a wrong mac address is used (unresolved)

--
    Manfred


             reply	other threads:[~2003-11-09  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09  9:47 Manfred Spraul [this message]
2003-11-09 14:14 ` [PATCH 2.4] forcedeth Markus Hästbacka
2003-11-09 14:47   ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2003-11-08  5:47 Carl-Daniel Hailfinger
2003-11-08  8:54 ` Christoph Hellwig
2003-11-08 10:51   ` Krzysztof Halasa
2003-11-08 17:55   ` Jeff Garzik
2003-11-08 20:23     ` Carl-Daniel Hailfinger
2003-11-09  0:15     ` Zwane Mwaikambo
2003-11-08 17:39 ` Jeff Garzik
2003-11-08 20:26 ` Markus Hästbacka
2003-11-08 20:59   ` Valdis.Kletnieks
2003-11-08 21:38     ` Markus Hästbacka
2003-11-09 12:36   ` Carl-Daniel Hailfinger
2003-11-09 14:07     ` Markus Hästbacka

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=3FAE0D35.40908@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midian@ihme.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