From: Dan Faerch <dan@hacker.dk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Tejun Heo <htejun@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Deepak Saxena <dsaxena@plexity.net>,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: ata and netdev (was Re: -mm merge plans for 2.6.23)
Date: Wed, 11 Jul 2007 18:47:55 +0200 [thread overview]
Message-ID: <469509BB.9050405@hacker.dk> (raw)
In-Reply-To: <20070710112458.e9dbb55e.akpm@linux-foundation.org>
Andrew Morton wrote:
> drivers-net-ns83820c-add-paramter-to-disable-auto.patch:
>
> See comments in changelog: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/drivers-net-ns83820c-add-paramter-to-disable-auto.patch
>
> Dan, Ben: is there any prospect of progress here?
Mmm.. Ben had 2 comments last year:
In regards to the ethtool stuff i coded:
> This part is good, although doing something for copper cards needs doing,
I know very little about hardware and only own the fiber version of this
card. Even if i tried to make code for the copper version, it would
probably blow it up the phy and set the switches on fire ;).
And in regards to the '"disable_autoneg" module argument':
> This is the part I disagree with. Are you sure it isn't a bug in the
> link autonegotiation state machine for fibre cards? It should be defaulting
> to 1Gbit/full duplex if no autonegotiation is happening, and if it isn't
> then that should be fixed instead of papering over things with a config
> option.
This is pretty much Russian to me.
I wouldnt know where to find the "link-autonegotiation-state-machine-for-fibre-cards" or know what to do with it anyway :).
The "disable_autoneg" is a convenient feature (for me and the other guy who made the same patch last year) and i consider it a harmless feature in every way.
It is simply an 'if'-statement, that skips the "start autoneg" function upon load.
We can simply remove the feature entirely if it is deemed undesirable.
So in conclusion:
- I vote "use the patch as-is", but im fine with it being changed.
- If it needs support for copper, someone else has to code it.
Regards
- Dan
next prev parent reply other threads:[~2007-07-11 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070710013152.ef2cd200.akpm@linux-foundation.org>
2007-07-10 17:42 ` ata and netdev (was Re: -mm merge plans for 2.6.23) Jeff Garzik
2007-07-10 18:24 ` Andrew Morton
2007-07-10 18:55 ` James Bottomley
2007-07-10 18:57 ` Jeff Garzik
2007-07-10 20:31 ` Sergei Shtylyov
2007-07-10 20:35 ` Andrew Morton
2007-07-11 16:47 ` Dan Faerch [this message]
2007-07-10 19:56 ` Sergei Shtylyov
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=469509BB.9050405@hacker.dk \
--to=dan@hacker.dk \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=dsaxena@plexity.net \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).