1. 01 4月, 2013 2 次提交
  2. 16 2月, 2013 2 次提交
    • V
      ARC: [Review] Multi-platform image #2: Board callback Infrastructure · 03a6d28c
      Vineet Gupta 提交于
      The orig platform code orgnaization was singleton design pattern - only
      one platform (and board thereof) would build at a time.
      
      Thus any platform/board specific code (e.g. irq init, early init ...)
      expected by ARC common code was exported as well defined set of APIs,
      with only ONE instance building ever.
      
      Now with multiple-platform build requirement, that design of code no
      longer holds - multiple board specific calls need to build at the same
      time - so ARC common code can't use the API approach, it needs a
      callback based design where each board registers it's specific set of
      functions, and at runtime, depending on board detection, the callbacks
      are used from the registry.
      
      This commit adds all the infrastructure, where board specific callbacks
      are specified as a "maThine description".
      
      All the hooks are placed in right spots, no board callbacks registered
      yet (with MACHINE_STARt/END constructs) so the hooks will not run.
      
      Next commit will actually convert the platform to this infrastructure.
      Signed-off-by: NVineet Gupta <vgupta@synopsys.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      03a6d28c
    • V
      ARC: [DeviceTree] Basic support · 999159a5
      Vineet Gupta 提交于
      This is minimal infrastructure needed for devicetree work.
      It uses an a sample "skeleton" devicetree - embedded in kernel image -
      to print the board, manufacturer by parsing the top-level "compatible"
      string.
      
      As of now we don't need any additional "board" specific "machine_desc".
      
      TODO: support interpreting the command line as boot-loader passed dtb
      Signed-off-by: NVineet Gupta <vgupta@synopsys.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: devicetree-discuss@lists.ozlabs.org
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: James Hogan <james.hogan@imgtec.com>
      Reviewed-by: NRob Herring <rob.herring@calxeda.com>
      Reviewed-by: NJames Hogan <james.hogan@imgtec.com>
      999159a5
  3. 11 2月, 2013 1 次提交
  4. 18 12月, 2010 1 次提交
  5. 22 11月, 2010 1 次提交
  6. 02 10月, 2010 1 次提交
    • N
      ARM: do not define VMALLOC_END relative to PAGE_OFFSET · 7c63984b
      Nicolas Pitre 提交于
      VMALLOC_END is supposed to be an absolute value, while PAGE_OFFSET may
      vary depending on the selected user:kernel memory split mode through
      CONFIG_VMSPLIT_*.  In fact, the goal of moving PAGE_OFFSET down is to
      accommodate more directly addressed RAM by the kernel below the vmalloc
      area, and having VMALLOC_END move along PAGE_OFFSET is rather against
      the very reason why PAGE_OFFSET can be moved in the first place.
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      7c63984b
  7. 07 8月, 2008 1 次提交
  8. 03 5月, 2005 1 次提交
  9. 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