All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
	Francois Romieu <romieu@fr.zoreil.com>,
	Simon Arlott <simon@fire.lp0.eu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	Edward Hsu <edward_hsu@realtek.com.tw>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: r8169 MAC addresses broken
Date: Tue, 04 Nov 2008 19:49:42 +0100	[thread overview]
Message-ID: <49109946.7020702@redhat.com> (raw)
In-Reply-To: <490F0FCF.4060905@gmail.com>

Jiri Slaby wrote:
> On 11/03/2008 10:04 AM, Ivan Vecera wrote:
>> Jiri Slaby wrote:
>>> On 10/28/2008 02:45 PM, Krzysztof Halasa wrote:
>>>> Jiri Slaby <jirislaby@gmail.com> writes:
>>>>
>>>>>> Same thing if you unplug the battery ?
>>>>> Thanks, now it seems to be OK.
>>>> Well, perhaps reverting that patch was a bit premature?
>>> No, it helped after reverting that patch. I think we don't want defunct 2.6.28
>>> with these nics.
>> I cannot agree.
> 
> You want defunct r8169 in 2.6.28? Or cannot agree with what?
> 
>> IMO the problem was in the first version of the patch that didn't
>> check for invalid (zeroed) MAC address. In this case is necessary to power-off (desktop
>> case) or unplug the battery (notebook case).
> 
> I see no updated patch in this thread to test -- am I missing something?
Francois has fix for this problem (zeroed MAC address) in his repository:
http://git.kernel.org/?p=linux/kernel/git/romieu/netdev-2.6.git;a=commitdiff;h=9b1abbccf53ef1a1213b159d56257b535c599f07

snippet:
...
-       /* Write MAC address */
-       rtl_rar_set(tp, mac);
+       if (is_valid_ether_addr(mac))
+               rtl_rar_set(tp, mac);
...


When MAC only zeros then it is not assigned. Pulling this commit is better than reverting whole patch.

Ivan

  reply	other threads:[~2008-11-04 18:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 20:25 r8169 MAC addresses broken Simon Arlott
2008-10-25 21:49 ` Jiri Slaby
2008-10-25 22:34   ` Francois Romieu
2008-10-25 23:55     ` Alistair John Strachan
2008-10-26 10:38     ` Jiri Slaby
2008-10-26 12:52       ` Krzysztof Halasa
2008-10-26 15:01         ` Francois Romieu
2008-10-27 19:50         ` Simon Arlott
2008-10-28  9:12           ` Ivan Vecera
2008-10-26 20:42       ` Krzysztof Halasa
2008-10-26 17:24     ` Jiri Slaby
2008-10-26 17:34       ` Arjan van de Ven
2008-10-26 17:46       ` Francois Romieu
2008-10-28 10:09         ` Jiri Slaby
2008-10-28 13:45           ` Krzysztof Halasa
2008-10-28 13:51             ` Jiri Slaby
2008-10-28 20:37               ` Krzysztof Halasa
2008-11-03  9:04               ` Ivan Vecera
2008-11-03 14:50                 ` Jiri Slaby
2008-11-04 18:49                   ` Ivan Vecera [this message]
2008-11-04 21:10                     ` Jiri Slaby
2008-11-05  9:51                       ` Ivan Vecera

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=49109946.7020702@redhat.com \
    --to=ivecera@redhat.com \
    --cc=arjan@infradead.org \
    --cc=edward_hsu@realtek.com.tw \
    --cc=jirislaby@gmail.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=simon@fire.lp0.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.