cvs commit: src/sys/pci if_vr.c

[Pyun YongHyeon]

On Sat, Oct 27, 2007 at 02:14:11AM -0200, JoaoBR wrote:
 > On Friday 26 October 2007 10:53:35 Pyun YongHyeon wrote:
 > 
 > >  > >  > > If you think vr(4) is culprit for the issue try overhauled vr(4).
 > >  > >  > > I think I've fixed many unresolved vr(4) issues but it needs more
 > >  > >  > > testing.
 > >  > >  > > You can download the overhauled vr(4) at the following URL.
 > >  > >  > > http://people.freebsd.org/~yongari/vr/if_vr.c
 > >  > >  > > http://people.freebsd.org/~yongari/vr/if_vrreg.h
 > >  > >  > >
 > >  > >  > > Note, don't use the overhauled driver on your production system.
 > >  > >  > > I couldn't see any issues in the driver but it may have unnoticed
 > >  > >  > > bugs.
 > >  > >  >
 > >  > >  > I will arrange a test machine to see how it goes
 > >  > >
 > >  > > Ok. Let me know if you see any unusual things. Pluging/unpluging
 > >  > > cables shouldn't affect the operation of vr(4). I heard stock vr(4)
 > >  > > is vulerable to this type of link changes. In addition, you may
 > >  > > notice better Rx performance.
 > >  >
 > 
 > 
 > Hi
 > 
 > your driver does not work with my hardware here, you forgot something
 > 
 > 
 > then the vr down event seems related to cpufreq and happens only when compiled 
 > in, I am running almost 24h without cpufreq and no down event 
 > 
 > 
 > Your if_vr.c
 > 
 > vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xec00-0xecff mem 
 > 0xec016000-0xec0160ff irq 23 at device 18.0 on pci0
 > vr0: Quirks: 0x0
 > vr0: Revision: 0x78
 > vr0: MII without any phy!
 > device_attach: vr0 attach returned 6
 > 

Sorry, I've fixed it. I applied incorrect mask to get PHY address
for Rhine II. Please try again.

-- 
Regards,
Pyun YongHyeon