nerves-project / nerves_pack Goto Github PK

Environment

• Elixir version (elixir -v):

Erlang/OTP 24 [erts-12.0.3] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]

Elixir 1.12.2 (compiled with Erlang/OTP 24)

• Nerves environment: (mix nerves.env --info)

|nerves_bootstrap| Environment Package List

  Pkg:         nerves_toolchain_ctng
  Vsn:         1.7.2
  Type:        toolchain_platform
  BuildRunner: {nil, []}

  Pkg:         nerves_system_elias
  Vsn:         0.6.1
  Type:        system
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:         nerves_toolchain_arm_unknown_linux_gnueabihf
  Vsn:         1.3.2
  Type:        toolchain
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:         nerves_system_br
  Vsn:         1.16.4
  Type:        system_platform
  BuildRunner: {nil, []}

|nerves_bootstrap| Loadpaths Start


Nerves environment
  MIX_TARGET:   nrv_elias
  MIX_ENV:      dev

|nerves_bootstrap| Environment Variable List
  target:     nrv_elias
  toolchain:  /home/connor/.nerves/artifacts/nerves_toolchain_arm_unknown_linux_gnueabihf-linux_x86_64-1.3.2
  system:     /home/connor/workspace/keeplabs/elias/o/elias
  app:        .

|nerves_bootstrap| Loadpaths End

• Additional information about your host, target hardware or environment that
  may help

Current behavior

On a board with no ethernet or gadget port, vintage_net_ethernet and vintage_net_direct
are loaded in the firmware

Expected behavior

Those deps should not be loaded if i don't want.

Erlang distribution can mostly be configured by editing vm.args.eex of your firmware, but it might be nice to handle it in a more controlled fashion within NervesPack. (much like nerves_init_gadget did)

This has become a more prevalent need in some places, so this would be a good place to add support as an example implementation

To get the iconic nerves.local host requires some mdns_lite config values at compile time

Once pcmarks/mdns_lite#59 is merged, then we should add default configuration at runtime.

#8 brought up a few good points about handling VintageNetWizard in this lib. I really teeter on the fence in this area so wanted to jot some thoughts if others want to weigh in.

Moving the button as optional was good. Used if people want, but also a solid example of what you could do.

Starting the wizard if you have wlan interface available but not configured might be a gray area. For now, I think it's convenient. But it could get in the way should others have specific logic for handling a wizard (which could be very common case). Should we keep it? Should it be behind a config value? Should we not even have as a dep?

First of all, thanks a lot for this awesome project. I am using the bbb project on bbg and I can't get the ipby usb (no virtual network card enumerated), but I can get the correct ip address by eth. I can be sure that my cable is ok because in the official bbb image it is working. Do you have any suggestions for this, thanks!

This would be convenient to have. Would help for the cases that you sometimes want to enable/disable on the fly but don't want to do a whole new fw image.