From: Giulio Benetti <giulio.benetti@micronovasrl.com>
To: netdev@vger.kernel.org
Subject: Re: macb phy address bug?
Date: Tue, 18 Nov 2008 12:54:10 +0100 [thread overview]
Message-ID: <gfuad2$907$1@ger.gmane.org> (raw)
In-Reply-To: 492281C9.6060006@st.com
Giuseppe CAVALLARO wrote:
> In my opinion, we need to rework this patch again for two reasons:
> 1) it doesn't cover the case when the PHYID is 0xffffffff.
> 2) we need to add an explicit comment on the PHYID check to highlight that
> this is a work-around the broken hardware (in case we get 0xffff or
> 0x0).
> I've also tested it on several PHY devices: e.g. smsc lan 8700, ste101p,
> ste100p,
> DP83865 National GPHY.
> Where, for some of these, we need to treat the phyid=0 as wrong UID.
> Please, review the attached patch.
>
> Regards,
> Peppe
>
> David Miller wrote:
>> I've applied this patch to net-2.6, thanks.
>>
>> As mentioned there is some rare chance that the new
>> zero test could cause problems, in which case we'll
>> need to undo that part.
>> --
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
You're right on hardware, it's my fault. The problem is on the primitives of
mdio from atmel, I will patch them.
Giulio
next prev parent reply other threads:[~2008-11-18 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 9:50 macb phy address bug? David Miller
2008-11-18 8:50 ` Giuseppe CAVALLARO
2008-11-18 11:54 ` Giulio Benetti [this message]
2008-11-18 15:35 ` Giuseppe CAVALLARO
2008-11-20 9:04 ` David Miller
2008-11-20 15:59 ` Giuseppe CAVALLARO
-- strict thread matches above, loose matches on Subject: below --
2008-11-14 7:53 Giulio Benetti
2008-11-14 8:46 ` Giuseppe CAVALLARO
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='gfuad2$907$1@ger.gmane.org' \
--to=giulio.benetti@micronovasrl.com \
--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).