[ новости /+++ | форум | теги | ]

NAME
     qe - QEC/MACE Ethernet device driver

SYNOPSIS
     #include <mace.h>

     #include <qe.h>

     #include <qec.h>

     #include <dlpi.h>

DESCRIPTION
     qe is a multi-threaded, loadable, clonable, STREAMS hardware
     device  driver  supporting the connectionless Data Link Pro-
     vider Interface, dlpi(7P),  over  Am79C940  (MACE)  Ethernet
     controllers  in the SBus QED card.  qec(7D) is its parent in
     the Open Boot Prom device tree. There is no fixed limitation
     on  the  number of QED cards supported by the driver. The qe
     driver provides basic support for the MACE and QEC hardware.
     Functions  include  chip  initialization, frame transmit and
     receive,  multicast  and  promiscuous  support,  and   error
     recovery and reporting.

     The cloning character-special  device  /dev/qe  is  used  to
     access all MACE controllers installed within the system.

  qe and DLPI
     The qe driver is a "style 2" Data Link Service provider. All
     M_PROTO  and  M_PCPROTO  type  msgs  are interpreted as DLPI
     primitives. An explicit DL_ATTACH_REQ message by the user is
     required  to  associate  the opened stream with a particular
     device (ppa). The ppa ID is interpreted as an unsigned  long
     and  indicates  the  corresponding  device  instance  (unit)
     number. An error (DL_ERROR_ACK) is returned by the driver if
     the  ppa  field  value does not correspond to a valid device
     instance number for this system. The device  is  initialized
     on first attach and de-initialized (stopped) on last detach.

     The values returned by the driver in the DL_INFO_ACK  primi-
     tive  in  response  to  the DL_INFO_REQ from the user are as
     follows:

        o  The max SDU is  1500 (ETHERMTU).

        o  The min SDU is  0.

        o  The dlsap address length is  8.

        o  The MAC type is DL_ETHER.

        o  The sap length  value  is   -2  meaning  the  physical
           address  component is followed immediately by a 2 byte
           sap component within the DLSAP address.

        o  The service mode is DL_CLDLS.

        o  No  optional  quality  of  service  (QOS)  support  is
           included at present so the QOS fields are 0.

        o  The provider style is DL_STYLE2.

        o  The version is DL_VERSION_2.

        o  The broadcast address value is Ethernet/IEEE broadcast
           address (0xFFFFFF).

     Once  in  the  DL_ATTACHED  state,  the  user  must  send  a
     DL_BIND_REQ  to  associate  a particular SAP (Service Access
     Pointer) with the stream.  The qe driver interprets the  sap
     field within the DL_BIND_REQ as an Ethernet "type" therefore
     valid values for the sap field are in the [0-0xFFFF]  range.
     Only  one  Ethernet  type  can be bound to the stream at any
     time.

     If the user selects a sap with a value of  0,  the  receiver
     will  be  in  802.3 mode. All frames received from the media
     having a "type" field in the range [0-1500] are  assumed  to
     be 802.3 frames and are routed up all open Streams which are
     bound to sap value 0. If more than one Stream is  in  "802.3
     mode" then the frame will be duplicated and routed up multi-
     ple Streams as DL_UNITDATA_IND messages.

     In transmission, the driver checks  the  sap  field  of  the
     DL_BIND_REQ  if  the  sap value is 0, and if the destination
     type field is in the range [0-1500]. If either is true,  the
     driver  computes  the  length  of the message, not including
     initial M_PROTO mblk  (message  block),  of  all  subsequent
     DL_UNITDATA_REQ  messages  and  transmits  802.3 frames that
     have this value in the MAC frame header length field.

     The driver also supports raw  M_DATA  mode.  When  the  user
     sends  a DLIOCRAW ioctl, the particular Stream is put in raw
     mode.  A complete frame along with a proper ether header  is
     expected as part of the data.

     The qe driver DLSAP address format consists of  the  6  byte
     physical  (Ethernet)  address component followed immediately
     by the 2 byte sap (type) component producing an 8 byte DLSAP
     address.   Applications should not hardcode to this particu-
     lar implementation-specific DLSAP  address  format  but  use
     information returned in the DL_INFO_ACK primitive to compose
     and decompose DLSAP addresses.  The sap length,  full  DLSAP
     length,  and  sap/physical  ordering are included within the
     DL_INFO_ACK. The physical address length can be computed  by
     subtracting  the  sap  length  from  the  full DLSAP address
     length or by issuing  the  DL_PHYS_ADDR_REQ  to  obtain  the
     current physical address associated with the stream.

     Once in the DL_BOUND state, the user may transmit frames  on
     the  Ethernet  by sending DL_UNITDATA_REQ messages to the qe
     driver. The qe driver will route received Ethernet frames up
     all  those open and bound streams having a sap which matches
     the Ethernet type as DL_UNITDATA_IND messages. Received Eth-
     ernet  frames  are  duplicated  and  routed up multiple open
     streams if necessary.  The DLSAP  address  contained  within
     the DL_UNITDATA_REQ and DL_UNITDATA_IND messages consists of
     both the sap (type) and physical (Ethernet) components.

  qe Primitives
     In addition to the mandatory connectionless DLPI message set
     the driver additionally supports the following primitives.

     The  DL_ENABMULTI_REQ   and   DL_DISABMULTI_REQ   primitives
     enable/disable   reception  of  individual  multicast  group
     addresses.  A set of multicast addresses may be  iteratively
     created and modified on a per-stream basis using these prim-
     itives. These primitives are accepted by the driver  in  any
     state following DL_ATTACHED.

     The DL_PROMISCON_REQ and DL_PROMISCOFF_REQ  primitives  with
     the   DL_PROMISC_PHYS   flag   set  in  the  dl_level  field
     enables/disables  reception  of  all  ("promiscuous   mode")
     frames  on the media including frames generated by the local
     host. When  used  with  the  DL_PROMISC_SAP  flag  set  this
     enables/disables   reception  of  all  sap  (Ethernet  type)
     values. When used with the DL_PROMISC_MULTI  flag  set  this
     enables/disables reception of all multicast group addresses.
     The effect of each is  always  on  a  per-stream  basis  and
     independent  of  the other sap and physical level configura-
     tions on this stream or other streams.

     The DL_PHYS_ADDR_REQ primitive return the 6  octet  Ethernet
     address currently associated (attached) to the stream in the
     DL_PHYS_ADDR_ACK primitive. This primitive is valid only  in
     states following a successful DL_ATTACH_REQ.

     The DL_SET_PHYS_ADDR_REQ primitive changes the 6 octet  Eth-
     ernet   address  currently  associated  (attached)  to  this
     stream. The credentials  of  the  process  which  originally
     opened this stream must be superuser or EPERM is returned in
     the DL_ERROR_ACK. This primitive is destructive in  that  it
     affects  all  other  current  and future streams attached to
     this device.  An  M_ERROR  is  sent  up  all  other  streams
     attached  to  this device when this primitive on this stream
     is successful. Once changed, all streams subsequently opened
     and  attached  to  this device will obtain this new physical
     address. Once changed, the physical address will  remain  so
     until  this primitive is used to change the physical address
     again or the system is rebooted, whichever comes first.

FILES
     /dev/qe
           qe special character device.

SEE ALSO
     dlpi(7P), le(7D), qec(7D)

Партнёры:

Хостинг: