[9fans] etherigbe.c

[9fans] etherigbe.c

[Brantley Coile]

Well, I got the driver working for the 8254[17]GI parts.  I did it by
cloning the driver as etherigbe0.c and removing everything that touched
the phy.  Any references to mii were removed.  It only matches the PCI
DIDs for these two chips and can be linked with the original. 

We're racing to finish a product, so we don't have time, but we will
go back and fixup the old driver to know about the new internal phys.
We have the books on the parts so that won't be a problem.

One question I have, though, is why do I want to touch the phy anyway?
Does anyone have a firm reason, other than the general `that's the way
we've always done it.'

Jim?

  Brantley

[9fans] plan9.log

[arisawa]

Hello,

How to understand 'd' flag in plan9.log ?
for example,

term% cp -x /n/sources/plan9/dist/replica/plan9.log x
term% grep acme.pdf x
1105569811 12923 d sys/doc/acme/acme.pdf - 664 sys sys 1020011999 0
term%

I have believed the 'd' means "delete".
However I have noticed:

term% cp -x /n/sources/plan9/dist/replica/plan9.db y
term% grep acme.pdf y
sys/doc/acme/acme.pdf - 664 sys sys 1020384351 117006
term% ls -l /n/sources/plan9/sys/doc/acme/acme.pdf
--rw-rw-r-- M 84 glenda sys 117006 May  3  2002 
/n/sources/plan9/sys/doc/acme/acme.pdf
-bash$

that is, /sys/doc/acme/acme.pdf in sources exists.

Kenji Arisawa

Re: [9fans] etherigbe.c

[jmk]

On Thu Apr  7 21:02:04 EDT 2005, brantley@coraid.com wrote:
> ...
> One question I have, though, is why do I want to touch the phy anyway?
> Does anyone have a firm reason, other than the general `that's the way
> we've always done it.'
> ...

we haven't always done it. in fact, we resisted for a very long time.
the usual reason is that you don't know the state of either the mac or
phy when you boot, so you reset both. sometimes the phy configures
automatically, sometimes not. there are vendor specified registers in
the phy which may need setting. there are bugs in the mac or phy which may
need to be worked around. the phy and mac may be tightly coupled so
the mac doesn't need any tweaking depending on what the phy does, or
they may be more loosely coupled and changes in the phy configuratiuon
(speed, duplex, pause) may require changes in the mac.