Re: SIS190.c

2007-11-09 Thread Francois Romieu
j gleacher <[EMAIL PROTECTED]> : [sorry for the delay, I was busy] > I'm not sure how to properly send you this information about subject, > but with a new Acer Desktop I needed to add 0x0968 to the below to > get the eth0 recognized. Ok. Can you check the patch below against 2.6.24-rc2 ? diff --

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 Erior
Hi I can change the speed with my changes however there is something wrong with taking care of failures. If we are sending something for example have a ping command running and change the speed with mii-tool or disconnect the cable and connect it again, the count on ifconfig says that we are send

Re: sis190 driver

2005-07-29 Thread Erior
This will get the driver to aknowledge mii-tool reported mode, without this the drivers always says "100BaseTx-FD" while my switch shows 10BaseT-HD as the selected mode. /Lars --- sis190.new 2005-07-29 23:26:39.0 + +++ sis190.c2005-07-29 23:38:39.0 + @@ -956,7 +956,8 @

Re: sis190 driver

2005-07-29 Thread Erior
Hi Added PHY identifier for the Asus K8S-MX motherboard. --- sis190.old 2005-07-29 23:16:07.0 + +++ sis190.c2005-07-29 23:15:37.0 + @@ -325,6 +325,7 @@ static struct mii_chip_info { { "Broadcom PHY BCM5461", { 0x0020, 0x60c0 }, LAN }, { "Agere PHY ET11

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-21 Thread Alexey Dobriyan
On Fri, Jul 22, 2005 at 01:09:50AM +0200, Francois Romieu wrote: > 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 net

Re: sis190

2005-07-10 Thread Pascal CHAPPERON
> Message du 09/07/05 23:02 > De : "Francois Romieu" <[EMAIL PROTECTED]> [...] > Can you do the same test but send the traffic from the host which > embeds the r8169 ? > > The sis190 should not be responsive during the flow. I expect that it > will happily return to a normal state once the traffic

Re: sis190

2005-07-09 Thread Francois Romieu
Pascal CHAPPERON <[EMAIL PROTECTED]> : [...] > I don't receive Lars's results, but here are my results. Lars can apparently not reproduce it any more. I'll consider this issue fixed until it returns. Thanks for checking. [ping test removed] > # cat /proc/net/pktgen/eth0 > Params: count 1000

Re: sis190

2005-07-09 Thread Pascal CHAPPERON
> Date: Wed, 6 Jul 2005 23:29:25 +0200 > From: Francois Romieu <[EMAIL PROTECTED]> [...] > The patchkit of the day should fix these issues: > http://www.zoreil.com/~romieu/sis190/20050706-2.6.13-rc1/patches [...] > I'd appreciate if you could check the allowed frame size range, say > ping -s 1468 .

Re: sis190

2005-07-06 Thread Pascal CHAPPERON
> Message du 05/07/05 01:34 > De : "Francois Romieu" <[EMAIL PROTECTED]> [...] > Can you check if there is a regression in sis190-000.patch available at > http://www.zoreil.com/~romieu/sis190/20050704-2.6.13-rc1/patches ? > That one works perfectly; i tried it in the same conditions as the previo

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 sis190_get_