1. 25 9月, 2020 1 次提交
  2. 09 7月, 2020 2 次提交
  3. 07 1月, 2020 1 次提交
  4. 14 4月, 2019 1 次提交
  5. 04 12月, 2018 1 次提交
  6. 21 11月, 2018 1 次提交
    • S
      video: Update video_set_default_colors() to support invert · b9f210a3
      Simon Glass 提交于
      It is useful to be able to invert the colours in some cases so that the
      text matches the background colour. Add a parameter to the function to
      support this.
      
      It is strange that function takes a private data structure from another
      driver as an argument. It seems better to pass the device and have the
      function internally work out how to find its required information.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      b9f210a3
  7. 09 10月, 2018 3 次提交
  8. 29 9月, 2018 1 次提交
  9. 06 3月, 2018 2 次提交
  10. 29 9月, 2017 1 次提交
  11. 24 10月, 2016 1 次提交
  12. 25 5月, 2016 1 次提交
  13. 30 1月, 2016 2 次提交
  14. 22 1月, 2016 1 次提交
  15. 21 1月, 2016 1 次提交
    • S
      dm: video: Add a video uclass · 1acafc73
      Simon Glass 提交于
      U-Boot has separate code for LCDs and 'video' devices. Both now use a
      very similar API thanks to earlier work by Nikita Kiryanov. With the driver-
      model conversion we should unify these into a single uclass.
      
      Unfortunately there are different features supported by each. This
      implementation provides for a common set of features which should serve
      most purposes. The intent is to support:
      
      - bitmap devices with 8, 16 and 32 bits per pixel
      - text console wih white on black or vice versa
      - rotated text console
      - bitmap display (BMP format)
      
      More can be added as additional boards are ported over to use driver model
      for video.
      
      The name 'video' is chosen for the uclass since it is more generic than LCD.
      Another option would be 'display' but that would introduce a third concept
      to U-Boot which seems like the wrong approach.
      
      The existing LCD and video init functions are not needed now, so this uclass
      makes no attempt to implement them.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Acked-by: NAnatolij Gustschin <agust@denx.de>
      1acafc73
  16. 20 4月, 2015 1 次提交
  17. 23 7月, 2014 1 次提交
    • S
      stdio: Pass device pointer to stdio methods · 709ea543
      Simon Glass 提交于
      At present stdio device functions do not get any clue as to which stdio
      device is being acted on. Some implementations go to great lengths to work
      around this, such as defining a whole separate set of functions for each
      possible device.
      
      For driver model we need to associate a stdio_dev with a device. It doesn't
      seem possible to continue with this work-around approach.
      
      Instead, add a stdio_dev pointer to each of the stdio member functions.
      
      Note: The serial drivers have the same problem, but it is not strictly
      necessary to fix that to get driver model running. Also, if we convert
      serial over to driver model the problem will go away.
      
      Code size increases by 244 bytes for Thumb2 and 428 for PowerPC.
      
      22: stdio: Pass device pointer to stdio methods
             arm: (for 2/2 boards)  all +244.0  bss -4.0  text +248.0
         powerpc: (for 1/1 boards)  all +428.0  text +428.0
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Acked-by: NMarek Vasut <marex@denx.de>
      Reviewed-by: NMarek Vasut <marex@denx.de>
      709ea543
  18. 28 8月, 2013 1 次提交
  19. 07 11月, 2012 1 次提交
  20. 25 5月, 2012 1 次提交
  21. 04 11月, 2001 1 次提交