Hello,
We are developing a custom embedded computer based on a Q7 module with an Intel
Atom E640 and two additional Intel i210 NIC's (with unprogrammed NVM).
The Q7 runs Debian Linux 7.3, Kernel 3.2.0-4-686-pae and igb driver version
5.0.6 (I was not able to build v5.1.2, btw.).
How can I
I just found this thread which explains some of my questions:
http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg08777.html
But what if I don't have a person from Intel who is supporting me? Where can I
get one? ;-)
Regards,
Alex
Where did you get the parts? That's who you should contact.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Lauper Alexander [mailto:alexander.lau...@comlab.ch]
Sent: Thursday,
Is the Debian kernel the same as the upstream kernel? We don't support Debian
directly, be we can look into why this is not compiling on the upstream kernel.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
Where did you buy the parts (the i210 parts) from? They are only sold from
suppliers that have the Intel contacts for supplying the tools and images
needed for HW development.
Cheers,
John
-Original Message-
From: Lauper Alexander [mailto:alexander.lau...@comlab.ch]
Sent:
Hi Alexander,
You need to get the tools and the NVM image from your field person from Intel
that sold you the i210 parts. You should be under NDA and your field person
will be able to get you the tools and the initial NVM image for you to put into
the NVM of the parts.
Let me know if your
Maybe but does it compile correctly if you don't specify -pae? I don't think
we test for that config option anymore and I'm pretty sure a generic 3.2 kernel
will compile the driver correctly it's probably something like this.
Cheers,
John
-Original Message-
From: Lauper Alexander
This reverts commit e8de1481fd71 (resource: allow MMIO exclusivity for
device drivers), removing these exported interfaces:
pci_request_region_exclusive()
pci_request_regions_exclusive()
pci_request_selected_regions_exclusive()
There's nothing wrong with the MMIO exclusivity code, but it
This is a rework of part of Stephen's patch [1].
This removes the MMIO exclusivity support that was added as part of an
e1000e bug hunt.
The e1000e driver still uses pci_request_selected_regions_exclusive(), but
there are no callers of pci_request_region_exclusive() and
On Thu, 2014-01-30 at 10:51 +, Michele Baldessari wrote:
From:
Michele Baldessari
mich...@acksyn.org
Reply-to:
Michele Baldessari
mich...@acksyn.org
To:
net...@vger.kernel.org
From: Brown, Aaron F aaron.f.br...@intel.com
Date: Fri, 31 Jan 2014 00:40:16 +
From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
On Behalf Of David Miller
Sent: Thursday, January 30, 2014 4:28 PM
To: mich...@acksyn.org
Cc: net...@vger.kernel.org;
I think I've figured out the problem. Unfortunately, I was remotely testing it
tonight and my system is no longer on the network. I'll have to get back to you
tomorrow.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
12 matches
Mail list logo
