From: Jens Osterkamp <jens@de.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: netdev@vger.kernel.org, James K Lewis <jim@jklewis.com>,
linuxppc-dev@ozlabs.org, jgarzik@pobox.com,
cbe-oss-dev@ozlabs.org
Subject: Re: spidernet: dynamic phy setup code
Date: Thu, 1 Feb 2007 11:50:51 +0100 [thread overview]
Message-ID: <200702011150.52199.jens@de.ibm.com> (raw)
In-Reply-To: <1169842902.24996.108.camel@localhost.localdomain>
On Friday 26 January 2007 9:21 pm, Benjamin Herrenschmidt wrote:
> Can't we have a device-tree property indicating wether to use fiber or
> copper ?
Well, yes, I am sure we could, but what would be the benefit of doing so
if we can get the same information dynamically ?
Jens
next prev parent reply other threads:[~2007-02-01 10:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 13:09 spidernet: dynamic phy setup code Jens Osterkamp
2007-01-26 17:58 ` Linas Vepstas
[not found] ` <200701262150.52882.jens@de.ibm.com>
2007-01-26 22:15 ` Linas Vepstas
2007-01-26 22:30 ` Jens Osterkamp
2007-01-26 20:21 ` Benjamin Herrenschmidt
2007-02-01 10:50 ` Jens Osterkamp [this message]
2007-02-01 8:05 ` [Cbe-oss-dev] " Ishizaki Kou
2007-02-01 11:04 ` Jens Osterkamp
2007-02-02 10:20 ` Ishizaki Kou
2007-02-05 0:08 ` Benjamin Herrenschmidt
2007-02-02 10:29 ` [RFC/PATCH 2.6.20-rc6 1/4] spidernet: autoneg support for Celleb Ishizaki Kou
2007-02-02 10:30 ` [RFC/PATCH 2.6.20-rc6 2/4] spidernet: load firmaware when open Ishizaki Kou
2007-02-02 10:31 ` [RFC/PATCH 2.6.20-rc6 3/4] spidernet: add support for Celleb Ishizaki Kou
2007-02-02 10:33 ` [RFC/PATCH 2.6.20-rc6 4/4] spidernet: remove txram full logging Ishizaki Kou
2007-02-04 23:44 ` [Cbe-oss-dev] spidernet: dynamic phy setup code Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2007-02-01 7:54 kou.ishizaki
2007-02-06 10:42 ` spidernet: dynamic phy setup code Ishizaki Kou
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=200702011150.52199.jens@de.ibm.com \
--to=jens@de.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=jgarzik@pobox.com \
--cc=jim@jklewis.com \
--cc=linuxppc-dev@ozlabs.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).