From: Darren Hart <dvhart@linux.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, arjan@linux.intel.com,
alan@linux.intel.com, tomoya.rohm@gmail.com,
jeffrey.t.kirsher@intel.com, paul.gortmaker@windriver.com,
jdmason@kudzu.us, netdev@vger.kernel.org
Subject: Re: [PATCH] pch_gbe: Use a randomly generated MAC instead of failing probe
Date: Sat, 14 Jan 2012 14:36:07 -0800 [thread overview]
Message-ID: <4F120357.3020808@linux.intel.com> (raw)
In-Reply-To: <20120114214658.4ddfec30@pyramind.ukuu.org.uk>
On 01/14/2012 01:46 PM, Alan Cox wrote:
>> I fear that people are just going to add this random MAC stuff way too
>> easily, it's a spreading disease.
>>
>> Ship functional hardware instead.
>
> See "choir, preaching to the".
>
> The stuff is out there and it's not Darren's fault !
>
> Alan
So perhaps I should provide some more context into why I'm sending these
patches. The following hardware is currently available and the existing
Linux support is confined to a Timesys Fedora-Based pre-installed image
which requires user intervention to write a MAC using an old, not
upstreamed, modified ioh_gbe_mac driver.
The board documentation is available here:
http://www.inforcecomputing.com/SYS940X_ECX.html
In particular, see:
http://www.inforcecomputing.com/proddls/SYS940X-01_UserGuide_001329.pdf
and:
http://www.inforcecomputing.com/proddls/BLDK2_Kern_2.6.29-10_and_2.6.29-12_for_SYS940X-1_1304.pdf
I felt this patch made this hardware more accessible by allowing it to
work with current kernels without ugly userspace hacks. It is also
following precedent set by existing drivers.
So while I completely agree with the sentiment "Ship functional
hardware", this wasn't a product I was involved with, I'm just trying to
make a bad situation better. As Alan alludes to above, I do actually
spend a good deal of time trying to improve hardware to avoid this kind
of thing (it's an amazingly difficult task).
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-01-14 22:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 6:44 [PATCH] pch_gbe: Use a randomly generated MAC instead of failing probe Darren Hart
2012-01-14 8:14 ` David Miller
2012-01-14 15:54 ` Darren Hart
2012-01-14 19:56 ` David Miller
2012-01-14 20:29 ` Joe Perches
2012-01-14 21:46 ` Alan Cox
2012-01-14 22:36 ` Darren Hart [this message]
2012-01-16 7:38 ` Tomoya MORINAGA
2012-01-16 12:31 ` Alan Cox
2012-01-16 15:42 ` Darren Hart
2012-01-16 16:07 ` Arjan van de Ven
2012-01-16 16:20 ` David Laight
2012-01-16 16:35 ` Arjan van de Ven
2012-01-16 16:44 ` Mark Brown
2012-01-16 17:02 ` Alan Cox
2012-01-16 21:06 ` Rick Jones
2012-01-16 15:38 ` Darren Hart
2012-01-14 8:15 ` David Miller
2012-01-14 8:18 ` Cong Wang
2012-01-14 15:45 ` Darren Hart
2012-01-16 15:22 ` Nick Bowler
2012-01-16 23:04 ` David Miller
2012-01-16 23:07 ` Darren Hart
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=4F120357.3020808@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=jdmason@kudzu.us \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tomoya.rohm@gmail.com \
/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).