From: Paul P Komkoff Jr <i@stingr.net>
To: linux-kernel@vger.kernel.org
Subject: Re: cs89x0 in 2.5 (was Re: eepro100 - 802.1q - mtu size)
Date: Fri, 17 Jan 2003 23:14:45 +0300 [thread overview]
Message-ID: <20030117201445.GS12676@stingr.net> (raw)
In-Reply-To: <20030117174928.GA8304@gtf.org>
Replying to Jeff Garzik:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5/2.5.48/split-dj1/net-cs89x0-media-corrections.diff
>
>
> IIRC it came from -ac tree without explanation, and I think akpm said it
> broke stuff. Since it has an alive maintainer (akpm), I would rather
> let Alan and Andrew fight it out :) Whatever they decide is fine with
> me for 2.5.
It is not a magic number in net drivers. I was author of this bit, and
without it I cannot start onboard nic on IBM PC300 GL (a lot of them I
have here). Actually, to _understand_ what this bit do you just need
to look at the driver source and see _how_ it works with
A_CNF_MEDIA_10B_2 constants. More specific, it expects that there are
single bits, and before my patch A_CNF_MEDIA_10B_2 was 0x60. 0x60 is
not a single bit.
I've thought this change is obvious, and as far as I can remember
Andrew has nothing against it.
--
Paul P 'Stingray' Komkoff Jr /// (icq)23200764 /// (http)stingr.net
This message represents the official view of the voices in my head
next prev parent reply other threads:[~2003-01-17 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 14:53 eepro100 - 802.1q - mtu size Florian Lohoff
2003-01-17 16:08 ` Paul P Komkoff Jr
2003-01-17 16:28 ` Jeff Garzik
2003-01-17 17:27 ` Dave Jones
2003-01-17 17:49 ` cs89x0 in 2.5 (was Re: eepro100 - 802.1q - mtu size) Jeff Garzik
2003-01-17 20:14 ` Paul P Komkoff Jr [this message]
2003-01-21 2:17 ` Alan
2003-01-21 23:39 ` Jeff Garzik
2003-01-17 17:48 ` eepro100 - 802.1q - mtu size Ducrot Bruno
2003-01-17 19:25 ` Florian Lohoff
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=20030117201445.GS12676@stingr.net \
--to=i@stingr.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.