From: Konstantin Kalin <konstantin.kalin@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: NVIDIA Ethernet & invalid MAC
Date: Tue, 16 Oct 2007 20:35:14 +0400 [thread overview]
Message-ID: <4714E842.8020105@gmail.com> (raw)
In-Reply-To: <4714E02D.7040804@garzik.org>
Hello,
I'm sorry, but I think that Alan proposed in the first email is more
than a hack. It would solve the issue for different versions and the
check is trivial. Or am I mistaken?
Thank you,
Kostya.
Jeff Garzik wrote:
> Alan Cox wrote:
>>> See the below for another report of this:
>>>
>>> http://marc.info/?t=119215716900001&r=1&w=2
>>>
>>> And apparently some motherboard vendors have their own allocations
>>> for ethernet
>>> addresses?
>>
>> We can teach it two ranges. I doubt anyone will be unlucky enough to
>> have
>> the one which could be either Nvidia or Gigabyte and have it matter.
>>
>> The "go complain to the BIOS vendor" comment from Nvidia to me isn't an
>> answer. Maybe Nvidia can complain to BIOS vendors but end user
>> complaints
>> of that form rarely have any effect.
>
> That wasn't the point of the response at all. The datum is that set
> of users where DEV_HAS_CORRECT_MACADDR is accurately set or clear is
> vast majority of cases.
>
> For the rest, we'll want to look at adjusting DEV_HAS_CORRECT_MACADDR
> based on DMI strings or a hueristic like you suggested.
>
> Jeff
>
>
>
next prev parent reply other threads:[~2007-10-16 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 14:10 NVIDIA Ethernet & invalid MAC Konstantin Kalin
2007-10-16 14:43 ` Alan Cox
2007-10-16 15:16 ` Chuck Ebbert
2007-10-16 15:43 ` Alan Cox
2007-10-16 16:00 ` Jeff Garzik
2007-10-16 16:20 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-16 16:35 ` Konstantin Kalin [this message]
2007-10-16 16:41 ` Jeff Garzik
2007-10-16 16:52 ` Konstantin Kalin
2007-10-17 13:08 ` Konstantin Kalin
2007-10-16 16:00 ` Chris Snook
2007-10-16 16:07 ` Jeff Garzik
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=4714E842.8020105@gmail.com \
--to=konstantin.kalin@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@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 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.