netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: TommyDrum <mycooc@yahoo.it>
To: Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: r8169 native module problems on 2.6.11 [SOLVED]
Date: Mon, 11 Apr 2005 02:26:49 +0200	[thread overview]
Message-ID: <4259C449.7000306@yahoo.it> (raw)
In-Reply-To: <20050410170251.GA9537@electric-eye.fr.zoreil.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

O/H Francois Romieu έγραψε:

| Ok, new pci id, no wonder it does not work. Can you give the attached
patch
| a quick but carefull test on your vanilla kernel ?

Wasn't too quick, sorry, had to supper (very long, I admit it!). It's
modprobed very quick (much faster than the USR provided module) and
works pretty good up 'til now; dmesg is clean, lspci also, and cat
/proc/interrupts doesn't show any conflicts. ifconfig also seems to be
in line, and the interface is up and running smoothly.
IMO all is quiet on this front ;)

I forwarded last message to netdev, also do it with this one.

Keep up the good work Francois, and thanks really a lot!

A presto!
Tommy

P.S. Any other info needed, I'll be glad to provide.


| ------------------------------------------------------------------------
|
| --- a/drivers/net/r8169.c	2005-04-10 18:45:05.200274476 +0200
| +++ b/drivers/net/r8169.c	2005-04-10 18:52:41.197933777 +0200
| @@ -176,6 +176,7 @@ const static struct {
|  static struct pci_device_id rtl8169_pci_tbl[] = {
|  	{0x10ec, 0x8169, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
|  	{0x1186, 0x4300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
| +	{0x16ec, 0x0116, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
|  	{0,},
|  };
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCWcRCgpUvhTIUBAERArnEAJ9A8/LbF2Mra0pVJS9Lcp+hg0pZ4wCeKAsu
N4L1zAsNmRg15EQOuqcPmEE=
=S2E/
-----END PGP SIGNATURE-----

           reply	other threads:[~2005-04-11  0:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20050410170251.GA9537@electric-eye.fr.zoreil.com>]

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=4259C449.7000306@yahoo.it \
    --to=mycooc@yahoo.it \
    --cc=romieu@fr.zoreil.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).