Re: realtec 8169 driver for linux kernel 2.4.22 : latest version

2005-08-03 Thread Francois Romieu
schb Schönbauer Peter <[EMAIL PROTECTED]> : [r8169 driver for 2.4.x] Against 2.4.31: http://www.zoreil.com/~romieu/r8169/20050803-2.4.31-r8169-test.patch -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More

Re: realtec 8169 driver for linux kernel 2.4.22 : latest version

2005-08-03 Thread Francois Romieu
schb Schönbauer Peter [EMAIL PROTECTED] : [r8169 driver for 2.4.x] Against 2.4.31: http://www.zoreil.com/~romieu/r8169/20050803-2.4.31-r8169-test.patch -- Ueimor - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo

Re: How come that in kernel 2.6.11 a dvd is readable, but not in kernel 2.6.12?

2005-07-31 Thread Francois Romieu
apache <[EMAIL PROTECTED]> : [...] > Fact: I can write a DVD on a machine with kernel-2.6.11, but I cannot > read that DVD in a machine with kernel-2.6.12, even worse: the system is > stuck. > > please explain I can't explain but we may try to fix it with your help. As a general remark, dmesg

Re: How come that in kernel 2.6.11 a dvd is readable, but not in kernel 2.6.12?

2005-07-31 Thread Francois Romieu
apache [EMAIL PROTECTED] : [...] Fact: I can write a DVD on a machine with kernel-2.6.11, but I cannot read that DVD in a machine with kernel-2.6.12, even worse: the system is stuck. please explain I can't explain but we may try to fix it with your help. As a general remark, dmesg +

Re: [patch 2.6.13-rc3] sis190 driver

2005-07-30 Thread Francois Romieu
Pascal CHAPPERON <[EMAIL PROTECTED]> : [...] > By the way, i still can not force speed/mode/autoneg (ethtool or mii-tool); > ethtool reports correctly the changes, but autoneg is not really disabled, > and the driver falls back to 100 Full... > > Had Lars better results with autoneg off? I

Re: [patch 2.6.13-rc3] sis190 driver

2005-07-30 Thread Francois Romieu
Pascal CHAPPERON <[EMAIL PROTECTED]> : [...] > sis190-120 compiles, loads but does not work (sis190_init_phy() function). > > # service network start > Bringing up loopback interface:[ OK ] > Bringing up interface eth0: > Determining IP information for eth0...

Re: [patch 2.6.13-rc3] sis190 driver

2005-07-30 Thread Francois Romieu
Pascal CHAPPERON [EMAIL PROTECTED] : [...] sis190-120 compiles, loads but does not work (sis190_init_phy() function). # service network start Bringing up loopback interface:[ OK ] Bringing up interface eth0: Determining IP information for eth0... failed; no

Re: sis190 driver

2005-07-29 Thread Francois Romieu
Erior <[EMAIL PROTECTED]> : [...] > Is there any kind of test or information I can provid to help you fixing > this ? It could help to know if the device reports a link event interrupt or such. (ethtool allow to modify the log level of the driver if required). Don't hesitate to publish a complete

Re: sis190 driver

2005-07-29 Thread Francois Romieu
Erior <[EMAIL PROTECTED]> : [...] > Added PHY identifier for the Asus K8S-MX motherboard. - is it ok to add a Signed-off-by: Lars Vahlenberg <[EMAIL PROTECTED]> ? - how the whole driver work now ? -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

Re: sis190 driver

2005-07-29 Thread Francois Romieu
Erior [EMAIL PROTECTED] : [...] Added PHY identifier for the Asus K8S-MX motherboard. - is it ok to add a Signed-off-by: Lars Vahlenberg [EMAIL PROTECTED] ? - how the whole driver work now ? -- Ueimor - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a

Re: sis190 driver

2005-07-29 Thread Francois Romieu
Erior [EMAIL PROTECTED] : [...] Is there any kind of test or information I can provid to help you fixing this ? It could help to know if the device reports a link event interrupt or such. (ethtool allow to modify the log level of the driver if required). Don't hesitate to publish a complete

[patch 2.6.13-rc3] sis190 driver

2005-07-28 Thread Francois Romieu
Single file patch: http://www.zoreil.com/~romieu/sis190/20050728-2.6.13-rc3-sis190-test.patch Patch-kit: http://www.zoreil.com/~romieu/sis190/20050728-2.6.13-rc3/patches Tarball: http://www.zoreil.com/~romieu/sis190/20050728-2.6.13-rc3.tar.bz2 Changes from previous version (20050722) o Add

[patch 2.6.13-rc3] sis190 driver

2005-07-28 Thread Francois Romieu
Single file patch: http://www.zoreil.com/~romieu/sis190/20050728-2.6.13-rc3-sis190-test.patch Patch-kit: http://www.zoreil.com/~romieu/sis190/20050728-2.6.13-rc3/patches Tarball: http://www.zoreil.com/~romieu/sis190/20050728-2.6.13-rc3.tar.bz2 Changes from previous version (20050722) o Add

Re: sis190 driver

2005-07-27 Thread Francois Romieu
[bouncing @sis.com address removed from the Cc:] Lars Vahlenberg <[EMAIL PROTECTED]> : [...] > I can get mii-tool to work with this patch, but if I have > a ping command running and changing to another speed I > stop receiving or get 1 - 3 sek pings. ei x000ms. The current SiS driver is way more

Re: sis190 driver

2005-07-27 Thread Francois Romieu
[bouncing @sis.com address removed from the Cc:] Lars Vahlenberg [EMAIL PROTECTED] : [...] I can get mii-tool to work with this patch, but if I have a ping command running and changing to another speed I stop receiving or get 1 - 3 sek pings. ei x000ms. The current SiS driver is way more

Re: NAPI (aka RX Polling) for natsemi?

2005-07-22 Thread Francois Romieu
Daniel Higgins <[EMAIL PROTECTED]> : [napi for natsemi] Can you please fill a bugzilla entry for it at bugzilla.kernel.org ? -- 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

Re: NAPI (aka RX Polling) for natsemi?

2005-07-22 Thread Francois Romieu
Daniel Higgins [EMAIL PROTECTED] : [napi for natsemi] Can you please fill a bugzilla entry for it at bugzilla.kernel.org ? -- 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

sis190 driver

2005-07-21 Thread Francois Romieu
No major change from previous version. I'm quietly merging bits from the SiS driver that Lars kindly pointed out. The detection of the mac address is done differently. I'll welcome feedback related to regressions and/or netconsole testing. Single file patch:

Re: Supermount

2005-07-21 Thread Francois Romieu
Lasse K??rkk??inen / Tronic <[EMAIL PROTECTED]> : > Is there a reason why this magnificient piece of software is not already > in the mainline? Yes, there is. Please search the archives. -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: Supermount

2005-07-21 Thread Francois Romieu
Lasse K??rkk??inen / Tronic [EMAIL PROTECTED] : Is there a reason why this magnificient piece of software is not already in the mainline? Yes, there is. Please search the archives. -- Ueimor - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to

sis190 driver

2005-07-21 Thread Francois Romieu
No major change from previous version. I'm quietly merging bits from the SiS driver that Lars kindly pointed out. The detection of the mac address is done differently. I'll welcome feedback related to regressions and/or netconsole testing. Single file patch:

Re: 2.6.10 Kernel Goes Crazy After Resetting MTU

2005-07-17 Thread Francois Romieu
[EMAIL PROTECTED] <[EMAIL PROTECTED]> : [2.6.10 + e1000 + page allocation failure] > Any ideas? - upgrade - increase vm.min_free_kbytes - renice kswapd - Cc: Nick Piggin and netdev@vger.kernel.org -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

Re: 2.6.10 Kernel Goes Crazy After Resetting MTU

2005-07-17 Thread Francois Romieu
[EMAIL PROTECTED] [EMAIL PROTECTED] : [2.6.10 + e1000 + page allocation failure] Any ideas? - upgrade - increase vm.min_free_kbytes - renice kswapd - Cc: Nick Piggin and netdev@vger.kernel.org -- Ueimor - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a

Re: [PATCH] add rlimit file to /proc/PID

2005-07-15 Thread Francois Romieu
dierbro <[EMAIL PROTECTED]> : [...] > with a friend i have made this patch that add rlimit file to /proc/PID > directory. > Trought this file you can set and get rlimit of a running process. I am not sure that new proc-functions will be welcome, anyway... [...] > ---

Re: [PATCH] add rlimit file to /proc/PID

2005-07-15 Thread Francois Romieu
dierbro [EMAIL PROTECTED] : [...] with a friend i have made this patch that add rlimit file to /proc/PID directory. Trought this file you can set and get rlimit of a running process. I am not sure that new proc-functions will be welcome, anyway... [...] --- linux-2.6.13-rc3/fs/proc/base.c

Re: [RFC][PATCH] split PCI probing code [1/9]

2005-07-14 Thread Francois Romieu
Greg KH <[EMAIL PROTECTED]> : > On Thu, Jul 14, 2005 at 07:10:14PM +0200, Francois Romieu wrote: > > Adam Belay <[EMAIL PROTECTED]> : > > [...] > > > > Some nits + a suspect error branch. It seems nice otherwise. > > If I'm correct, this p

Re: [RFC][PATCH] split PCI probing code [1/9]

2005-07-14 Thread Francois Romieu
Adam Belay <[EMAIL PROTECTED]> : [...] Some nits + a suspect error branch. It seems nice otherwise. > --- a/drivers/pci/bus/bus.c 1969-12-31 19:00:00.0 -0500 > +++ b/drivers/pci/bus/bus.c 2005-07-10 22:32:53.0 -0400 [...] > +struct pci_bus * pci_alloc_bus(void) > +{ > +

Re: [RFC][PATCH] split PCI probing code [1/9]

2005-07-14 Thread Francois Romieu
Adam Belay [EMAIL PROTECTED] : [...] Some nits + a suspect error branch. It seems nice otherwise. --- a/drivers/pci/bus/bus.c 1969-12-31 19:00:00.0 -0500 +++ b/drivers/pci/bus/bus.c 2005-07-10 22:32:53.0 -0400 [...] +struct pci_bus * pci_alloc_bus(void) +{ + struct

Re: [RFC][PATCH] split PCI probing code [1/9]

2005-07-14 Thread Francois Romieu
Greg KH [EMAIL PROTECTED] : On Thu, Jul 14, 2005 at 07:10:14PM +0200, Francois Romieu wrote: Adam Belay [EMAIL PROTECTED] : [...] Some nits + a suspect error branch. It seems nice otherwise. If I'm correct, this patch only moves the code into different files, it doesn't change any

Re: [05/11] SMP fix for 6pack driver

2005-07-13 Thread Francois Romieu
Greg KH <[EMAIL PROTECTED]> : > -stable review patch. If anyone has any objections, please let us know. > > -- > > > Drivers really only work well in SMP if they actually can be selected. > This is a leftover from the time when the 6pack drive only used to be > a bitrotten

Re: [05/11] SMP fix for 6pack driver

2005-07-13 Thread Francois Romieu
Greg KH [EMAIL PROTECTED] : -stable review patch. If anyone has any objections, please let us know. -- Drivers really only work well in SMP if they actually can be selected. This is a leftover from the time when the 6pack drive only used to be a bitrotten variant of the

Re: sis190

2005-07-09 Thread Francois Romieu
makes a difference (the patch applies on top of the current driver). Can you issue a simple 'ethtool -s eth0 autoneg off' and report what happens ? [html] Sorry, it was just a notice for Lars -- Ueimor Do not update StationControl after the link was forced. Signed-off-by: Francois Romieu

Re: sis190

2005-07-09 Thread Francois Romieu
-off-by: Francois Romieu [EMAIL PROTECTED] diff -puN drivers/net/sis190.c~sis190-030 drivers/net/sis190.c --- linux-2.6.13-rc1-gitXX/drivers/net/sis190.c~sis190-030 2005-07-09 22:11:02.381627199 +0200 +++ linux-2.6.13-rc1-gitXX-romieu/drivers/net/sis190.c 2005-07-09 22:25:37.537549276 +0200

Re: sis190

2005-07-06 Thread Francois Romieu
Pascal CHAPPERON <[EMAIL PROTECTED]> : [...] > That one works perfectly; i tried it in the same conditions as > the previous patch, and i don't notice a regression. Nice. [...] > sis190-010.patch does not compile properly : Point taken. Thanks. [...] > But i get those traces in syslog, when

Re: sis190

2005-07-06 Thread Francois Romieu
Pascal CHAPPERON [EMAIL PROTECTED] : [...] That one works perfectly; i tried it in the same conditions as the previous patch, and i don't notice a regression. Nice. [...] sis190-010.patch does not compile properly : Point taken. Thanks. [...] But i get those traces in syslog, when the

Re: sis190

2005-07-04 Thread Francois Romieu
Pascal CHAPPERON <[EMAIL PROTECTED]> : [...] > I can not make other tries before Monday, but i'll take a > look at the media management after... > > BTW, can you remove the following printks from the patch ? > The printks in interrupt functions make dmesg unusuable, > and the stuff in

Re: sis190

2005-07-04 Thread Francois Romieu
Pascal CHAPPERON [EMAIL PROTECTED] : [...] I can not make other tries before Monday, but i'll take a look at the media management after... BTW, can you remove the following printks from the patch ? The printks in interrupt functions make dmesg unusuable, and the stuff in sis190_get_drvinfo

Re: [PATCH 1/3] cifs: md5 cleanup - functions

2005-04-12 Thread Francois Romieu
Steve French <[EMAIL PROTECTED]> : [...] > There was a patch suggested a year or so ago to remove the older cifs > md5 implementation and have cifsencrypt.c use the newer Linux crypto > API, but since it made the code considerably more complex it did not > make any sense. The current crypto API

Re: [PATCH 1/3] cifs: md5 cleanup - functions

2005-04-12 Thread Francois Romieu
Steve French [EMAIL PROTECTED] : [...] There was a patch suggested a year or so ago to remove the older cifs md5 implementation and have cifsencrypt.c use the newer Linux crypto API, but since it made the code considerably more complex it did not make any sense. The current crypto API seems to

Re: r8169 native module problems on 2.6.11

2005-04-10 Thread Francois Romieu
TommyDrum <[EMAIL PROTECTED]> : [new brand of r8169 adapter coming into town] > and dmesg for both: > > kernel native: > > ACPI: PCI interrupt :00:09.0[A] -> GSI 11 (level, low) -> IRQ 11 > eth0: Identified chip type is 'RTL8169s/8110s'. > eth0: U.S. Robotics 10/100/1000 PCI NIC driver

Re: r8169 native module problems on 2.6.11

2005-04-10 Thread Francois Romieu
TommyDrum [EMAIL PROTECTED] : [new brand of r8169 adapter coming into town] and dmesg for both: kernel native: ACPI: PCI interrupt :00:09.0[A] - GSI 11 (level, low) - IRQ 11 eth0: Identified chip type is 'RTL8169s/8110s'. eth0: U.S. Robotics 10/100/1000 PCI NIC driver version 2.0 at

Re: [RFC,PATCH 3/4] Change synchronize_kernel to _rcu and _sched

2005-04-09 Thread Francois Romieu
Manfred Spraul <[EMAIL PROTECTED]> : [...] > I always thought that all callers of dev->hard_start_xmit() acquire > dev->xmit_lock before calling hard_start_xmit(). > > Is that assumption wrong? I think I even rely on that in one of my > drivers. Afaik, no, it is right. This part of the r8169

Re: [RFC,PATCH 3/4] Change synchronize_kernel to _rcu and _sched

2005-04-09 Thread Francois Romieu
Manfred Spraul <[EMAIL PROTECTED]> : > [Jeff added to cc list - it's a network driver question] [...] > I haven't read the whole driver, but what about > spin_unlock_wait(>xmit_lock); > ? The race here is a dev->close() against dev->hard_start_xmit() one where dev->hard_start_xmit() does

Re: [RFC,PATCH 3/4] Change synchronize_kernel to _rcu and _sched

2005-04-09 Thread Francois Romieu
Manfred Spraul [EMAIL PROTECTED] : [Jeff added to cc list - it's a network driver question] [...] I haven't read the whole driver, but what about spin_unlock_wait(dev-xmit_lock); ? The race here is a dev-close() against dev-hard_start_xmit() one where dev-hard_start_xmit() does not do

Re: [RFC,PATCH 3/4] Change synchronize_kernel to _rcu and _sched

2005-04-09 Thread Francois Romieu
Manfred Spraul [EMAIL PROTECTED] : [...] I always thought that all callers of dev-hard_start_xmit() acquire dev-xmit_lock before calling hard_start_xmit(). Is that assumption wrong? I think I even rely on that in one of my drivers. Afaik, no, it is right. This part of the r8169 driver

Re: [RFC,PATCH 3/4] Change synchronize_kernel to _rcu and _sched

2005-04-07 Thread Francois Romieu
Paul E. McKenney <[EMAIL PROTECTED]> : > This patch changes calls to synchronize_kernel(), deprecated in the > earlier "Deprecate synchronize_kernel, GPL replacement" patch to > instead call the new synchronize_rcu() and synchronize_sched() APIs. [...] > diff -urpN -X dontdiff

Re: [RFC,PATCH 3/4] Change synchronize_kernel to _rcu and _sched

2005-04-07 Thread Francois Romieu
Paul E. McKenney [EMAIL PROTECTED] : This patch changes calls to synchronize_kernel(), deprecated in the earlier Deprecate synchronize_kernel, GPL replacement patch to instead call the new synchronize_rcu() and synchronize_sched() APIs. [...] diff -urpN -X dontdiff

Re: How's the nforce4 support in Linux?

2005-03-30 Thread Francois Romieu
Jeff Garzik <[EMAIL PROTECTED]> : > Andi Kleen wrote: [r8169 driver] > >It does not seem to support DAC (or rather it breaks with DAC enabled), > >which makes it not very useful on any machine with >3GB of memory. > > Driver bug. I can futz with it and get it to do 64-bit on my Athlon64. Care

Re: How's the nforce4 support in Linux?

2005-03-30 Thread Francois Romieu
Jeff Garzik [EMAIL PROTECTED] : Andi Kleen wrote: [r8169 driver] It does not seem to support DAC (or rather it breaks with DAC enabled), which makes it not very useful on any machine with 3GB of memory. Driver bug. I can futz with it and get it to do 64-bit on my Athlon64. Care to send a

[PATCH] r8169 backport for 2.4.x

2005-03-26 Thread Francois Romieu
It took a bit longer than expected but the backport of the r8169 driver has been updated for kernel 2.4.29. Noticeable changes since 12/2004: - better handling of PHY as found on Acer Aspire 1524WLMi (Richard Dawe); - fix a bug triggered when the device is brought down then up again; - avoid a

[PATCH] r8169 backport for 2.4.x

2005-03-26 Thread Francois Romieu
It took a bit longer than expected but the backport of the r8169 driver has been updated for kernel 2.4.29. Noticeable changes since 12/2004: - better handling of PHY as found on Acer Aspire 1524WLMi (Richard Dawe); - fix a bug triggered when the device is brought down then up again; - avoid a

Re: PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard

2005-03-24 Thread Francois Romieu
Daniel Egger <[EMAIL PROTECTED]> : [...] > NFS machines on the Gbit network will resume operation) I popped > in the chp RealTek card (which caused some slight problems > like permanent hangs and bad performance before) and everything > works like a charm. Of course, after throwing in some

Re: PCI interrupt problem: e1000 Super-Micro X6DVA motherboard

2005-03-24 Thread Francois Romieu
Daniel Egger [EMAIL PROTECTED] : [...] NFS machines on the Gbit network will resume operation) I popped in the chp RealTek card (which caused some slight problems like permanent hangs and bad performance before) and everything works like a charm. Of course, after throwing in some extra

Re: Kernel panic - r8169 on 2.6.11-rc1-mm1

2005-03-19 Thread Francois Romieu
Cameron Harris <[EMAIL PROTECTED]> : [r8169 crash] > Linux laptop 2.6.11-rc1-mm1 #2 SMP Sun Jan 16 22:36:26 GMT 2005 i686 ^^ [...] > I would try a newer kernel, but the command line options for > specifying the framebuffer settings seems to have changed in the > latest

Re: Kernel panic - r8169 on 2.6.11-rc1-mm1

2005-03-19 Thread Francois Romieu
Cameron Harris [EMAIL PROTECTED] : [r8169 crash] Linux laptop 2.6.11-rc1-mm1 #2 SMP Sun Jan 16 22:36:26 GMT 2005 i686 ^^ [...] I would try a newer kernel, but the command line options for specifying the framebuffer settings seems to have changed in the latest kernel

Re: yenta_socket "nobody cared - Disabling IRQ #4"

2005-03-18 Thread Francois Romieu
Jonas Oreland <[EMAIL PROTECTED]> : [...] > Report: > 1) It works somewhat better. irq doesn't get disabled. > 2) however wlan card get disfunctional. I haven't been able to contact my > wap > even if i'm standing on it... > 3) unplug has resulted in kernel panic (twice) > (btw: how do I do

Re: yenta_socket nobody cared - Disabling IRQ #4

2005-03-18 Thread Francois Romieu
Jonas Oreland [EMAIL PROTECTED] : [...] Report: 1) It works somewhat better. irq doesn't get disabled. 2) however wlan card get disfunctional. I haven't been able to contact my wap even if i'm standing on it... 3) unplug has resulted in kernel panic (twice) (btw: how do I do to capture

Re: [patch 14/15] drivers/block/*: convert to pci_register_driver

2005-03-05 Thread Francois Romieu
[EMAIL PROTECTED] <[EMAIL PROTECTED]> : [...] > diff -puN drivers/block/umem.c~pci_register_driver-drivers_block > drivers/block/umem.c > --- kj/drivers/block/umem.c~pci_register_driver-drivers_block 2005-03-05 > 16:12:16.0 +0100 > +++ kj-domen/drivers/block/umem.c 2005-03-05

Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec

2005-03-04 Thread Francois Romieu
Jeff Garzik <[EMAIL PROTECTED]> : > Greg KH wrote: [...] > >An alias would probably be easier, unless you think everything sent > >there should be archived? > > I do. But I don't have a strong opinion on the subject. A bk-commit mailing-list would be nice. -- Ueimor - To unsubscribe from this

Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec

2005-03-04 Thread Francois Romieu
Jeff Garzik [EMAIL PROTECTED] : Greg KH wrote: [...] An alias would probably be easier, unless you think everything sent there should be archived? I do. But I don't have a strong opinion on the subject. A bk-commit mailing-list would be nice. -- Ueimor - To unsubscribe from this list:

Re: [BK PATCHES] 2.6.x r8169 update

2005-02-23 Thread Francois Romieu
Jeff Garzik <[EMAIL PROTECTED]> : [...] > Agree it needs fixing, but I actually think the rx-offset stuff is more > urgent than this. For the future, it would be useful for both of us to > have separate r8169-fixes and r8169-cleanups queues. Do you have a synonym/pointer for the rx-offset

Re: 2.6.11-rc4-mm1

2005-02-23 Thread Francois Romieu
Andrew Morton <[EMAIL PROTECTED]> : [...] > - Last, final, ultimate call: if anyone has patches in here which are 2.6.11 > material, please tell me. Any chance to convince the alien who took control of Jeff's libata queue to push: r8169: synchronization and balancing when the device is closed

[patch 2.6.11-rc4-mm1 2/2] r8169: factor out some code.

2005-02-23 Thread Francois Romieu
Factor out some code Signed-off-by: Francois Romieu <[EMAIL PROTECTED]> diff -puN drivers/net/r8169.c~r8169-460 drivers/net/r8169.c --- a/drivers/net/r8169.c~r8169-460 2005-02-23 21:35:28.715271999 +0100 +++ b/drivers/net/r8169.c 2005-02-23 21:35:28.720271177 +0100 @@ -495,6 +

[patch 2.6.11-rc4-mm1 1/2] r8169: IRQ races during change of mtu

2005-02-23 Thread Francois Romieu
it safe to request a change of mtu on a live device. Signed-off-by: Francois Romieu <[EMAIL PROTECTED]> diff -puN drivers/net/r8169.c~r8169-450 drivers/net/r8169.c --- a/drivers/net/r8169.c~r8169-450 2005-02-23 21:35:21.112521942 +0100 +++ b/drivers/net/r8169.c 2005-02-23

Re: [rft/update] r8169 changes in 2.6.x

2005-02-23 Thread Francois Romieu
Andrew Morton <[EMAIL PROTECTED]> : > There are already a bunch of r8169 patches in Jeff's tree. The combination > isn't pretty: [removed by parental advisory] I sent r8169-4{0/1/2/3/4}0 on netdev + Jeff the 22/02/2005. Jeff's netdev (thus your tree) already had the r8169-3xx changes. Jeff has

Re: [rft/update] r8169 changes in 2.6.x

2005-02-23 Thread Francois Romieu
Andrew Morton [EMAIL PROTECTED] : There are already a bunch of r8169 patches in Jeff's tree. The combination isn't pretty: [removed by parental advisory] I sent r8169-4{0/1/2/3/4}0 on netdev + Jeff the 22/02/2005. Jeff's netdev (thus your tree) already had the r8169-3xx changes. Jeff has

[patch 2.6.11-rc4-mm1 1/2] r8169: IRQ races during change of mtu

2005-02-23 Thread Francois Romieu
it safe to request a change of mtu on a live device. Signed-off-by: Francois Romieu [EMAIL PROTECTED] diff -puN drivers/net/r8169.c~r8169-450 drivers/net/r8169.c --- a/drivers/net/r8169.c~r8169-450 2005-02-23 21:35:21.112521942 +0100 +++ b/drivers/net/r8169.c 2005-02-23 21:35:21.117521120

[patch 2.6.11-rc4-mm1 2/2] r8169: factor out some code.

2005-02-23 Thread Francois Romieu
Factor out some code Signed-off-by: Francois Romieu [EMAIL PROTECTED] diff -puN drivers/net/r8169.c~r8169-460 drivers/net/r8169.c --- a/drivers/net/r8169.c~r8169-460 2005-02-23 21:35:28.715271999 +0100 +++ b/drivers/net/r8169.c 2005-02-23 21:35:28.720271177 +0100 @@ -495,6 +495,13

Re: 2.6.11-rc4-mm1

2005-02-23 Thread Francois Romieu
Andrew Morton [EMAIL PROTECTED] : [...] - Last, final, ultimate call: if anyone has patches in here which are 2.6.11 material, please tell me. Any chance to convince the alien who took control of Jeff's libata queue to push: r8169: synchronization and balancing when the device is closed

Re: [BK PATCHES] 2.6.x r8169 update

2005-02-23 Thread Francois Romieu
Jeff Garzik [EMAIL PROTECTED] : [...] Agree it needs fixing, but I actually think the rx-offset stuff is more urgent than this. For the future, it would be useful for both of us to have separate r8169-fixes and r8169-cleanups queues. Do you have a synonym/pointer for the rx-offset stuff ?

[rft/update] r8169 changes in 2.6.x

2005-02-22 Thread Francois Romieu
An update of the r8169 driver is available for the 2.6.11-rc4 kernel. Noticable changes: - better handling of PHY as found on Acer Aspire 1524WLMi (Richard Dawe); - fix a bug triggered when the device is brought down then up again; - avoid a few lost/screaming interrupts; - closed a race when a

[rft/update] r8169 changes in 2.6.x

2005-02-22 Thread Francois Romieu
An update of the r8169 driver is available for the 2.6.11-rc4 kernel. Noticable changes: - better handling of PHY as found on Acer Aspire 1524WLMi (Richard Dawe); - fix a bug triggered when the device is brought down then up again; - avoid a few lost/screaming interrupts; - closed a race when a

Re: strange bug with realtek 8169 card

2005-02-16 Thread Francois Romieu
Alexandre <[EMAIL PROTECTED]> : [...] > thanks again, unfortunately PCs with those cards are at work, and from > today that's holidays until march 7th... :D Excellent. Your testing will not impact the normal production. I have done a minor update to sync with Jeff's latest -netdev

Re: strange bug with realtek 8169 card

2005-02-16 Thread Francois Romieu
shishir verma <[EMAIL PROTECTED]> : > by any chance is the watchdog enabled for the card...because i had a > similar problem with a broadcom gigabit cardi commented the > watchdog code and made the module again... > it worked like a charm for me after that... The original user wrote: [...] >

Re: strange bug with realtek 8169 card

2005-02-16 Thread Francois Romieu
Alexandre <[EMAIL PROTECTED]> : [...] > Any other idea ? Please try: http://www.fr.zoreil.com/~francois/misc/20050202-2.4.29-r8169.c-test.patch Compile with gcc-3.x and send/publish _complete_ dmesg + lspci -vx + cat /proc/interrupts + ifconfig if it still hangs. -- Ueimor - To unsubscribe from

Re: strange bug with realtek 8169 card

2005-02-16 Thread Francois Romieu
Alexandre [EMAIL PROTECTED] : [...] Any other idea ? Please try: http://www.fr.zoreil.com/~francois/misc/20050202-2.4.29-r8169.c-test.patch Compile with gcc-3.x and send/publish _complete_ dmesg + lspci -vx + cat /proc/interrupts + ifconfig if it still hangs. -- Ueimor - To unsubscribe from

Re: strange bug with realtek 8169 card

2005-02-16 Thread Francois Romieu
shishir verma [EMAIL PROTECTED] : by any chance is the watchdog enabled for the card...because i had a similar problem with a broadcom gigabit cardi commented the watchdog code and made the module again... it worked like a charm for me after that... The original user wrote: [...] If I

Re: strange bug with realtek 8169 card

2005-02-16 Thread Francois Romieu
Alexandre [EMAIL PROTECTED] : [...] thanks again, unfortunately PCs with those cards are at work, and from today that's holidays until march 7th... :D Excellent. Your testing will not impact the normal production. I have done a minor update to sync with Jeff's latest -netdev

Re: strange bug with realtek 8169 card

2005-02-15 Thread Francois Romieu
Alexandre <[EMAIL PROTECTED]> : [...] > Or any idea why the problem occurs and how to correct this (if it is > possbile)? Upgrade the compiler if you use gcc 2.95.x. -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED]

Re: strange bug with realtek 8169 card

2005-02-15 Thread Francois Romieu
Alexandre [EMAIL PROTECTED] : [...] Or any idea why the problem occurs and how to correct this (if it is possbile)? Upgrade the compiler if you use gcc 2.95.x. -- Ueimor - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More

Re: Linux 2.6.11-rc4

2005-02-13 Thread Francois Romieu
Linus Torvalds <[EMAIL PROTECTED]> : [...] > this is hopefully the last -rc kernel before the real 2.6.11, so please > give it a whirl, and complain loudly about anything broken. - dscc4 (patch in Jeff's -netdev) Apart the fact that the driver crashes on module insertion and is unusable,

Re: Linux 2.6.11-rc4

2005-02-13 Thread Francois Romieu
Linus Torvalds [EMAIL PROTECTED] : [...] this is hopefully the last -rc kernel before the real 2.6.11, so please give it a whirl, and complain loudly about anything broken. - dscc4 (patch in Jeff's -netdev) Apart the fact that the driver crashes on module insertion and is unusable, users

Re: [RFC] Linux Kernel Subversion Howto

2005-02-04 Thread Francois Romieu
Stelian Pop <[EMAIL PROTECTED]> : [...] > Now, suppose one of my patches introduced a problem. How can someone > not using BK isolate the patch which introduced the problem ? All he > can do is to back out the entire set of patches, and the whole point > of having split the patch initialy into

Re: [RFC] Linux Kernel Subversion Howto

2005-02-04 Thread Francois Romieu
Stelian Pop [EMAIL PROTECTED] : [...] Now, suppose one of my patches introduced a problem. How can someone not using BK isolate the patch which introduced the problem ? All he can do is to back out the entire set of patches, and the whole point of having split the patch initialy into logical

Re: [2.6 patch] remove subscribers-only tlinux-users address

2005-01-31 Thread Francois Romieu
Adrian Bunk <[EMAIL PROTECTED]> : > It's generally agreed that subscribers-only mailing lists shouldn't be > listed in MAINTAINERS (since it's impossible to send a simple Cc to such > a list). What about marking the mailing-list as subscriber-only instead of removing information ? -- Ueimor -

Re: [2.6 patch] remove subscribers-only tlinux-users address

2005-01-31 Thread Francois Romieu
Adrian Bunk [EMAIL PROTECTED] : It's generally agreed that subscribers-only mailing lists shouldn't be listed in MAINTAINERS (since it's impossible to send a simple Cc to such a list). What about marking the mailing-list as subscriber-only instead of removing information ? -- Ueimor - To

Re: Bug report : drivers/net/hamradio/Kconfig

2005-01-24 Thread Francois Romieu
[EMAIL PROTECTED] <[EMAIL PROTECTED]> : [...] > I've also made a patch, my first too :))) : > http://bugzilla.kernel.org/attachment.cgi?id=4450=view > > I don't know if the patch is correct, but i think The second hunk is not strictly needed. It could be removed. > Should I do some other thing

Re: Bug report : drivers/net/hamradio/Kconfig

2005-01-24 Thread Francois Romieu
[EMAIL PROTECTED] [EMAIL PROTECTED] : [...] I've also made a patch, my first too :))) : http://bugzilla.kernel.org/attachment.cgi?id=4450action=view I don't know if the patch is correct, but i think The second hunk is not strictly needed. It could be removed. Should I do some other thing ?

Re: Request for comments

2001-07-19 Thread Francois Romieu
Cornel Ciocirlan <[EMAIL PROTECTED]> ecrit : [heavy linux networking rewrite in sight] > Is it useful at all ? Point b) above could be implemented in userspace > (Actually I've done a basic skeleton a while ago). Are the others worth > the trouble ? > > What do you gurus think ? * Are you sure

Re: Request for comments

2001-07-19 Thread Francois Romieu
Cornel Ciocirlan [EMAIL PROTECTED] ecrit : [heavy linux networking rewrite in sight] Is it useful at all ? Point b) above could be implemented in userspace (Actually I've done a basic skeleton a while ago). Are the others worth the trouble ? What do you gurus think ? * Are you sure of

Re: [PATCH] Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-06 Thread Francois Romieu
Jeff Garzik <[EMAIL PROTECTED]> ecrit : [...] > --- /spare/tmp/linux-2.4.7-pre3/drivers/net/epic100.c Mon Jul 2 21:03:04 2001 > +++ linux/drivers/net/epic100.c Fri Jul 6 12:56:40 2001 [...] > /* The user-configurable values. > @@ -448,7 +451,7 @@ > outl(0x0008, ioaddr + TEST1); >

Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-06 Thread Francois Romieu
Juergen Wolf <[EMAIL PROTECTED]> ecrit : [...] > Luckily I got a very helpfull hint from Hans-Christian Armingeon in > reply to my questions here on the list. The epic100.c from > http://lrcwww.epfl.ch/~boch/sw/epic100.c.txt fixes the problem in all > the affected kernel versions. Interesting.

Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-06 Thread Francois Romieu
Juergen Wolf [EMAIL PROTECTED] ecrit : [...] Luckily I got a very helpfull hint from Hans-Christian Armingeon in reply to my questions here on the list. The epic100.c from http://lrcwww.epfl.ch/~boch/sw/epic100.c.txt fixes the problem in all the affected kernel versions. Interesting. -

Re: [PATCH] Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-06 Thread Francois Romieu
Jeff Garzik [EMAIL PROTECTED] ecrit : [...] --- /spare/tmp/linux-2.4.7-pre3/drivers/net/epic100.c Mon Jul 2 21:03:04 2001 +++ linux/drivers/net/epic100.c Fri Jul 6 12:56:40 2001 [...] /* The user-configurable values. @@ -448,7 +451,7 @@ outl(0x0008, ioaddr + TEST1);

Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-04 Thread Francois Romieu
Juergen Wolf <[EMAIL PROTECTED]> ecrit : [...] Jul 2 13:06:59 localhost kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004. Receive Status Valid Receive Copy In Progress Transmit Idle Receive Queue Empty -> no more receive buffer available It looks like one waits too long before

Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-04 Thread Francois Romieu
Florian Schmitt <[EMAIL PROTECTED]> ecrit : [...] > Same problem here, it won't run at all on newer kernels. But it isn't even > 100% stable in 2.2.x here - on very high network traffic the card stops > working. In this case, it helps to pull the network plug for a short time, Could you

Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-04 Thread Francois Romieu
Florian Schmitt [EMAIL PROTECTED] ecrit : [...] Same problem here, it won't run at all on newer kernels. But it isn't even 100% stable in 2.2.x here - on very high network traffic the card stops working. In this case, it helps to pull the network plug for a short time, Could you specify

Re: Problem with SMC Etherpower II + kernel newer 2.4.2

2001-07-04 Thread Francois Romieu
Juergen Wolf [EMAIL PROTECTED] ecrit : [...] Jul 2 13:06:59 localhost kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004. Receive Status Valid Receive Copy In Progress Transmit Idle Receive Queue Empty - no more receive buffer available It looks like one waits too long before

Re: fealnx problem

2001-06-22 Thread Francois Romieu
Jon Forsberg <[EMAIL PROTECTED]> ecrit : [...] > Prints the same messages as before but continues working afterwards. No need > for ifdown/ifup in other words. No crash so far. I'll polish and submit it to the maintainer next week then. -- Ueimor - To unsubscribe from this list: send the line

Re: fealnx problem

2001-06-22 Thread Francois Romieu
Jon Forsberg [EMAIL PROTECTED] ecrit : [...] Prints the same messages as before but continues working afterwards. No need for ifdown/ifup in other words. No crash so far. I'll polish and submit it to the maintainer next week then. -- Ueimor - To unsubscribe from this list: send the line

<    3   4   5   6   7   8   9   10   >