1. 07 1月, 2006 1 次提交
  2. 04 12月, 2005 1 次提交
    • L
      Link USB drivers later in the kernel · 6015d2c4
      Linus Torvalds 提交于
      We want to link the "regular" SCSI drivers before the USB storage
      driver, since historically we've always detected internal SCSI disks
      before the external USB storage modules.
      
      The link order matters for initcall ordering, and this got broken by
      mistake by commit 7586269c which moved
      the USB host controller PCI quirk handling around.
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6015d2c4
  3. 07 11月, 2005 2 次提交
  4. 29 10月, 2005 1 次提交
    • D
      [PATCH] USB: move handoff code · 7586269c
      David Brownell 提交于
      This moves the PCI quirk handling for USB host controllers from the
      PCI directory to the USB directory.  Follow-on patches will need to:
      
      (a) merge these copies with the originals in the HCD reset methods.
      they don't wholly agree, despite doing the very same thing; and
      
      (b) eventually change it so "usb-handoff" is the default, to help
      get more robust USB/BIOS/input/... interactions.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
       drivers/Makefile              |    2
       drivers/pci/quirks.c          |  253 ---------------------------------------
       drivers/usb/Makefile          |    1
       drivers/usb/host/Makefile     |    5
       drivers/usb/host/pci-quirks.c |  272 ++++++++++++++++++++++++++++++++++++++++++
       5 files changed, 280 insertions(+), 253 deletions(-)
      7586269c
  5. 12 9月, 2005 1 次提交
    • 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
  6. 25 8月, 2005 1 次提交
  7. 18 8月, 2005 1 次提交
  8. 12 7月, 2005 1 次提交
  9. 22 6月, 2005 1 次提交
  10. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4