| commit | 3f4919e49e28e161567b3730ef02b6904bfd9887 | |
| author | Thomas Huth <thuth@redhat.com> | |
| Mon, 20 Aug 2018 17:28:03 +0000 (20 19:28 +0200) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Tue, 21 Aug 2018 07:47:16 +0000 (21 09:47 +0200) | ||
| tree | 607f3ed8394b19977addb86b69628ea28a048247 | treesnapshot (tar.gz zip) |
| parent | d0092d90eb546a8bbe9e9120426c189474123797 | commitdiff |
hw/display/ramfb: Compile the ramfb code only when CONFIG_FW_CFG_DMA is set
According to the ramfb_setup() function, the ramfb device needs fw_cfg
with DMA, so we should also only compile and link it into those targets
which support it, to avoid that the device shows up on systems where it
can not be used at all (e.g. s390x).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-id: 1534786083-26559-1-git-send-email-thuth@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
According to the ramfb_setup() function, the ramfb device needs fw_cfg
with DMA, so we should also only compile and link it into those targets
which support it, to avoid that the device shows up on systems where it
can not be used at all (e.g. s390x).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-id: 1534786083-26559-1-git-send-email-thuth@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
| hw/display/Makefile.objs | diffblobblamehistory |