1. 21 11月, 2009 1 次提交
  2. 17 11月, 2009 1 次提交
  3. 15 10月, 2009 3 次提交
  4. 14 10月, 2009 1 次提交
  5. 13 10月, 2009 1 次提交
  6. 01 10月, 2009 1 次提交
  7. 23 9月, 2009 1 次提交
  8. 18 9月, 2009 1 次提交
  9. 31 8月, 2009 1 次提交
  10. 24 8月, 2009 1 次提交
  11. 20 8月, 2009 2 次提交
  12. 13 8月, 2009 1 次提交
  13. 06 8月, 2009 1 次提交
  14. 23 7月, 2009 1 次提交
  15. 20 7月, 2009 1 次提交
  16. 27 6月, 2009 1 次提交
  17. 23 6月, 2009 1 次提交
  18. 22 6月, 2009 1 次提交
  19. 16 6月, 2009 1 次提交
    • G
      debugfs: Fix terminology inconsistency of dir name to mount debugfs filesystem. · 156f5a78
      GeunSik Lim 提交于
      Many developers use "/debug/" or "/debugfs/" or "/sys/kernel/debug/"
      directory name to mount debugfs filesystem for ftrace according to
      ./Documentation/tracers/ftrace.txt file.
      
      And, three directory names(ex:/debug/, /debugfs/, /sys/kernel/debug/) is
      existed in kernel source like ftrace, DRM, Wireless, Documentation,
      Network[sky2]files to mount debugfs filesystem.
      
      debugfs means debug filesystem for debugging easy to use by greg kroah
      hartman. "/sys/kernel/debug/" name is suitable as directory name
      of debugfs filesystem.
      - debugfs related reference: http://lwn.net/Articles/334546/
      
      Fix inconsistency of directory name to mount debugfs filesystem.
      
      * From Steven Rostedt
        - find_debugfs() and tracing_files() in this patch.
      Signed-off-by: NGeunSik Lim <geunsik.lim@samsung.com>
      Acked-by     : Inaky Perez-Gonzalez <inaky@linux.intel.com>
      Reviewed-by  : Steven Rostedt <rostedt@goodmis.org>
      Reviewed-by  : James Smart <james.smart@emulex.com>
      CC: Jiri Kosina <trivial@kernel.org>
      CC: David Airlie <airlied@linux.ie>
      CC: Peter Osterlund <petero2@telia.com>
      CC: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
      CC: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
      CC: Masami Hiramatsu <mhiramat@redhat.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      156f5a78
  20. 15 6月, 2009 1 次提交
  21. 13 6月, 2009 1 次提交
  22. 09 6月, 2009 2 次提交
  23. 08 6月, 2009 2 次提交
  24. 30 5月, 2009 1 次提交
  25. 26 5月, 2009 2 次提交
  26. 25 5月, 2009 1 次提交
  27. 19 5月, 2009 1 次提交
  28. 18 5月, 2009 1 次提交
  29. 30 4月, 2009 4 次提交
  30. 27 4月, 2009 2 次提交
    • V
      bnx2x: Separated FW from the source. · 94a78b79
      Vladislav Zolotarov 提交于
      >From now on FW will be downloaded from the binary file using request_firmware.
      
      There will be different files for every supported chip. Currently 57710 (e1) and
      57711 (e1h).
      
      File names have the following format: bnx2x-<chip version>-<FW version>.fw.
      ihex versions of current FW files are submitted in the next patch.
      
      Each binary file has a header in the following format:
      
      
      struct bnx2x_fw_file_section {
      	__be32 len;
      	__be32 offset;
      }
      
      struct bnx2x_fw_file_hdr {
      	struct bnx2x_fw_file_section init_ops;
      	struct bnx2x_fw_file_section init_ops_offsets;
      	struct bnx2x_fw_file_section init_data;
      	struct bnx2x_fw_file_section tsem_int_table_data;
      	struct bnx2x_fw_file_section tsem_pram_data;
      	struct bnx2x_fw_file_section usem_int_table_data;
      	struct bnx2x_fw_file_section usem_pram_data;
      	struct bnx2x_fw_file_section csem_int_table_data;
      	struct bnx2x_fw_file_section csem_pram_data;
      	struct bnx2x_fw_file_section xsem_int_table_data;
      	struct bnx2x_fw_file_section xsem_pram_data;
      	struct bnx2x_fw_file_section fw_version;
      }
      
      Each bnx2x_fw_file_section contains the length and the offset of the appropriate
      section in the binary file. Values are stored in the big endian format.
      
      Data types of arrays:
      
      init_data            __be32
      init_ops_offsets     __be16
      XXsem_pram_data         u8
      XXsem_int_table_data    u8
      init_ops             struct raw_op {
                                u8   op;
      			__be24 offset;
                              __be32 data;
      		     }
      fw_version              u8
      
      >From now boundaries of a specific initialization stage are stored in
      init_ops_offsets array instead of being defined by separate macroes. The index 
      in init_ops_offsets is calculated by BLOCK_OPS_IDX macro:
      
      #define BLOCK_OPS_IDX(block, stage, end) \
             (2*(((block)*STAGE_IDX_MAX) + (stage)) + (end))
      
      Security:
      
      In addition to sanity check of array boundaries bnx2x will check a FW version.
      Additional checks might be added in the future.
      Signed-off-by: NVladislav Zolotarov <vladz@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      94a78b79
    • G
      net: add Xilinx ll_temac device driver · 92744989
      Grant Likely 提交于
      This patch adds support for the Xilinx ll_temac 10/100/1000 Ethernet
      device.  The ll_temac ipcore is typically used on Xilinx Virtex and
      Spartan designs attached to either a PowerPC 4xx or Microblaze
      processor.
      
      At the present moment, this driver only works with Virtex5 PowerPC
      designs because it assumes DCR is used to access the DMA registers.
      However, the low level access to DMA registers is abstracted and
      it should be easy to adapt for the other implementations.
      
      I'm posting this driver now as an RFC.  There are still some things that
      need to be tightened up, but it does appear to be stable.
      
      Derived from driver code written by Yoshio Kashiwagi and David H. Lynch Jr.
      
      Tested on Xilinx ML507 eval board with Base System Builder generated
      FPGA design.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Acked-by: NAndy Fleming <afleming@freescale.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      92744989