Fork of the vendor (Boundary Devices) u-boot for Reform 2, with minor tweaks. The goal is to migrate to mainstream u-boot or barebox ASAP. The main impediment so far is the 4GB RAM config.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.

63 lines
1.9 KiB

  1. # Copyright (c) 2016 DENX Software Engineering GmbH
  2. # Heiko Schocher <>
  3. #
  4. # SPDX-License-Identifier: GPL-2.0+
  5. #
  6. ToDo list for tbot
  7. ==================
  8. please look also into the tbot ToDo list.
  10. - cleanup tbot code:
  11. - remove all retry / timeout pieces of code
  12. - clean up tbot function names, as I am not good in
  13. giving function a understandable name ;-)
  14. - as I am not a python programmer, cleanup whole tbot code
  15. - introduce a "layering" like yocto do, so U-Boot TC can integrated
  16. into U-Boot source code.
  17. Proposal:
  18. introduce subdirs in "src/tc"
  19. lab: all lab specific stuff
  20. lab/common: common lab stuff (for example ssh handling)
  21. lab/ssh_std: ssh_std specific stuff
  22. u-boot: all u-boot tests
  23. u-boot/common: common u-boot tc
  24. u-boot/duts: DUTS tc
  25. u-boot-dxr2: all u-boot dxr2 board specific tc
  26. board: board tc
  27. board/common: common board tc
  28. board/dxr2: all tc for dxr2 board
  29. linux: all linux tc
  30. linux/common: common linux tc
  31. linux/dxr2
  32. - move U-Boot special TC to U-Boot source
  33. -> need a mechanism in tbot, how it gets automatically for example
  34. U-Boot TC from U-Boot source...
  35. -> add a consistency checker
  36. - simplify tbot log output (seperate a lot of output which is currently
  37. in INFO logging level, to another logging level)
  38. started (new loglevel "CON", whih prints read/write from console only), see:
  40. - make the timestamp configurable
  41. - Open more than 2 filehandles ?
  42. Do we need for more complex TC more than 2 filehandles?
  43. - Find a way to document all TC and document all variables they use in an
  44. automated way.
  45. - write a lot of more TC
  46. - get U-Boot configuration settings from current U-Boot code and use
  47. them in U-Boot TC-es