Hello,
I’m posting a request for article which would cover the PHY when writing
network driver. The only source of information on that is Network DDK pcnet
driver source. Which functions are in PHY api, what’s the purpose of them?
Also do I need to initialize the phy if my driver is “software emulated”, i
mean virtual driver, which does not have any hardware, but simply transmits
the data through /dev/serX, for ex.
Thanks in advance,
Arunas
No, you don’t. The PHY API is basically just a set of logic for talking
to IEEE standard physical interfaces. IF you don’t have one of these
you don’t need to worry about it. 
chris
Arunas Bytautas <arubyt@elsis.com> wrote:
Hello,
I’m posting a request for article which would cover the PHY when writing
network driver. The only source of information on that is Network DDK pcnet
driver source. Which functions are in PHY api, what’s the purpose of them?Also do I need to initialize the phy if my driver is “software emulated”, i
mean virtual driver, which does not have any hardware, but simply transmits
the data through /dev/serX, for ex.Thanks in advance,
Arunas
\
–
cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Chris McKillop <cdm@qnx.com> wrote:
No, you don’t. The PHY API is basically just a set of logic for talking
to IEEE standard physical interfaces. IF you don’t have one of these
you don’t need to worry about it. >
There is a satuation here.
In you case, you don’t need to worry about the PHY
in net_iov comming down, because you always using
the net_iov.iov_base to access the data pass down.
When you receive a packet, you have to set the
physical address in net_iov, the address is not
used by TCPIP stack, but in case the stack forwarding
your incomming packet to another ethernet interface,
that driver is going to use that physical address.
-xtang
chris
Arunas Bytautas <> arubyt@elsis.com> > wrote:Hello,
I’m posting a request for article which would cover the PHY when writing
network driver. The only source of information on that is Network DDK pcnet
driver source. Which functions are in PHY api, what’s the purpose of them?Also do I need to initialize the phy if my driver is “software emulated”, i
mean virtual driver, which does not have any hardware, but simply transmits
the data through /dev/serX, for ex.Thanks in advance,
Arunas
\cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL