[SeaBIOS] Re: [PATCH] hw/nvme: Increase `nvme_cmd_readwrite()` message log level from 3 to 5

On 7/27/20 2:59 PM, Paul Menzel wrote: > Currently, setting SeaBIOS debug level to 3, the log is filled with > messages like below. > > ns 1 read lba 11346288+8: 0 > ns 1 read lba 11346296+4: 0 > ns 1 read lba 11346300+4: 0 > ns 1 read lba 11346304+8: 0 > ns 1 read lba 11346312

[SeaBIOS] [PATCH v2] virtio-scsi: fix boot prio detection by using correct lun

Commits d6bdb85eb0 virtio-scsi: skip initializing non-bootable devices f82e82a5ab2 virtio-mmio: add support for scsi devices. both use the lun value from tmpl_drv, which is always 0, instead of the correct one passed as a separate parameter. This causes systems where LUNs other than 0 are set

[SeaBIOS] [PATCH] hw/nvme: Increase `nvme_cmd_readwrite()` message log level from 3 to 5

Currently, setting SeaBIOS debug level to 3, the log is filled with messages like below. ns 1 read lba 11346288+8: 0 ns 1 read lba 11346296+4: 0 ns 1 read lba 11346300+4: 0 ns 1 read lba 11346304+8: 0 ns 1 read lba 11346312+8: 0 ns 1 read lba 11346320+8: 0 ns 1 read lba

[SeaBIOS] Re: [PATCH] virtio-scsi: fix boot prio detection by using correct lun

Dear Stefan, Am 27.07.20 um 14:47 schrieb Stefan Reiter: Commits d6bdb85eb0 virtio-scsi: skip initializing non-bootable devices f82e82a5ab2 virtio-mmio: add support for scsi devices. both use the lun value from tmpl_drv, which is always 0, instead of the correct one passed as a seperate

[SeaBIOS] [PATCH] virtio-scsi: fix boot prio detection by using correct lun

Commits d6bdb85eb0 virtio-scsi: skip initializing non-bootable devices f82e82a5ab2 virtio-mmio: add support for scsi devices. both use the lun value from tmpl_drv, which is always 0, instead of the correct one passed as a seperate parameter. This causes systems where LUNs other than 0 are set