From: "Jason R. Martin" <nsxfreddy@gmail.com>
To: iSteve <isteve@rulez.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possibly wrong contact for e100 driver
Date: Sun, 28 Aug 2005 12:43:54 -0700 [thread overview]
Message-ID: <c295378405082812434429ccd1@mail.gmail.com> (raw)
In-Reply-To: <43120783.7040406@rulez.cz>
On 8/28/05, iSteve <isteve@rulez.cz> wrote:
> Greetings,
> in past few days, I've been trying to obtain certian information about
> behavior of e100 NIC driver with my minipci card. My first hit was the
> contact information mentioned in the header of e100.c, that is, "Linux
> NICS <linux.nics@intel.com>".
>
> I've sent in my mail, praying for reply. The first reply was automated
> response, which suggested me eg. Win 3.11 install notes. After asking
> tech support reply, the email from tech support, which arrived day
> later, only told me that Intel doesn't distribute MiniPCI cards
> directly, instead sells them to companies who distribute them. He also
> suggested me to "for the best possible technical support and the latest
> drivers for your MPCI hardware, please contact the manufacturer of your
> PC".
>
> Since I sent a rather technical question, and got such reply (and no
> reply so far, when I asked for better support - contact on someone
> closer to the actual driver, be it from Intel or not, politely), I
> wonder whether the contact information is still up to date? If no, what
> is the new contact information?
Try asking on netdev@vger.kernel.org. Or email the guys listed in
MAINTAINERS for e100. Or check out the e1000 sourceforge project
(which covers e100 and ixgb as well).
Jason
next prev parent reply other threads:[~2005-08-28 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 18:50 Possibly wrong contact for e100 driver iSteve
2005-08-28 19:43 ` Jason R. Martin [this message]
2005-08-28 20:12 ` Martin Josefsson
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=c295378405082812434429ccd1@mail.gmail.com \
--to=nsxfreddy@gmail.com \
--cc=isteve@rulez.cz \
--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.