Hi Francois,
Francois Romieu wrote:
Despite the fact that the newer 8168 has been reported to only work with an
extra alignment (gross hack: s/NET_IP_ALIGN/8/), the serie seems otherwise
fine.
I'll submit an updated serie to correctly support the 8168.
Any word on the updated 8168 patch?
Francois Romieu [EMAIL PROTECTED] :
The patch below agaisnt 2.6.17-rc6 includes the following changes:
commit 3072cc0aba3ac0c944e196a63c4154ca5746ec0b
r8169: sync with vendor's driver
- add several PCI ID for the PCI-E adapters ;
- new identification strings ;
- the
Hi,
sorry for the delayed response...
On 13/06/06 00:29, Francois Romieu wrote:
wget goes faster, right ? Do you have some vmstat 1 output at hand
for it ?
It does indeed go faster, and it seems a little bit more reliable, but
with big enough transfers it locks up too. See commandline-2.txt
On 12/06/06 01:30, Francois Romieu wrote:
The patch below agaisnt 2.6.17-rc6 includes the following changes:
Just FYI:
I just tried this patch set, but it doesn't do anything for the freeze
at high speed I mentioned on 2006-06-09. It still locks up. (As an
additional data point: I installed
Mourad De Clerck [EMAIL PROTECTED] :
[...]
I just tried this patch set, but it doesn't do anything for the freeze
at high speed I mentioned on 2006-06-09. It still locks up. (As an
additional data point: I installed win2k on this machine, and it seems
to have no problems transferring at high
Mourad De Clerck [EMAIL PROTECTED] :
[...]
I do notice a pattern with more and less complicated/cpu intensive
traffic: using http (wget) I manage to finish doing the transfer of the
same reasonably big file. With scp I only manage to get to 90% of that
file before it freezes - I should still
The patch below agaisnt 2.6.17-rc6 includes the following changes:
commit 3072cc0aba3ac0c944e196a63c4154ca5746ec0b
r8169: sync with vendor's driver
- add several PCI ID for the PCI-E adapters ;
- new identification strings ;
- the RTL_GIGA_MAC_VER_ defines have been renamed
Jeff Garzik [EMAIL PROTECTED] :
Francois Romieu wrote:
Jeff Garzik [EMAIL PROTECTED] :
Randy.Dunlap wrote:
Conversely, any reason to use the RealTek r1000 driver?
FWIW, RealTek emailed me about merging r1000. I suggested that, if the
Which one ?
r1000_n.c where #define RELEASE_DATE
Francois Romieu [EMAIL PROTECTED] :
[...]
- the != ... ... != test above seems inverted.
Answering to myself: yes, it is. The 8100 and 8101 are PCI Express
fast ethernet only (but they should do 802.1q, go figure).
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe netdev in
Jeff Garzik [EMAIL PROTECTED] :
Randy.Dunlap wrote:
Conversely, any reason to use the RealTek r1000 driver?
FWIW, RealTek emailed me about merging r1000. I suggested that, if the
Which one ?
r1000_n.c where #define RELEASE_DATE 2006/02/23
--
Ueimor
-
To unsubscribe from this list: send
Francois Romieu wrote:
Jeff Garzik [EMAIL PROTECTED] :
Randy.Dunlap wrote:
Conversely, any reason to use the RealTek r1000 driver?
FWIW, RealTek emailed me about merging r1000. I suggested that, if the
Which one ?
r1000_n.c where #define RELEASE_DATE 2006/02/23
They didn't say. Just
On Thu, 1 Jun 2006 21:02:00 +0100 (BST) Daniel Drake wrote:
I've produced this patch which should allow the r8169 driver to work with the
new Realtek 8168 chips. These are found in PCI-Express form and onboard some
newer motherboards.
Does anyone own this hardware? I'm looking for someone
Randy.Dunlap [EMAIL PROTECTED] :
[...]
static struct pci_device_id r1000_pci_tbl[] __devinitdata = {
{ 0x10ec, 0x8169, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
{ 0x10ec, 0x8167, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
{ 0x10ec, 0x8168, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
{ 0x10ec,
Randy.Dunlap wrote:
Conversely, any reason to use the RealTek r1000 driver?
FWIW, RealTek emailed me about merging r1000. I suggested that, if the
register sets were similar, that r8169 should be updated instead, to
preserve compatibility with existing users (and not lose existing work).
On Thu, 08 Jun 2006 22:40:05 -0400 Jeff Garzik wrote:
Randy.Dunlap wrote:
Conversely, any reason to use the RealTek r1000 driver?
FWIW, RealTek emailed me about merging r1000. I suggested that, if the
register sets were similar, that r8169 should be updated instead, to
preserve
Daniel Drake [EMAIL PROTECTED] :
[...]
@@ -1442,20 +1444,24 @@ rtl8169_init_board(struct pci_dev *pdev,
}
}
- /* make sure PCI base addr 1 is MMIO */
- if (!(pci_resource_flags(pdev, 1) IORESOURCE_MEM)) {
- if (netif_msg_probe(tp)) {
-
On Fri, Jun 02, 2006 at 12:24:37AM +0200, Francois Romieu wrote:
I'd rather use pci_device_id-driver_data but it's an option.
I would prefer this, too.
Jeff
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo
17 matches
Mail list logo
