23 Jun, 2015

1 commit


17 Sep, 2013

1 commit


23 Jun, 2013

2 commits

  • arch/h8300/include/asm/io.h supports only H83007 (H8/3006,3007), H83068
    (H8/3065,3066,3067,3068,3069), and H8S2678 (H8S/2670,2673,2674R,2675,2676)
    CPU types.

    Hence disable H83002 (H8/3001,3002,3003) and H83048
    (H8/3044,3045,3046,3047,3048,3052) CPU support at the Kconfig level.

    This fixes build failures in allmodconfig/allyesconfig builds, as these
    always choose the first CPU type (H83002), which was unsupported:

    arch/h8300/include/asm/io.h:13:2: error: #error UNKNOWN CPU TYPE

    Signed-off-by: Geert Uytterhoeven

    Geert Uytterhoeven
     
  • arch/h8300/kernel/timer/itu.c and arch/h8300/kernel/timer/tpu.c
    only support 0--4 for CONFIG_H8300_ITU_CH resp. H8300_TPU_CH, hence limit
    them to that range in Kconfig.

    Signed-off-by: Geert Uytterhoeven

    Geert Uytterhoeven
     

22 May, 2012

1 commit

  • Sigh, I missed to check which architecture Kconfig files actually
    include the core Kconfig file. There are a few which did not. So we
    broke them.

    Instead of adding the includes to those, we are better off to move the
    include to init/Kconfig like we did already with irqs and others.

    This does not change anything for the architectures using the old
    style periodic timer mode. It just solves the build wreckage there.

    For those architectures which use the clock events infrastructure it
    moves the include of the core Kconfig file to "General setup" which is
    a way more logical place than having it at random locations specified
    by the architecture specific Kconfigs.

    Reported-by: Ingo Molnar
    Cc: Anna-Maria Gleixner
    Signed-off-by: Thomas Gleixner

    Thomas Gleixner
     

06 Jul, 2011

1 commit


18 Oct, 2010

1 commit


24 Jun, 2009

1 commit


17 Oct, 2008

1 commit


15 Feb, 2006

1 commit


24 Jun, 2005

1 commit

  • For all architectures, this just means that you'll see a "Memory Model"
    choice in your architecture menu. For those that implement DISCONTIGMEM,
    you may eventually want to make your ARCH_DISCONTIGMEM_ENABLE a "def_bool
    y" and make your users select DISCONTIGMEM right out of the new choice
    menu. The only disadvantage might be if you have some specific things that
    you need in your help option to explain something about DISCONTIGMEM.

    Signed-off-by: Dave Hansen
    Signed-off-by: Adrian Bunk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Dave Hansen
     

17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds