On Tue, 25 May 1999, Stefano Giacometti wrote:
> Have you got some code that uses these ioctl?
> > > trying to use the private ioctl, but it seems to me that there is
> > > a problem with the pointer address. Should this patch solve the
> > > problem?
> > > - u16 *data = (u16 *)&rq->ifr_data;
> > > + u16 *data = (u16 *)rq->ifr_data;
> > From: Alan Cox [mailto:[EMAIL PROTECTED]]
> > The original code is correct
The 'mii-diag' program uses these ioctl() calls. See
http://cesdis.gsfc.nasa.gov/linux/diag/index.html
I'll take this opportunity to describe this little-known but very useful
utility. I hope that it ends up with the standard network support program
someday.
The 'mii-diag' program is a status monitoring and diagnostic program for
network interfaces that use MII (Media Independent Interface) transceivers.
A few drivers even generate synthetic MII status (that means they fake it)
for non-MII transceivers since it's such a useful model.
The 'mii-diag' program may be used for diagnosing problems, detecting
marginal physical layer links and monitoring link status.
[[ It takes only a trivial monitoring shell script to implement fail-over.
I plan to implement an non-zero exit status for failed links to make
this even easier. ]]
I hope to move the common MII reporting code into the generic driver support
for 2.3.*, although not to the pointless level of bloat as in some systems.
The kernel shouldn't need to know details such as the transceiver name --
that's why I've provided 'mii-diag' and libmii.c as user-level code.
Background info:
MII transceivers are usually associated with NWay autonegotiation:
http://cesdis.gsfc.nasa.gov/linux/misc/NWay.html
The libmii source code
ftp://cesdis.gsfc.nasa.gov/pub/linux/diag/libmii.c
Donald Becker [EMAIL PROTECTED]
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771
301-286-0882 http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
