1. 29 6月, 2018 2 次提交
    • P
      sd: Don't trace SDRequest crc field · 13606b99
      Peter Maydell 提交于
      We don't actually implement SD command CRC checking, because
      for almost all of our SD controllers the CRC generation is
      done in hardware, and so modelling CRC generation and checking
      would be a bit pointless. (The exception is that milkymist-memcard
      makes the guest software compute the CRC.)
      
      As a result almost all of our SD controller models don't bother
      to set the SDRequest crc field, and the SD card model doesn't
      check it. So the tracing of it in sdbus_do_command() provokes
      Coverity warnings about use of uninitialized data.
      
      Drop the CRC field from the trace; we can always add it back
      if and when we do anything useful with the CRC.
      
      Fixes Coverity issues 1386072, 1386074, 1386076, 1390571.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NPhilippe Mathieu-Daudé <f4bug@amsat.org>
      Message-id: 20180626180324.5537-1-peter.maydell@linaro.org
      13606b99
    • P
      sdcard: Reduce sdcard_set_blocklen() trace digits · dcfebcf9
      Philippe Mathieu-Daudé 提交于
      Per the Physical Layer Simplified Spec. "5.3 CSD Register":
      
        "The maximum block length might therefore be in the range 512...2048 bytes"
      
      Therefore 3 hexdigits are enough to report the block length.
      Signed-off-by: NPhilippe Mathieu-Daudé <f4bug@amsat.org>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      dcfebcf9
  2. 10 4月, 2018 1 次提交
  3. 10 3月, 2018 2 次提交
  4. 22 2月, 2018 3 次提交
  5. 13 2月, 2018 4 次提交
  6. 16 1月, 2018 1 次提交
  7. 11 1月, 2018 1 次提交
  8. 01 8月, 2017 1 次提交
  9. 31 7月, 2017 1 次提交
  10. 12 8月, 2016 1 次提交
  11. 21 6月, 2016 1 次提交