From: David Updegraff <dave@cray.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] multicast tftp: RFC2090
Date: Tue, 01 May 2007 11:41:01 -0500 [thread overview]
Message-ID: <46376D9D.9050104@cray.com> (raw)
In-Reply-To: <2acbd3e40705010916v4d9ae9e3pa6565b8078f3059e@mail.gmail.com>
Andy
whoops! I see your point now! the parse_sr shouldn't be taking the
stab at determining lnk.etc. if the curphy != generic I guess.
> On 5/1/07, David Updegraff <dave@cray.com> wrote:
>> Here is a first pass; not yet request for merge.
>>
>> Only have been able to test with 8343 TSEC and an old SC520-based
>> rtl8139 so far, and with only two concurrent downloads; against atftpd
>> server. Re-cycling the existing ext2 bitmap functions to do housekeeping.
>>
>> In about a month I should have access to enough hardware to test 20+
>> concurrent tftpboots.
>>
>> Suggestions & comments appreciated.
>
> I have to NACK this portion:
>
> @@ -378,6 +378,28 @@ uint mii_parse_sr(uint mii_reg, struct tsec_private
> * priv)
> priv->link = 1;
> }
>
> + /* take a stab at 10/100 and Duplex info too; from linux mii.c */
> + mii_reg = (read_phy_reg(priv, PHY_ANAR) & read_phy_reg(priv,
> PHY_ANLPAR));
> + if ( mii_reg & PHY_ANLPAR_TXFD ) {
> + priv->duplexity = 1;
> + priv->speed = 100;
> + }
> + else if ( mii_reg & PHY_ANLPAR_TX ) {
> + priv->duplexity = 0;
> + priv->speed = 100;
> + }
> + else if ( mii_reg & PHY_ANLPAR_TX ) {
> + priv->duplexity = 0;
> + priv->speed = 100;
> + }
> + else if ( mii_reg & PHY_ANLPAR_10FD ) {
> + priv->duplexity = 1;
> + priv->speed = 10;
> + } else {
> + priv->duplexity = 0;
> + priv->speed = 10;
> + }
> +
> return 0;
> }
>
> @@ -1056,6 +1078,26 @@ struct phy_info phy_info_VSC8244 = {
> {miim_end,}
> },
> };
> +/* a generic flavor. */
> +struct phy_info phy_info_generic = {
> + 0,
> + "Unknown/Generic PHY",
> + 32,
> + (struct phy_cmd[]) { /* config */
> + {PHY_BMCR, PHY_BMCR_RESET, NULL},
> + {PHY_BMCR, PHY_BMCR_AUTON|PHY_BMCR_RST_NEG, NULL},
> + {miim_end,}
> + },
> + (struct phy_cmd[]) { /* startup */
> + {PHY_BMSR, miim_read, NULL},
> + {PHY_BMSR, miim_read, &mii_parse_sr},
> + {miim_end,}
> + },
> + (struct phy_cmd[]) { /* shutdown */
> + {miim_end,}
> + }
> +};
> +
>
> struct phy_info phy_info_dm9161 = {
> 0x0181b88,
> @@ -1203,6 +1245,7 @@ struct phy_info *phy_info[] = {
> &phy_info_lxt971,
> &phy_info_VSC8244,
> &phy_info_dp83865,
> + &phy_info_generic,
> NULL
> };
>
>
> Sadly, I've already applied it to my tree, but I've just determined
> that it breaks gigabit links, even on boards with known PHYs.
>
> I'm going to fix that, but these two hunks need to be in a separate
> patch, anyway. I will post the updated version.
>
> Andy
next prev parent reply other threads:[~2007-05-01 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 15:19 [U-Boot-Users] multicast tftp: RFC2090 David Updegraff
2007-04-24 16:27 ` Wolfgang Denk
2007-04-24 16:27 ` Ben Warren
2007-04-24 16:34 ` David Updegraff
2007-05-01 15:29 ` David Updegraff
2007-05-01 16:16 ` Andy Fleming
2007-05-01 16:41 ` David Updegraff [this message]
2007-05-01 19:00 ` Andy Fleming
2007-05-18 17:05 ` David Updegraff
2007-05-19 1:26 ` Jerry Van Baren
2007-05-19 1:52 ` David Updegraff
[not found] <1181312200.8300.81.camel@saruman.qstreams.net>
2007-06-08 15:24 ` Ben Warren
2007-06-08 15:39 ` Wolfgang Denk
2007-06-08 15:41 ` David Updegraff
2007-06-08 18:35 ` Ben Warren
2007-06-08 18:48 ` Wolfgang Denk
2007-06-08 18:51 ` Ben Warren
2007-06-08 19:31 ` David Updegraff
2007-06-11 15:41 ` David Updegraff
2007-06-11 20:29 ` Wolfgang Denk
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=46376D9D.9050104@cray.com \
--to=dave@cray.com \
--cc=u-boot@lists.denx.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