Skip to content
Snippets Groups Projects
  1. Jan 30, 2017
    • Alessandro Rubini's avatar
      config: force ppsi reconfiguration by default · ce184a81
      Alessandro Rubini authored and Adam Wujek's avatar Adam Wujek committed
      
      Without this, after the first build of wrpc-sw the ppsi
      configuration was never changed.
      
      So if you built e.g. "gsi_defconfig" and then reconfigure
      for "gsi_pdelay_defconfig" you'll get no pdelay in there.
      
      For me, and the next maintainers of ppsi, the new configuration option
      CONFIG_PPSI_FORCE_CONFIG can be unset in order to test with personale
      changes in ppsi configuration.
      
      Signed-off-by: default avatarAlessandro Rubini <rubini@gnudd.com>
      ce184a81
    • Alessandro Rubini's avatar
      MAKEALL: force preferred ppsi configuration for each wrpc configuration · e37189e2
      Alessandro Rubini authored and Adam Wujek's avatar Adam Wujek committed
      
      Also, preserve and restore current configuration, so I don't get mad
      when checking with MAKEALL during my tests for new feature.
      
      The rationale for this is that wrpc-sw will soon select different ppsi
      choices according to its own configuration, through $(PPSI-CFG-y).
      Actually, it already does for the host process build.
      
      MAKEALL must obey this choice, so we trim ppsi configuration
      each time we reconfigure wrpc (removing the file would spit an
      error instead).
      
      Then, our Makefile forces a ppsi reconfig if ppsi/.config is missing
      *or* empty.
      
      Signed-off-by: default avatarAlessandro Rubini <rubini@gnudd.com>
      e37189e2
    • Alessandro Rubini's avatar
      tools/update_configs: name says it all · c7d2c711
      Alessandro Rubini authored and Adam Wujek's avatar Adam Wujek committed
      
      Signed-off-by: default avatarAlessandro Rubini <rubini@gnudd.com>
      c7d2c711
    • Alessandro Rubini's avatar
      Kconfig: fix warnings · affb4139
      Alessandro Rubini authored and Adam Wujek's avatar Adam Wujek committed
      
      The new config tools are more picky. We got:
      
         Kconfig:22:warning: defaults for choice values not supported
      
      and
      
        warning: (WR_SWITCH) selects UART which has unmet direct dependencies
                   (DEVELOPER && EMBEDDED_NODE)
      
      The latter is fixed adding WR_SWITCH in the dependencies. The former
      is worked-around by using "IS_XINT" and friends in "choice", and
      then "XINT" replicates the "IS_" choice.  I dislike it, because it's
      repetition, but we really need CONFIG_PRINTF_XINT and friends in
      pp_printf/
      
      Signed-off-by: default avatarAlessandro Rubini <rubini@gnudd.com>
      affb4139
  2. Jan 26, 2017
  3. Nov 28, 2016
  4. Nov 03, 2016
  5. Nov 01, 2016
  6. Oct 27, 2016
  7. Aug 30, 2016
  8. Aug 22, 2016
  9. Aug 09, 2016
  10. Aug 04, 2016
  11. Aug 03, 2016
  12. Jul 29, 2016