1. 12 9月, 2005 4 次提交
    • E
      [NET]: Add netlink connector. · 7672d0b5
      Evgeniy Polyakov 提交于
      Kernel connector - new userspace <-> kernel space easy to use
      communication module which implements easy to use bidirectional
      message bus using netlink as it's backend.  Connector was created to
      eliminate complex skb handling both in send and receive message bus
      direction.
      
      Connector driver adds possibility to connect various agents using as
      one of it's backends netlink based network.  One must register
      callback and identifier. When driver receives special netlink message
      with appropriate identifier, appropriate callback will be called.
      
      From the userspace point of view it's quite straightforward:
      
      	socket();
      	bind();
      	send();
      	recv();
      
      But if kernelspace want to use full power of such connections, driver
      writer must create special sockets, must know about struct sk_buff
      handling...  Connector allows any kernelspace agents to use netlink
      based networking for inter-process communication in a significantly
      easier way:
      
      int cn_add_callback(struct cb_id *id, char *name, void (*callback) (void *));
      void cn_netlink_send(struct cn_msg *msg, u32 __groups, int gfp_mask);
      
      struct cb_id
      {
      	__u32			idx;
      	__u32			val;
      };
      
      idx and val are unique identifiers which must be registered in
      connector.h for in-kernel usage.  void (*callback) (void *) - is a
      callback function which will be called when message with above idx.val
      will be received by connector core.
      
      Using connector completely hides low-level transport layer from it's
      users.
      
      Connector uses new netlink ability to have many groups in one socket.
      
      [ Incorporating many cleanups and fixes by myself and
        Andrew Morton -DaveM ]
      Signed-off-by: NEvgeniy Polyakov <johnpol@2ka.mipt.ru>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7672d0b5
    • W
      [PATCH] Sun HME: enable and map PCI ROM properly · ce1289ad
      Willy Tarreau 提交于
      This ports the Sun GEM ROM mapping/enable fixes it sunhme (which used
      the same PCI ROM mapping code).
      
      Without this, I get NULL MAC addresses for all 4 ports (it's a SUN QFE).
      With it, I get the correct addresses (the ones printed on the label on
      the card).
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ce1289ad
    • L
      Sun GEM ethernet: enable and map PCI ROM properly · 4120b028
      Linus Torvalds 提交于
      This same patch was reported to fix the MAC address detection on sunhme
      (next patch).  Most people seem to be running this on Sparcs or PPC
      machines, where we get the MAC address from their respective firmware
      rather than from the (previously broken) ROM mapping routines.
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4120b028
    • L
      hpt366: write the full 4 bytes of ROM address, not just low 1 byte · 9ec4ff42
      Linus Torvalds 提交于
      This is one heck of a confused driver.  It uses a byte write to a dword
      register to enable a ROM resource that it doesn't even seem to be using.
      
      "Lost and wandering in the desert of confusion"
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9ec4ff42
  2. 11 9月, 2005 35 次提交
  3. 10 9月, 2005 1 次提交