Boring week-end in sight ?
The new serie of r8169 changes is available at:
http://www.fr.zoreil.com/people/francois/misc/20070316-2.6.21-rc4-r8169-test.patch
or:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21-rc4/r8169-20070316
or (rebase happy branch):
Boring week-end in sight ?
The new serie of r8169 changes is available at:
http://www.fr.zoreil.com/people/francois/misc/20070316-2.6.21-rc4-r8169-test.patch
or:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21-rc4/r8169-20070316
or (rebase happy branch):
la.kernel.org if the issue does not go away.
8<-
8139too: netconsole breakage when link changes
rtl8139_interrupt is not supposed to be reentrant but its link
management part can emit printk.
Signed-off-by: Francois Romieu
-
8139too: netconsole breakage when link changes
rtl8139_interrupt is not supposed to be reentrant but its link
management part can emit printk.
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
diff --git a/drivers/net/8139too.c b
Eric Lacombe <[EMAIL PROTECTED]> :
[...]
> Also, if you have some new ideas about the problem or what I could try to
> trigger it more frequently (I already wake up the NAS as more as I can, but
> maybe I could write a script to do that), I would be thankful.
You can add more DEBUG options for
Eric Lacombe [EMAIL PROTECTED] :
[...]
Also, if you have some new ideas about the problem or what I could try to
trigger it more frequently (I already wake up the NAS as more as I can, but
maybe I could write a script to do that), I would be thankful.
You can add more DEBUG options for
Boris B. Zhmurov <[EMAIL PROTECTED]> :
[...]
> to your 2.6.11. Francois, please, correct me, if I'm wrong.
It will regularly DMA into incorrectly aligned addresses. :o/
Surprizing as it may sound, the symptoms range from unnoticeable
to unusable (both inclusive).
--
Ueimor
-
To unsubscribe
Please Cc: the maintainer from the MAINTAINERS file.
Petri T. Koistinen <[EMAIL PROTECTED]> :
[...]
> I just brought two D-Link DGE-528T (uses r8159 driver) network adapters
> to have nice 1 Gbps home network between two computers.
- which kernel ?
- dmesg please ?
[...]
> and when I use this
Boris B. Zhmurov [EMAIL PROTECTED] :
[...]
to your 2.6.11. Francois, please, correct me, if I'm wrong.
It will regularly DMA into incorrectly aligned addresses. :o/
Surprizing as it may sound, the symptoms range from unnoticeable
to unusable (both inclusive).
--
Ueimor
-
To unsubscribe from
Please Cc: the maintainer from the MAINTAINERS file.
Petri T. Koistinen [EMAIL PROTECTED] :
[...]
I just brought two D-Link DGE-528T (uses r8159 driver) network adapters
to have nice 1 Gbps home network between two computers.
- which kernel ?
- dmesg please ?
[...]
and when I use this cable
Tom Burns <[EMAIL PROTECTED]> :
[...]
> 2.6.15-1 - it was trivial changes aside from 2.6.20.1 which required
> changes to the task scheduling code, but I'm pretty certain I didn't
> break anything.
I do not have the answar that you expect but some information could help:
- which motherboard is it
Tom Burns [EMAIL PROTECTED] :
[...]
2.6.15-1 - it was trivial changes aside from 2.6.20.1 which required
changes to the task scheduling code, but I'm pretty certain I didn't
break anything.
I do not have the answar that you expect but some information could help:
- which motherboard is it ?
-
Francois Romieu <[EMAIL PROTECTED]> :
> Michal Piotrowski <[EMAIL PROTECTED]> :
> [...]
>
> Did you enable RTL8139_DEBUG ?
>
> If so you can try the patch below.
It's buggy there too but you are not experiencing this one.
1 - netpoll() calls the poll()
Michal Piotrowski <[EMAIL PROTECTED]> :
[...]
Did you enable RTL8139_DEBUG ?
If so you can try the patch below.
diff --git a/drivers/net/8139too.c b/drivers/net/8139too.c
index 35ad5cf..da61368 100644
--- a/drivers/net/8139too.c
+++ b/drivers/net/8139too.c
@@ -634,7 +634,6 @@ static int
Michal Piotrowski [EMAIL PROTECTED] :
[...]
Did you enable RTL8139_DEBUG ?
If so you can try the patch below.
diff --git a/drivers/net/8139too.c b/drivers/net/8139too.c
index 35ad5cf..da61368 100644
--- a/drivers/net/8139too.c
+++ b/drivers/net/8139too.c
@@ -634,7 +634,6 @@ static int
Francois Romieu [EMAIL PROTECTED] :
Michal Piotrowski [EMAIL PROTECTED] :
[...]
Did you enable RTL8139_DEBUG ?
If so you can try the patch below.
It's buggy there too but you are not experiencing this one.
1 - netpoll() calls the poll() handler of the device through netpoll_poll()
2
Eric Lacombe <[EMAIL PROTECTED]> :
[...]
> That problem also remind me that when I compiled this driver without
> the "CONFIG_NET_ETHERNET" (in the section "Ethernet (10 or 100Mbit)"), I have
> really poor performance with the net device. Maybe it is related, or not ;)
>
> If it gives you more
Eric Lacombe [EMAIL PROTECTED] :
[...]
That problem also remind me that when I compiled this driver without
the CONFIG_NET_ETHERNET (in the section Ethernet (10 or 100Mbit)), I have
really poor performance with the net device. Maybe it is related, or not ;)
If it gives you more ideas ?
? <[EMAIL PROTECTED]> :
> Dear Francois:
>
> I think I didn't make it clear about the programming manuals for PCI-E ICs.
>
> Due to several legal issues, Realtek won't put the programming guide on
> its website. However, Realtek does offer the programming guide if the
> customers need
? [EMAIL PROTECTED] :
Dear Francois:
I think I didn't make it clear about the programming manuals for PCI-E ICs.
Due to several legal issues, Realtek won't put the programming guide on
its website. However, Realtek does offer the programming guide if the
customers need it. If
[EMAIL PROTECTED] :
[...]
> ANS_2:
> So, do you think that it is a good idea to keep other vendos's PID and
> DID in the part?
Yes.
[...]
> ANS_2:
>
> Sure! You are right. RTL8110SC, RTL8111B and RTL8101E have modest
> differences, now. However, RTL8101E is a PCI-E fast ethernet controller.
> I
[EMAIL PROTECTED] :
[...]
ANS_2:
So, do you think that it is a good idea to keep other vendos's PID and
DID in the part?
Yes.
[...]
ANS_2:
Sure! You are right. RTL8110SC, RTL8111B and RTL8101E have modest
differences, now. However, RTL8101E is a PCI-E fast ethernet controller.
I don't
? <[EMAIL PROTECTED]> :
[...]
> >>static struct pci_device_id rtl8169_pci_tbl[] = {
> >>- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8129), 0, 0, RTL_CFG_0 },
> >>- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8136), 0, 0, RTL_CFG_2 },
> >>- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8167), 0, 0, RTL_CFG_0
? [EMAIL PROTECTED] :
[...]
static struct pci_device_id rtl8169_pci_tbl[] = {
- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8129), 0, 0, RTL_CFG_0 },
- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8136), 0, 0, RTL_CFG_2 },
- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8167), 0, 0, RTL_CFG_0 },
- {
e and Interframe Gap Time */
> - RTL_W32(TxConfig, (TX_DMA_BURST << TxDMAShift) |
> - (InterFrameGap << TxInterFrameGapShift));
> + RTL_W16(CPlusCmd, RTL_R16(CPlusCmd) | PCIMulRW);
> + pci_write_config_byte(pdev, PCI_CACHE_LINE_SIZE, 0x08);
>
> - tp->cp_cmd |= RTL_R16(CPl
in rtl8169_hw_start
with the code that you sent. I have kept a few parts inherited from
the code in v1.05 of the r1000 driver (which was reported to work
rather well despite some strange code).
Merge of r8169 6.001.00.
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
---
drivers/net/r8169.c | 112
Nicolas Mailhot <[EMAIL PROTECTED]> :
[...]
> incomplete NDAed documentation. If (as this offer implies) there are good
> driver authors waiting to do more drivering, why aren't those a priority?
So far nobody cared enough to maintain a list of said out-of-tree drivers.
--
Ueimor
-
To
Nicolas Mailhot [EMAIL PROTECTED] :
[...]
incomplete NDAed documentation. If (as this offer implies) there are good
driver authors waiting to do more drivering, why aren't those a priority?
So far nobody cared enough to maintain a list of said out-of-tree drivers.
--
Ueimor
-
To unsubscribe
Untested, straight from the "release early" dept. You have been warned.
Realtek's driver restricts itself to 0x8169 and 0x8167.
It won't be surprising if it breaks on anything else until
I merge the new 0x8168 and 0x8136 bits.
Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
Untested, straight from the release early dept. You have been warned.
Realtek's driver restricts itself to 0x8169 and 0x8167.
It won't be surprising if it breaks on anything else until
I merge the new 0x8168 and 0x8136 bits.
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
---
drivers/net/r8169
> diff --git a/drivers/net/atl1/atl1_hw.h b/drivers/net/atl1/atl1_hw.h
> new file mode 100644
> index 000..0450b77
> --- /dev/null
> +++ b/drivers/net/atl1/atl1_hw.h
[...]
> +/* MII definition */
> +/* PHY Common Register */
> +#define MII_BMCR 0x00
>
diff --git a/drivers/net/atl1/atl1_hw.h b/drivers/net/atl1/atl1_hw.h
new file mode 100644
index 000..0450b77
--- /dev/null
+++ b/drivers/net/atl1/atl1_hw.h
[...]
+/* MII definition */
+/* PHY Common Register */
+#define MII_BMCR 0x00
+#define
Bernhard Walle <[EMAIL PROTECTED]> :
> --- linux-2.6.20-rc4.orig/drivers/net/r8169.c 2007-01-07 06:45:51.0
> +0100
> +++ linux-2.6.20-rc4/drivers/net/r8169.c 2007-01-17 11:39:13.792309228
> +0100
[...]
> @@ -2227,7 +2227,7 @@ static int rtl8169_xmit_frags(struct rtl
> {
>
Bernhard Walle [EMAIL PROTECTED] :
--- linux-2.6.20-rc4.orig/drivers/net/r8169.c 2007-01-07 06:45:51.0
+0100
+++ linux-2.6.20-rc4/drivers/net/r8169.c 2007-01-17 11:39:13.792309228
+0100
[...]
@@ -2227,7 +2227,7 @@ static int rtl8169_xmit_frags(struct rtl
{
struct
Jay Cliburn <[EMAIL PROTECTED]> :
[...]
> I welcome any comments on the rationality of this approach.
An URL for the current version of the patch would be welcome too :o)
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Jay Cliburn [EMAIL PROTECTED] :
[...]
I welcome any comments on the rationality of this approach.
An URL for the current version of the patch would be welcome too :o)
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
Anders Karlsson <[EMAIL PROTECTED]> :
[...]
> PCI ID's in there, so this driver *should* work. In the past, it *has*
> worked, but that was on a older kernel (2.6.8 or thereabouts).
No datapoint beyond 2.6.12 ? It would make thinks easier (for you :o} ).
> If there are patches or tweaks to the
Anders Karlsson [EMAIL PROTECTED] :
[...]
PCI ID's in there, so this driver *should* work. In the past, it *has*
worked, but that was on a older kernel (2.6.8 or thereabouts).
No datapoint beyond 2.6.12 ? It would make thinks easier (for you :o} ).
If there are patches or tweaks to the
Dmitriy Monakhov <[EMAIL PROTECTED]> :
> Return value of 'pci_enable_device' was ignored in b44_resume().
> We can't ingore it because it can fail.
- Please Cc: netdev@vger.kernel.org, [EMAIL PROTECTED] and the maintainer
of the driver (Gary Zambrano <[EMAIL PROTECTED]> as per MAINTAINERS
Anders Karlsson <[EMAIL PROTECTED]> :
[...]
No message from the sundance driver in dmesg ?
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
Anders Karlsson [EMAIL PROTECTED] :
[...]
No message from the sundance driver in dmesg ?
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
Dmitriy Monakhov [EMAIL PROTECTED] :
Return value of 'pci_enable_device' was ignored in b44_resume().
We can't ingore it because it can fail.
- Please Cc: netdev@vger.kernel.org, [EMAIL PROTECTED] and the maintainer
of the driver (Gary Zambrano [EMAIL PROTECTED] as per MAINTAINERS
file and
Jeff Garzik <[EMAIL PROTECTED]> :
> I refreshed my git intro/cookbook for kernel hackers, at
> http://linux.yyz.us/git-howto.html
>
> This describes most of the commands I use in day-to-day kernel hacking.
> Let me know if there are glaring errors or missing key commands.
o 'git whatchanged
Stephen Hemminger <[EMAIL PROTECTED]> :
[...]
> We need to allow ethtool setting to be done before device has been brought
> up and started autonegotiation. The current MII library doesn't really support
> it.
I completely agree.
--
Ueimor
-
To unsubscribe from this list: send the line
Stephen Hemminger [EMAIL PROTECTED] :
[...]
We need to allow ethtool setting to be done before device has been brought
up and started autonegotiation. The current MII library doesn't really support
it.
I completely agree.
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe
Jeff Garzik [EMAIL PROTECTED] :
I refreshed my git intro/cookbook for kernel hackers, at
http://linux.yyz.us/git-howto.html
This describes most of the commands I use in day-to-day kernel hacking.
Let me know if there are glaring errors or missing key commands.
o 'git whatchanged shnortz'
Stephen Hemminger <[EMAIL PROTECTED]> :
[...]
>IMHO:
> When device is down, it should:
>a) use as few resources as possible:
> - not grab memory for buffers
> - not assign IRQ unless it could get one
> - turn off all power consumption
Stephen Hemminger [EMAIL PROTECTED] :
[...]
IMHO:
When device is down, it should:
a) use as few resources as possible:
- not grab memory for buffers
- not assign IRQ unless it could get one
- turn off all power consumption possible
Lennert Buytenhek <[EMAIL PROTECTED]> :
[...]
> Francois, if you submit the r8169.c half of that patch, I'll do my half.
Ok, I'll do it now.
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Lennert Buytenhek [EMAIL PROTECTED] :
[...]
Francois, if you submit the r8169.c half of that patch, I'll do my half.
Ok, I'll do it now.
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Lennert Buytenhek <[EMAIL PROTECTED]> :
[...]
> Sounds good. How about something like the patch below plus the
> corresponding r8169 diff?
Go wild.
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Lennert Buytenhek <[EMAIL PROTECTED]> :
> On Sat, Dec 16, 2006 at 01:54:39AM +0100, Francois Romieu wrote:
[...]
> I'm thinking that the entire option is just wrong. It sucks for
> distributors to have to make the choice between having it always on
> and having it always off.
Lennert Buytenhek [EMAIL PROTECTED] :
On Sat, Dec 16, 2006 at 01:54:39AM +0100, Francois Romieu wrote:
[...]
I'm thinking that the entire option is just wrong. It sucks for
distributors to have to make the choice between having it always on
and having it always off. It sucks for end users
Lennert Buytenhek [EMAIL PROTECTED] :
[...]
Sounds good. How about something like the patch below plus the
corresponding r8169 diff?
Go wild.
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Lennert Buytenhek <[EMAIL PROTECTED]> :
[...]
> No, that wouldn't make sense, that's like making a workaround depend on
> arch == i386.
>
> I'm thinking that we should somehow enable this option on the n2100
> built-in r8169 ports by default only. Since the n2100 also has a mini-PCI
> slot, and
Lennert Buytenhek <[EMAIL PROTECTED]> :
[...]
> Is there a way we can have this done by default on the n2100? I guess
> that since it's a PCI device, there isn't much hope for that..?
Do you mean an automagically tuned default value based on CONFIG_ARM ?
--
Ueimor
-
To unsubscribe from this
Lennert Buytenhek [EMAIL PROTECTED] :
[...]
Is there a way we can have this done by default on the n2100? I guess
that since it's a PCI device, there isn't much hope for that..?
Do you mean an automagically tuned default value based on CONFIG_ARM ?
--
Ueimor
-
To unsubscribe from this list:
Lennert Buytenhek [EMAIL PROTECTED] :
[...]
No, that wouldn't make sense, that's like making a workaround depend on
arch == i386.
I'm thinking that we should somehow enable this option on the n2100
built-in r8169 ports by default only. Since the n2100 also has a mini-PCI
slot, and it is in
Jeff Garzik <[EMAIL PROTECTED]> :
> Ingo Molnar wrote:
[...]
> >fix deadlock in the 8139too driver: poll handlers should never forcibly
> >enable local interrupts, because they might be used by netpoll/printk
> >from IRQ context.
>
> ACK
>
> (I'll queue it, if Linus doesn't pick it up; please
Jeff Garzik [EMAIL PROTECTED] :
Ingo Molnar wrote:
[...]
fix deadlock in the 8139too driver: poll handlers should never forcibly
enable local interrupts, because they might be used by netpoll/printk
from IRQ context.
ACK
(I'll queue it, if Linus doesn't pick it up; please CC me in the
Steve Wise <[EMAIL PROTECTED]> :
[...]
> Version 2 changes:
>
> - Make code sparse endian clean
> - Use IDRs for mapping QP and CQ IDs to structure pointers instead of arrays
> - Clean up confusing bitfields
> - Use random32() instead of local random function
> - Use krefs to track endpoint
Steve Wise [EMAIL PROTECTED] :
[...]
Version 2 changes:
- Make code sparse endian clean
- Use IDRs for mapping QP and CQ IDs to structure pointers instead of arrays
- Clean up confusing bitfields
- Use random32() instead of local random function
- Use krefs to track endpoint reference
Mariusz Kozlowski <[EMAIL PROTECTED]> :
[...]
Applied at git://electric-eye.fr.zoreil.com/home/romieu/linux-2.6.git#chelsio
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Mariusz Kozlowski [EMAIL PROTECTED] :
[...]
Applied at git://electric-eye.fr.zoreil.com/home/romieu/linux-2.6.git#chelsio
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Martin Korous <[EMAIL PROTECTED]> :
[...]
> I want report a bug in sky2 driver. Sky2 will shutdown every 5-6 days.
Please Cc: [EMAIL PROTECTED] and netdev@vger.kernel.org as suggested
in the MAINTAINERS file.
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Martin Korous [EMAIL PROTECTED] :
[...]
I want report a bug in sky2 driver. Sky2 will shutdown every 5-6 days.
Please Cc: [EMAIL PROTECTED] and netdev@vger.kernel.org as suggested
in the MAINTAINERS file.
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
Toralf F??rster <[EMAIL PROTECTED]> :
[...]
> WARNING: "hdlc_close" [drivers/net/wan/dscc4.ko] undefined!
> WARNING: "hdlc_open" [drivers/net/wan/dscc4.ko] undefined!
> WARNING: "alloc_hdlcdev" [drivers/net/wan/dscc4.ko] undefined!
> WARNING: "unregister_hdlc_device" [drivers/net/wan/dscc4.ko]
Toralf F??rster [EMAIL PROTECTED] :
[...]
WARNING: hdlc_close [drivers/net/wan/dscc4.ko] undefined!
WARNING: hdlc_open [drivers/net/wan/dscc4.ko] undefined!
WARNING: alloc_hdlcdev [drivers/net/wan/dscc4.ko] undefined!
WARNING: unregister_hdlc_device [drivers/net/wan/dscc4.ko] undefined!
Miroslaw Mieszczak <[EMAIL PROTECTED]> :
> Francois Romieu napisał(a):
>
> >You can silence this message in 2.6.13 by using the 'msglvl'
> >option of the ethtool command.
>
> It would be disabled only this message, or all warning messages from the
> net driver
Miroslaw Mieszczak [EMAIL PROTECTED] :
Francois Romieu napisał(a):
You can silence this message in 2.6.13 by using the 'msglvl'
option of the ethtool command.
It would be disabled only this message, or all warning messages from the
net driver?
One issues 'ethtool msglvl xyz' where xyz
Miroslaw Mieszczak <[EMAIL PROTECTED]> :
[...]
> The main problem with this driver is, that if I do like this, then every
> 10 seconds I receive new message from the network card in kernel log.
> There is following message:
>
> Sep 4 16:31:43 laptop_mirka eth0: PHY reset until link up
> Sep 4
Miroslaw Mieszczak [EMAIL PROTECTED] :
[...]
The main problem with this driver is, that if I do like this, then every
10 seconds I receive new message from the network card in kernel log.
There is following message:
Sep 4 16:31:43 laptop_mirka eth0: PHY reset until link up
Sep 4 16:31:53
[EMAIL PROTECTED] <[EMAIL PROTECTED]> :
> On Tue, 06 Sep 2005 22:42:21 +0200, Francois Romieu said:
>
> > Currently one can do 'ifconfig ethX up', check the link status, then try
> > to DHCP or whatever. Apparently a few drivers do not support tne detection
> >
[EMAIL PROTECTED] <[EMAIL PROTECTED]> :
[...]
Ok, thanks for the hint.
Currently one can do 'ifconfig ethX up', check the link status, then try
to DHCP or whatever. Apparently a few drivers do not support tne detection
of link as presented above. So is it anything like a vendor requirement/a
Miroslaw Mieszczak <[EMAIL PROTECTED]> :
> There is a patch to driver of RLT8169 network card. This match make
> possible detection of the link status even if network interface is down.
> This is usefull for laptop users.
(side note: there is maintainer entry for the r8169 and network related
Miroslaw Mieszczak [EMAIL PROTECTED] :
There is a patch to driver of RLT8169 network card. This match make
possible detection of the link status even if network interface is down.
This is usefull for laptop users.
(side note: there is maintainer entry for the r8169 and network related
patches
[EMAIL PROTECTED] [EMAIL PROTECTED] :
[...]
Ok, thanks for the hint.
Currently one can do 'ifconfig ethX up', check the link status, then try
to DHCP or whatever. Apparently a few drivers do not support tne detection
of link as presented above. So is it anything like a vendor requirement/a
[EMAIL PROTECTED] [EMAIL PROTECTED] :
On Tue, 06 Sep 2005 22:42:21 +0200, Francois Romieu said:
Currently one can do 'ifconfig ethX up', check the link status, then try
to DHCP or whatever. Apparently a few drivers do not support tne detection
of link as presented above. So is it anything
Nick Warne <[EMAIL PROTECTED]> :
[...]
> This one looks _so_ familiar to me personally - exactly the same problems I
> had:
>
> http://marc.theaimsgroup.com/?l=linux-kernel=112458400611745=2
Hmmm... I had not envisioned a lost event but it could turn into
something interesting. Thanks for the
Andrew Morton <[EMAIL PROTECTED]> :
[...]
> [Bugme-new] [Bug 5078] New: r8169: eth0: PHY reset until link up
> http://bugzilla.kernel.org/show_bug.cgi?id=5078
Not a bug. I closed it.
[...]
> [Bugme-new] [Bug 5137] New: r8169 - network dies.
>
Andrew Morton [EMAIL PROTECTED] :
[...]
[Bugme-new] [Bug 5078] New: r8169: eth0: PHY reset until link up
http://bugzilla.kernel.org/show_bug.cgi?id=5078
Not a bug. I closed it.
[...]
[Bugme-new] [Bug 5137] New: r8169 - network dies.
http://bugzilla.kernel.org/show_bug.cgi?id=5137
Nick Warne [EMAIL PROTECTED] :
[...]
This one looks _so_ familiar to me personally - exactly the same problems I
had:
http://marc.theaimsgroup.com/?l=linux-kernelm=112458400611745w=2
Hmmm... I had not envisioned a lost event but it could turn into
something interesting. Thanks for the
Giampaolo Tomassoni <[EMAIL PROTECTED]> :
[...]
> Well, the idea is that more pci devices may appear, as adsl-enabled
> embedded systems will begin to appear in the market.
>
> Also, I believe that adsl will carry much more services then just AAL5 for
> internet connection in the future.
I'd be
Giampaolo Tomassoni <[EMAIL PROTECTED]> :
[...]
> However, I'm still hearing for your comments about the usefulness of an
> ATMSAR layer.
Afaik all but one pci ADSL modems are out of tree drivers and include various
level of proprietary code. If Duncan is not interested in changing its code,
the
Bret Towe <[EMAIL PROTECTED]> :
[...]
> after moving some files on the server to a new location then trying to
> add the files
> to xmms playlist i found the following in dmesg after xmms froze
> wonder how many more items i can find...
The system includes some binary only stuff. Please contact
Bret Towe [EMAIL PROTECTED] :
[...]
after moving some files on the server to a new location then trying to
add the files
to xmms playlist i found the following in dmesg after xmms froze
wonder how many more items i can find...
The system includes some binary only stuff. Please contact your
Giampaolo Tomassoni [EMAIL PROTECTED] :
[...]
However, I'm still hearing for your comments about the usefulness of an
ATMSAR layer.
Afaik all but one pci ADSL modems are out of tree drivers and include various
level of proprietary code. If Duncan is not interested in changing its code,
the
Giampaolo Tomassoni [EMAIL PROTECTED] :
[...]
Well, the idea is that more pci devices may appear, as adsl-enabled
embedded systems will begin to appear in the market.
Also, I believe that adsl will carry much more services then just AAL5 for
internet connection in the future.
I'd be happily
-by: Francois Romieu <[EMAIL PROTECTED]>
diff -puN a/drivers/net/sis190.c~sis190-180 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-180 2005-09-02 23:27:35.912352373 +0200
+++ b/drivers/net/sis190.c 2005-09-02 23:27:35.917351565 +0200
@@ -279,6 +279,11 @@ enum sis190_eeprom_a
link changes reporting does not work when the driver masks its irq event
Signed-off-by: Arnaud Patard <[EMAIL PROTECTED]>
Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
diff -puN a/drivers/net/sis190.c~sis190-170 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-170 2005
the relevant register layout is not documented. SiS's driver does
not provide these features either (at least not for Linux).
Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
diff -puN a/drivers/net/sis190.c~sis190-210 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-210 2005-09-02
Don't ask.
The patch is based on SiS's GPLed driver.
Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
diff -puN a/drivers/net/sis190.c~sis190-200 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-200 2005-09-02 23:27:58.126761637 +0200
+++ b/drivers/net/sis190.c 2005-09-02
mon denominator when everything else failed.
Btw it works better than the current code. :o)
- remove some enums: they do not document anymore.
Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
diff -puN a/drivers/net/sis190.c~sis190-190 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-190
A new patch-kit is available.
o Fix link event reporting (Arnaud Patard).
o Default to 10Mbps when nothing better can be detected (me).
o Experimental sis191 support + small rgmii changes.
Please report anything related to link management you are not satisfied
with. You can report success as
A new patch-kit is available.
o Fix link event reporting (Arnaud Patard).
o Default to 10Mbps when nothing better can be detected (me).
o Experimental sis191 support + small rgmii changes.
Please report anything related to link management you are not satisfied
with. You can report success as
Don't ask.
The patch is based on SiS's GPLed driver.
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
diff -puN a/drivers/net/sis190.c~sis190-200 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-200 2005-09-02 23:27:58.126761637 +0200
+++ b/drivers/net/sis190.c 2005-09-02 23:27
when everything else failed.
Btw it works better than the current code. :o)
- remove some enums: they do not document anymore.
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
diff -puN a/drivers/net/sis190.c~sis190-190 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-190 2005-09-02
the relevant register layout is not documented. SiS's driver does
not provide these features either (at least not for Linux).
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
diff -puN a/drivers/net/sis190.c~sis190-210 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-210 2005-09-02 23:28
-by: Francois Romieu [EMAIL PROTECTED]
diff -puN a/drivers/net/sis190.c~sis190-180 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-180 2005-09-02 23:27:35.912352373 +0200
+++ b/drivers/net/sis190.c 2005-09-02 23:27:35.917351565 +0200
@@ -279,6 +279,11 @@ enum sis190_eeprom_address
link changes reporting does not work when the driver masks its irq event
Signed-off-by: Arnaud Patard [EMAIL PROTECTED]
Signed-off-by: Francois Romieu [EMAIL PROTECTED]
diff -puN a/drivers/net/sis190.c~sis190-170 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-170 2005-09-02 23:27
601 - 700 of 914 matches
Mail list logo
