From: Glen Gray <glen@lincor.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: Multicast issues with RTL8110SC in r8169.c
Date: Fri, 27 Jul 2007 09:13:29 +0100 [thread overview]
Message-ID: <46A9A929.7020605@lincor.com> (raw)
In-Reply-To: <20070726213020.GB14306@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Glen Gray <glen@lincor.com> :
>> Hey Francois,
>> I've CC'd the netdev list as requested
>
> Your PR is not lost (nor are the pending ones btw...). I'm simply trying
> to find a real explanation for
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242572
>
Ah, apologies. When I couldn't see my follow up posts hitting the list,
I figured I'd sign up and post it again.
The linked bug entry indicates issues with the driver initializing
certain cards etc. As previously stated, my issue was mainly in
multicast. I was able to get the machine up and on the network without
issue in the 2.6.21 kernel from F7. Though there's obviously issues with
the newer Realtek cards and the post 2.6.20 kernels.
FYI, The Realtek driver release 1.06 (r1000.ko), although not officially
supporting the 2.6 kernel (the Makefile just needed modification) works
extremely well for us here.
If I can help test experimental patchs or anything, please don't
hesitate to let me know.
--
Glen Gray <glen@lincor.com> Digital Depot, Thomas Street
Senior Software Engineer Dublin 8, Ireland
Lincor Solutions Ltd. Ph: +353 (0) 1 4893682
prev parent reply other threads:[~2007-07-27 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F5A04EB7-0726-4CF5-A4B8-F32F00D9BC52@lincor.com>
[not found] ` <20070718221107.GE9755@electric-eye.fr.zoreil.com>
2007-07-19 17:49 ` Status of RTL8110SC in vanilla r8169.c Glen Gray
2007-07-26 7:33 ` Multicast issues with RTL8110SC in r8169.c Glen Gray
2007-07-26 21:30 ` Francois Romieu
2007-07-27 8:13 ` Glen Gray [this message]
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=46A9A929.7020605@lincor.com \
--to=glen@lincor.com \
--cc=netdev@vger.kernel.org \
--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).