From: "Seewer Philippe" <philippe.seewer@bfh.ch>
To: "Don Fry" <brazilnut@us.ibm.com>
Cc: <tsbogend@alpha.franken.de>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH 1/2] pcnet32: Introduce basic AT 2700/01 FTX support
Date: Fri, 17 Feb 2006 21:12:52 +0100 [thread overview]
Message-ID: <43F62E44.2090109@bfh.ch> (raw)
In-Reply-To: <20060217182104.GA19257@us.ibm.com>
Don Fry wrote:
> Philippe,
>
> On a purely mechanical note, the patches do not apply cleanly because
> of whitespace changes. Possibly your mailer changed tabs to spaces,
> which causes the patch not to apply, and also causes your patch to have
> different spacing than the rest of the file. The driver does not
> conform to the 8-space indentation guideline/rule, but it is consistent
> in 4-space indentation.
uhhh.... did i forget to run Lindent..? Or was it that i just
selected-middle clicked them into thunderbird?
what's the recommended procedure oh how to append patches to
mails? (Documentation just says included not attached...)
>
> I am looking over this change and the following one, to try and
> understand what and why you made your changes.
>
> The change made by Thomas Bogendoerfer and modified by myself is much
> more flexible than your changes, in that they are not specific just to
> the Allied Telesyn boards with multiple Phys.
I'm not sure what you are talking about. I didn't see any PHY switching
code in the driver... And the specs specifically say that when more than
one PHY is connected control should revert to software.
> They also allow dynamic
> changing of cabling without requiring the driver to be removed/installed
> or the card power cycled. I also see little value in the module
> parameters, when it can be determined dynamically. Also, maxphy might be
> thought to the the maximum number of phys, rather than the maximum phy
> number supported. If static selection of the phy to use is passed in as
> a module parameter, why also include a maxphy?
maxphy is supposed to be how many PHYs are actually connected to the chip.
I didn't want to introduce a generic PHY scanner (which is possible)
because that would have haa impact on all cards not only cards that actually
have more than one phy.
I really tried to put this into pcnet32_open. But i just didn't work...
>
> As I review your patches I will follow up to the mailing list.
>
> On Fri, Feb 17, 2006 at 05:14:39PM +0100, Seewer Philippe wrote:
>
>>This patch extends Don Fry's last patch for AT 2700/01 FX to set the
>>speed/fdx options for the FTX variants of these cards as well.
>>
>>Additionally the option override has been moved from pcnet32_open to
>>pcnet32_probe1 because it's only necessary to override the options once.
>>
>>Tested and works.
>>
>>Patch applies to 2.6.16-rc3
>>
>
> Don Fry
> brazilnut@us.ibm.com
prev parent reply other threads:[~2006-02-17 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 16:14 [PATCH 1/2] pcnet32: Introduce basic AT 2700/01 FTX support Seewer Philippe
2006-02-17 18:21 ` Don Fry
2006-02-17 20:12 ` Seewer Philippe [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=43F62E44.2090109@bfh.ch \
--to=philippe.seewer@bfh.ch \
--cc=brazilnut@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).